similar to: Packet integrity error. (29)

I just installed the 1.2pre15 RPMs and, as hinted in the announcement, it fixed this problem. Thank you! _______________________ Ron Bickers ===== ORIGINAL POST ===== I'm using SecureCRT (http://www.vandyke.com/) to connect to OpenSSH (1.2pre14 built from source RPMs) running on RedHat Linux 6.1. When I forward a local port using SecureCRT to a port on the server and try to connect, I

Hi guys, OpenSSH 2.9p1 using SSH2 currently caches the username sent in the USERAUTH_REQUEST [none] packet. This does not allow you to change the username in a later authentication packet. >From SSH Authentication Protocol, section 2.1: "The user name and service are repeated in every new authentication attempt, and MAY change. The server implementation MUST carefully

Sorry...I deleted the thread about SOCKS before I realized I knew the solution... I checked up on how SMB connections work on an NT workstation running the Hummingbird SOCKS proxy. It looks like "net use..." and its GUI variant don't use the WINSOCK/WINSOCK 2 interface to make netbios-session (139/tcp) connections. The machine attempted to make a direct connection to the remote

So this has been bugging me for a few years now and I can always "fix" the problem, but I don't know if that's actually the correct way. So the issue is terminal emulation. I use Secure CRT (vandyke.com) to connect to any and all of my servers through SSH. Whether the terminal is set to 'linux' or 'xterm' makes no difference, I always get this output when I run a

Hi, I am using Van Dyke SecureCRT 3.2.1 to access an AIX server running OpenSSH-2.5.0p1. Using ssh1 with X11 forwarding enabled, the server reports the following error (in the client session): Packet integrity error. (34) This problem was not evident in 2.3.0p1. Running sshd in debug gives the output: debug1: sshd version OpenSSH_2.5.1p1 debug1: load_private_key_autodetect: type 0 RSA1

Hi, I installed Wine 0.9.4 package for Suse 10 and configured it with WineTools 0.9.3jo. Internet Explorer 6 and other Windows software installs and run fine. I have a problem running SecureCRT (version 5.0.0 and 5.0.4). I used the suggestion found in the application DB, i.e. installing with version=winxp and run it with version=win98. The installation run fine but when I run the application

Client - secureCRT 3.3 outside the firewall (Checkpoint) Server - openssh v3.7 on an aix51 rs6k inside the fw The firewall lets in the first packet but blocks the second with the message: ssh 1.x not allowed. The connection gets reset. Here is the trace from the client: [SSH LOCAL ONLY] : Connect: 12.x.x.x:22 [direct] [SSH LOCAL ONLY] : StateChange:

I was directed to the following site by one of our customers regarding a keyserver built into openssh. There's a patch for 3.4p1 on their site, but the license isn't very clear, nor is it clear if they have approached the openssh team regarding the inclusion of this subsystem into openssh proper. I've been asked to patch Mandrake's openssh with this feature, but I'm

Hello all. I have been searching the web for a formula to get openssh and securecrt ssh2 keys working properly. Does anyone have a set of directions? I have attempted creating keys in securecrt and converting them (ssh-keygen) to OpenSSH keys. I have attempted using OpenSSH's keys, but nothing seems to take. Any advice will help. Thank you. OpenSSH v3.8 SecurCRT v4.1.7 -g

Good day, I have installed the latest version of wine with yum on Fedora Core 10. I have installed the latest stable version of securecrt 6.1.4. All goes well. I start up securecrt and log onto a session it asks for a username and then hangs? Anyone got any ideas? Thanks leon

Hello, We are having issue with SFTP for Windows server. The OpenSSH reports the "Exit Staus -1" upon exiting the sftp session ( Though the file is successfully getting transferred!!). I have opened ticket with VanDyke Software - vShell and reported this issue. Accordiong to VanDyke Software, there is no issue with vShell configuration / its debug logs. Would you

http://bugzilla.mindrot.org/show_bug.cgi?id=669 Summary: Putty / SecureCRT connections fail to authenticate Product: Portable OpenSSH Version: 3.7.1p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=648 Summary: Cannot login using SecureCRT since openssh 3.7p1 Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've seen a few posts, but no solutions as of yet. Here's a bit more info. BoxA - Solaris 2.7, Maintenance Update 01/09/2001, SunWorks cc compiler BoxB - Solaris 2.8, gcc-2.95.2 gcc compiler BoxC - Solaris 2.7, Maintenance Update 01/09/2001, gcc-2.95.2 gcc compiler BoxD - OpenBSD 2.8, patched to STABLE, gcc-2.95.2 _and_ BSD cc compilers

hi, i don't understand how 3.6.1p2 breaks ssh1.... On Fri, Sep 12, 2003 at 10:27:15AM -0700, Mike Bethune wrote: > Hello, > the new way this works breaks windows ssh clients using v1 (I know, who cares :) > since when these options are enabled and you connect w/v1, the server asks: > Password: > Response: > and I guess these clients (tested putty, pscp, vandyke) expect

Hi, I have a problem with SecureCRT (6.2.2) telnet session. The first line in the telnet session don't refreshing. I tried 1.1.28-29 release but still have a same problem. all lines are scrolling well, but the first is not. I tried to resize the screen and change settings but nothing happened. Is it a bug or I forgot to set something?

Jeff Van Dyke's "Public Key Assistant subsystem" was previously discussed here: (end of a short thread) http://marc.theaimsgroup.com/?l=openssh-unix-dev&m=103436908422003&w=2 I do see a few comments that seem to point out his arrogance and some disgust about OpenBSD's RCSID, but has anybody found it to be unsecure or if it was bug ridden. The subject sorta dies right

http://bugzilla.mindrot.org/show_bug.cgi?id=259 Summary: UsePrivilegeSeparation crashed sshd under Linux 2.2 Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org

root at ns2:~# sshd -D -dddd Too high debugging level. root at ns2:~# sshd -D -ddd debug1: sshd version OpenSSH_3.3 debug3: Not a RSA1 key file /usr/local/etc/ssh_host_rsa_key. debug1: read PEM private key done: type RSA debug1: private host key: #0 type 1 RSA debug3: Not a RSA1 key file /usr/local/etc/ssh_host_dsa_key. debug1: read PEM private key done: type DSA debug1: private host key: #1 type

These problem aren't bugs per se but rather major version differences. Sun has finally published a FAQ on their SSH two days ago http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=finfodoc%2F50465&zone_32 =sshd The problem is rooted in the fact that Sun developed their SSH based on OpenSSH 2.5.1p1 That version came out in February of 2001. There have been a number of changes since then and