similar to: Build bug and execution bug

Displaying 20 results from an estimated 2000 matches similar to: "Build bug and execution bug"

2008 May 12
12
[Bug 1463] New: Running nohup sleep 70 & and then exiting shell, hangs ssh
https://bugzilla.mindrot.org/show_bug.cgi?id=1463 Summary: Running nohup sleep 70 & and then exiting shell, hangs ssh Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component:
2013 Aug 05
2
RemoteForward and dynamically allocated listen port
Specifying a RemoteForward of 0:example.com:1234 dynamically allocates the listen port on the server, and then reports it to ... the client! Where it is practically useless. Was this someone's idea of a joke? Presumably not--there are some technical obstacles to reporting it to the remote process. I'd like to help solve that problem. The natural way to me would be to extend the syntax
2020 Mar 26
6
[Bug 3140] New: support a token for XDG_RUNTIME_DIR
https://bugzilla.mindrot.org/show_bug.cgi?id=3140 Bug ID: 3140 Summary: support a token for XDG_RUNTIME_DIR Product: Portable OpenSSH Version: 8.2p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org
2023 Aug 30
2
[Bug 3609] New: Support the special ${RANDOM} environment variable
https://bugzilla.mindrot.org/show_bug.cgi?id=3609 Bug ID: 3609 Summary: Support the special ${RANDOM} environment variable Product: Portable OpenSSH Version: 9.4p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs
2023 Dec 25
3
[Bug 3648] New: ssh client blocks itself by leaving unix domain socket alive after user
https://bugzilla.mindrot.org/show_bug.cgi?id=3648 Bug ID: 3648 Summary: ssh client blocks itself by leaving unix domain socket alive after user Product: Portable OpenSSH Version: 9.3p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh
2016 Oct 05
3
Socket forwarding with non existent remote directories
Hi openssh dev's, I love an truly appreciate the Socket forwarding feature in OpenSSH 6.7. i use it for forwarding the socket of GnuPG's agent (that handles the secret stuff) to remote machines. Usecase: ====== I am a remote worker and use gnupg agent forwarding to connect to our company infrastructure that makes heavy use of PGP encryption while keeping my key out of the hands of
2020 Nov 12
3
run firefox via an ssh tunnel
On 11/12/20 7:50 AM, Jonathan Billings wrote: > On Thu, Nov 12, 2020 at 12:56:15PM +0000, Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS wrote: >> If the point is to access a specific web site only the remote >> machine can get to, you can also do it with port forwarding: >> ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine >> and
2019 Jun 27
2
Does ssh need sendfd in pledge() call?
Hi, I posted this question to the OpenBSD bugs list last week, however I have had no reply and it was suggested on IRC that I post here instead. So I must apologise if this is not appropriate. For a reference here is my previous post: https://marc.info/?l=openbsd-bugs&m=156080681530337&w=2 I am running OpenBSD 6.5-stable (also tested on -current). When I ssh somewhere I get a sig abort
2008 Jul 09
2
[Bug 1484] New: escape character does not work over shared connections
https://bugzilla.mindrot.org/show_bug.cgi?id=1484 Summary: escape character does not work over shared connections Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: ssh AssignedTo:
2008 Aug 04
1
Hanging ssh sessions with openssh-5.1p1 and Solaris 8 & 10
Since we upgraded OpenSSH from 5.0p1 to 5.1p1 on our Solaris 8 boxes (I know, I know, we should upgrade or retire them...), we've started experiencing problems with slogin'ing into these boxes, running vi, and pasting text into the vi session. As long as we are pasting in less that 1024 characters it's fine. With >= 1024 characters, the session hangs. If you run
2003 Feb 03
8
[Bug 413] Port forwarding: [localhost:]localport:remotehost:remoteport
http://bugzilla.mindrot.org/show_bug.cgi?id=413 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From markus at openbsd.org 2003-02-03 19:50 ------- i'll look into this. ------- You are
2017 Feb 15
5
[Bug 2677] New: Provide a way to set an environment variable from ssh_config
https://bugzilla.mindrot.org/show_bug.cgi?id=2677 Bug ID: 2677 Summary: Provide a way to set an environment variable from ssh_config Product: Portable OpenSSH Version: 7.4p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh
2017 Oct 03
0
Announce: OpenSSH 7.6 released
OpenSSH 7.6 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches, reported bugs, tested
2008 Jun 18
2
SSH connection hang after upgrade
I recently had to upgrade my version of OpenSSH from 4.7 to 5.0p1 on my MacBook (Darwin). I installed the latest 'portable' tarball and removed the system version: $ ssh -V OpenSSH_5.0p1, OpenSSL 0.9.7l 28 Sep 2006 $ which ssh /usr/bin/ssh sshd is the same version, installed in /usr/sbin/sshd. Now, things are a bit broken: I am able to ssh from another machine into my MacBook, so the
2008 Aug 05
1
rsync problem after ssh upgrade
Hello. In my setup I collected logs from many hosts using ssh + rsync. It worked fine untill I upgraded OpenSSH from version 5.0p1 to 5.1p1 on those hosts running Slackware Linux. After upgrade nothing works as before. When I try to get logs connection breaks with the following message in syslog on the server side: Aug 4 15:34:44 srvhost sshd[8130]: Accepted publickey for user from
2017 Oct 03
2
Announce: OpenSSH 7.6 released
OpenSSH 7.6 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches, reported bugs, tested
2007 Sep 21
0
openssh-4.7p1 & RemoteForward to openssh-3.6.1p2 Disconnecting: Bad, packet length
Hi, I've just upgraded to openssh-4.7p1 on my gentoo box, and I've noticed a incompatibility with openssh-3.6.1p2 running on a redhat AS3 server. If I ssh from my openssh-4.7_p1 client to the openssh-3.6.1p2 server, and RemoteForward a port, the ssh connection closes if I try to send more than roughly 300K through the tunneled port. The problem isn't present when I use openssh-4.6p1
2007 Sep 20
0
openssh-4.7p1 & RemoteForward to openssh-3.6.1p2 Disconnecting: Bad packet length
Hi, I've just upgraded to openssh-4.7p1 on my gentoo box, and I've noticed a incompatibility with openssh-3.6.1p2 running on a redhat AS3 server. If I ssh from my openssh-4.7_p1 client to the openssh-3.6.1p2 server, and RemoteForward a port, the ssh connection closes if I try to send more than roughly 300K through the tunneled port. The problem isn't present when I use openssh-4.6p1
2020 Nov 12
0
run firefox via an ssh tunnel
On Thu, Nov 12, 2020 at 10:02:57AM -0700, S Bob wrote: > On 11/12/20 7:50 AM, Jonathan Billings wrote: > > If this is actually something you want to do with regularity, I > > suggest using the SSH SOCKS proxy (with the DynamicForward port), and > > configure Firefox to use the localhost:port as a SOCKS5 proxy. Then > > all traffic in firefox will be routed over the ssh
2015 Feb 23
2
Call for testing: OpenSSH 6.8
Hi Damien, On Feb 23 10:28, Corinna Vinschen wrote: > On Feb 22 07:59, Damien Miller wrote: > > On Sat, 21 Feb 2015, Corinna Vinschen wrote: > > > - The failing last loop in the "forwarding" script as reported back > > > during 6.7 testing is still failing for me more often than not. It's > > > always the same reason, the script tries to use