search for: flugstad

...king that the private key is valid, but I would expect that this would be uncovered when the SSH server attempts to verify the signature? Anyone got a clue on how this is working, or am I just getting lucky on which part of the SSH private key I corrupt is not used for the signature? Thanks, Pete Flugstad

Hi, I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am connecting from a ssh client (openssh-2.9p2) on an x86 Linux box. This works fine for ssh protocol version 1, but am getting the below error for ssh v2: Disconnecting: Bad packet length -857542839. I am also attaching the complete debug traces from sshd & ssh below. I am not sure if this is an "endian" issue.

I think I've found two minor memory management issues (neither exploitable in any way) in OpenSSH 3.7.1p2 that should probably be addressed. In serverloop.c, function server_input_channel_open(), the ctype variable is a char *, dynamically allocated in packet_get_string. It's xfree'd at the end of the function. However, before that, it's passed to

Hi, I'm seeing problems with an NT box accessing Samba 2.0.6 running on NetBSD 1.3F. The exact same setup accessing Samba 2.0.5a running on NetBSD 1.4 works just fine. Specifically, I have one of the shares mapped to a drive letter on the NT box and when I use NTEmacs to open a file on the share, it takes upwards of a 60 seconds to open the file. During this time, the smbd process