similar to: openssh code

Using OpenSSH_8.3p1 I had an open (working) connection to some other box; after a bit of inactivity, some device in the middle seems to have forgotten about the TCP connection (NAT) and broke it. I've got an EscapeChar defined, though; so first I tried to send a BREAK and, when that didn't help (TCP already gone, packets get lost!), I tried (just out of curiosity) a Rekey. Now I can see

http://bugzilla.mindrot.org/show_bug.cgi?id=52 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |1274 nThis| | ------- You are receiving this mail because: ------- You are the assignee for

The 4.6p1 sshd is logging this error during remote commands or file transfers: error: channel 0: chan_read_failed for istate 3 Platform is Solaris 8, 4.6p1 + OpenSSL 0.9.8d. The commands and transfers work correctly, so the error message appears to be spurious. The error message does not appear when processing logins. Otherwise 4.6p1 is running without any apparent problems. This error

Hi OpenSSH developers, I am using openSSH (now 2.9.9p2, but prob occurs in 2.9p2 also) to execute commands on a remote machine which outputs data to stdout then pipes it to another invocation of ssh which connects back to the first machine in the same way, where it starts a program to read and store the output from the command on the second machine. I am using the "command" option in

Here are some patches to re-enable support for AIX's authenticate routines. With them, ssh will honor locked & unlocked accounts, record successful and unsuccessful logins, and deny accounts that are prohibited to log in via the network. Tested with AIX 4.3. It also includes a fix for handling SIGCHLD that may be needed for other platforms (HP-UX 10.20, for example). If I get the time

I'm using OpenSSH-2.9.9p2 on Solaris 8 sparc64. 2.9p2 worked fine, but 2.9.9p2+ is giving me trouble with one thing - sshd segfaults if I try to connect and execute a command, such as "ssh machine ls". Otherwise it works great. sshd will fork, and the child process segfaults. CVS snapshot does the same thing. I've narrowed this down somewhat. It will only happen if you use

On Tue, Jun 11, 2024 at 1:24?PM Opty <opty77 at gmail.com> wrote: > On Wed, Jun 5, 2024 at 3:14?PM Opty <opty77 at gmail.com> wrote: > > On Wed, Jun 5, 2024 at 6:03?AM Damien Miller <djm at mindrot.org> wrote: > > > We need to decide whether to promote these log messages to INFO. > > > > > > [...] > > > > I will wait for the final

Hello, In response to the timing analysis attacks presented by Dawn Song et. al. in her paper http://paris.cs.berkeley.edu/~dawnsong/ssh-timing.html we at Silicon Defense developed a patch for openssh to avoid such measures. Timing Analysis Evasion changes were developed by C. Jason Coit and Roel Jonkman of Silicon Defense. These changes cause SSH to send packets unless request not to,

On Wed, Jun 5, 2024 at 3:14?PM Opty <opty77 at gmail.com> wrote: > On Wed, Jun 5, 2024 at 6:03?AM Damien Miller <djm at mindrot.org> wrote: > > On Sat, 1 Jun 2024, Opty wrote: > > > Indeed I am. > > > > > > What now? > > > > We need to decide whether to promote these log messages to INFO. > > > > > Should PuTTY change its

Hello, In response to the timing analysis attacks presented by Dawn Song et. al. in her paper http://paris.cs.berkeley.edu/~dawnsong/ssh-timing.html we at Silicon Defense developed a patch for openssh to avoid such measures. Timing Analysis Evasion changes were developed by C. Jason Coit and Roel Jonkman of Silicon Defense. These changes cause SSH to send packets unless request not to,

Hello, The error message in the subject line occurs with the new 2.3.0 openssh version and appeared in the previous snapshots on our Solaris systems. As far as I remember it was reported, but have not seen any more about this. I have looked into it a little bit. First, the file session.c (line 1849 onwards): debug("session_exit_message: release channel %d", s->chanid);

On Fri, 14 Jun 2024, Opty wrote: > On Tue, Jun 11, 2024 at 1:24?PM Opty <opty77 at gmail.com> wrote: > > On Wed, Jun 5, 2024 at 3:14?PM Opty <opty77 at gmail.com> wrote: > > > On Wed, Jun 5, 2024 at 6:03?AM Damien Miller <djm at mindrot.org> wrote: > > > > We need to decide whether to promote these log messages to INFO. > > > > > >

While looking for leaks I came across two old packet APIs which are easy to remove. I'm sending patches for each separately. First, there is the packet_set_connection(int fd_in, int fd_out) function in opacket.c The function relies on a behavior in ssh_packet_set_connection() where, when it is passed a NULL pointer, it will implicitely allocate a struct ssh and return it after then set

http://bugzilla.mindrot.org/show_bug.cgi?id=160 ------- Additional Comments From Nicolas.Williams at ubsw.com 2002-03-13 09:10 ------- Created an attachment (id=40) Debug output, lsof output, etc... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Hi, I met some difficult in reading ssh/sshd souce code, I want to find out how the command that user input in client is executed on the server. I only found out the process_input function put the command in a buffer,but can not find how it is executed. Could you please help me on that? Thank you very much. B Rgds, Kexin

Hi, I'm a newbie to openssh and was trying to read the source code recently. Could anyone tell me why in sshd the connection_in and connection_out are the same(seems to be integer 3 in my machine). connection_in is used in process_input(readset), and connection_out is used in process_output(writeset); But how does it work if it tries to read and write from the same file descriptor? /Bob

On Fri, 31 May 2024, Opty wrote: > > 9.3p2, 64-bit Slackware 15.0 package which uses two patches but they > > look LogLevel-safe to me, you can check at > > http://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/source/openssh/ > > 9.7p1 built from source without TCP wrappers and still no 'Connection > closed' at 'LogLevel INFO'. You might be

http://bugzilla.mindrot.org/show_bug.cgi?id=615 ------- Additional Comments From dtucker at zip.com.au 2003-09-06 12:51 ------- Created an attachment (id=387) --> (http://bugzilla.mindrot.org/attachment.cgi?id=387&action=view) Move libgen test after dirname test Looked at this again, I think the reason it's not working is libgen has already been detected before the dirname test,

I have a strange problem with sshd (from openssh-2.9p2) on Solaris 7. My shell is bash. When I open an ssh session , and type a Control-C to bash's prompt, the shell hangs. (But, if I for instance run "sleep 10" (during which time the pty is in cooked mode) and press Control-C, the sleep command is interrupted quite normally, and the bash prompt returns.) Adding some debugging

This to announce a test release of 2.1.0p1 before making it widely available. This release includes many fixes to problems reported over the last week. In particular: - spurious error and coredumps caused by the inbuilt entropy gathering - RSAref detection - Compilation fixes for Solaris and others It also contains (completely untested) support for compiling without RSA support. This may be