similar to: FYI Incompatibilities between recent versions of OpenSSH and Sun SSH

http://bugzilla.mindrot.org/show_bug.cgi?id=738 Summary: OpenSSH 3.7.1p2 Password Authentication Failure Through NIS+ on Non-Master Server Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: PAM support

Hello, I am having a very aggrivating problem, and I will try and provide all of the necessary information. I have openssh-3.7.1p2 with openssl-0.9.6k installed on Solaris 8. Here is what I've been able to determine so far: 1. Local account authentication works fine (non-NIS+). 1a. NIS+ is running at security level 2 2. Telnet authentication works fine. 2a. When I use the SSH client,

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

hi all, we had quite a few requests recently so that SunSSH allowed to hush a banner on client side when in command-mode only. The argument usually is that the banner is mandatory due to legal reasons so first time login users should see it but that it causes problems when ssh is used from scripts after that. '-q' often seems not an option. RFC 4252 permits hushing banner in section

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:

Hello, I just learned this morning about a new patch from Sun for Solaris 8 that adds /dev/random. The patch is based on the device in Solaris 9. I have not tried it yet, but I though some might be interested. The patch is: (this is available for free from sunsolve) Patch-ID# 112438-01 Keywords: secuity random number generator PRNG Synopsis: SunOS 5.8: /kernel/drv/random patch Date: Mar/28/2002

I am running Solaris 8 with the Basic Security Module (BSM) loaded and Sun's Enterprise Authentication Mechanism (SEAM) installed. Our servers are using Sun One Directory Services (LDAP) for authorization and Sun's Kerberos 5 implementation for authentication. We have been using OpenSSH 3.4p1 with OpenSSL 0.9.6f and everything has been working fine. We are updating our OpenSSH and OpenSSL

http://bugzilla.mindrot.org/show_bug.cgi?id=362 Summary: Loss of change password functionality Product: Portable OpenSSH Version: -current Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org

It's great to see this fixed. It's too bad that: a) I didn't have the sense of humor in 2004 to propose KnownUnknowns, and even UnknownUnknowns (a boolean, natch); b) you used a different parameter name than SunSSH (which uses IgnoreIfUnknown). It may not be too late to do something about either of those... I think the Oracle folks will have no problem adding IgnoreUnknown as an

http://bugzilla.mindrot.org/show_bug.cgi?id=813 ------- Additional Comments From alex at milivojevic.org 2005-04-07 04:50 ------- I was doing some testing, and the strange thing is that SunSSH server gives wrong exit status only when using newer versions of openssh on the client side. For example, Red Hat 7.3 as client (openssh 3.1) is OK Fedora Core / RHEL4 as client (openssh 3.9) gives

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

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

http://bugzilla.mindrot.org/show_bug.cgi?id=921 Summary: Add operating system to OpenSSH version string Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org

Howdy: I need some help please to get hiera configuration data derived from YAML, thru puppet. I have studied Internet search results and puppet documentation on create_resources and custom defines but need a little help along. I can print out the YAML from variables, arrays, and, finally, hashes too from a puppet manifest. One thing that is stumping me is how to access from the custom define

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?

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 get the error message "Packet integrity error. (29)" on the server and the session is disconnected. This forwarding setup works with the not-so-free sshd just

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

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