similar to: Permission Denied

Has anyone had success with getting /dev/random to work after installing SUNWski? After I install the pkg and start /etc/ init.d/cryptorand, the /dev/random file remains 0 bytes. I am running Solaris 2.8 - David

I have upgraded my openssh version from 2.2.0.p1 to 3.0.2p1. 3.0.2 was compile on a sunblade 100 running Solaris 8. Is it possible for my to use my existing DSA key? Thanks, David Higdon UNIX System Administrator (503) 450-4800 (Office) (503) 701-5558 (Cell Phone) higdon.david at cnf.com

has anyone noticed a performance gain with protocol 2? -David Higdon

This is my first time installing ssh and I am getting the following error: $ ssh <hostname> The authenticity of host <hostname> can't be established. RSA key fingerprint is <xxxxxxxxxxxxxxxxxxxxxxxxx>. Are you sure you want to continue connecting (yes/no)? David

I have been experiencing problems with remote data collection systems reporting not enough entropy in RNG. It mostly seems to be self correcting since a retry of the data transport succeeds. One system however shows the following everytime an ssh connection is attempted. Interactive commands do not seem to be affected. I have perused the code but the entropy gatherer seems to be fairly simple and

Hi, using OpenSSH_2.1.1 p4 i have problems with X11 forwarding. I used the same sources for Solaris and Linux. Tried nearly every combination, but it seems that the "opensshd" for Solaris has some problems. Of course i tried to connect with "ssh -X", the server has in its /etc/sshd_config: X11Forwarding yes X11DisplayOffset 10 XAuthLocation /usr/openwin/bin/xauth The client

hi everyone, i do have a Redhat7.0 with open-ssh-2.1.1p4-1.src.rpm installed together with openssh-server-2.1.1p4 and openssh-clients in my linux server. i used the default configuration under /etc/ssh/sshd_config. but when i ran ssh -v root at x.x.x.x, it doesn't establish a connection and i have this error: ssh_exchange_identification error what does it mean? and can

I have just tarred up a snapshot and uploaded it to: http://www.mindrot.org/misc/openssh/openssh-SNAP-20000823.tar.gz The snapshot incorporates the last month's fixes and enhancements from the openssh-unix-dev mailing list and from the OpenBSD developers. In particular: - ssh-agent and ssh-add now handle DSA keys. NB. this does not interop with ssh.com's ssh-agent. (Markus Friedl)

I am on Solaris 2.8 with openssh 2.3.0p1 and openssl 0.9.6. The remote machine is running ssh.com 1.2.20 and Solaris 2.6. I think the problem has to do with the 1.2.20 KeyRegeneration, because in the next hour I will beable to get into the machine ok with openssh and then later in the day I will not beable to ssh in again for another hour. ssh -v -v sa at myhost.com SSH Version OpenSSH_2.3.0p1,

Hi people, Please excuse this rather long debug output... $ uname -a SunOS echelon 5.6 Generic_105181-17 sun4u sparc SUNW,Ultra-Enterprise $ /usr/local/openssh/bin/ssh -v x.x.x.x SSH Version OpenSSH_2.1.1, protocol versions 1.5/2.0. Compiled with SSL (0x0090581f). debug: Reading configuration data /usr/local/etc/ssh_config debug: Applying options for * debug: ssh_connect: getuid 1002 geteuid 0

i do have a Redhat7.0 with open-ssh-2.9 installed together with openssh-server-2.9 and openssh-clients in my linux server. i used the default configuration under /etc/ssh/sshd_config. but when i ran ssh -v root at x.x.x.x, it doesn't establish a connection and i have this error: ssh_exchange_identification connection closed by remote host. i'm using secureCRT3.3 on my

Hi all, I have noticed a problem with the newly released version 2.1.1p4 (as well as with 2.1.1p3) : If sshd is run from inetd, all interactive sessions are automatically closed right after (successful) login. The problem disappears, if sshd is run from the command line (ie. no -i option) and did not exist in 2.1.1p2. This was noticed on a linux x86 box. I have appended a typescript of the

I have been unable to use the Banner option in the sshd_config for the verision of openssh I am using: # ssh -V SSH Version OpenSSH_2.1.1, protocol versions 1.5/2.0. Compiled with SSL (0x0090704f). Here is what I get when I have the entry "Banner /etc/issue" in the sshd_config: starting SSHD daemon # /usr/local/etc/sshd_config: line 21: Bad configuration option: Banner

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

I just upgraded my Windows SSH client from the 2.1.x version (whatever it was) to 2.2.0 and am now experiencing difficulties connecting to my OpenSSH-2.1.1p1 Linux servers. I'm not as up-to-speed as I should be on the inner workings of the handshakes that go on, but from the debug logs and from trying different connection methods, it seems to be isolated to using publickeys. This

I wasn't sur if you're the right person to send the bug reports to... SCO Unixware 7.1.0 (uname: UnixWare) and probably the 2.1.x versions (uname: UNIX_SV) requires also to have USE_PIPES defined. Also when compiling with tcpwrap it doesn't link due to the fact that UW doesn't have setenv() and libwrap have one built-in (duplicate symbols)... Also when using the SSH2 protocol to

Hello again, I was testing today's SNAP (openssh-SNAP-20000830.tar.gz) in my Solaris 2.6-8 environment, when I found some problems with the ssh2 support. While connecting, it seeds the RNG something like 32 times! And then once connected, it seeds again 2 or 3 times with *every* keystroke! This makes for some slow going. This happens on all of the Solaris boxes I tried. Binary was

On Thursday, April 5, 2001, at 02:09 , Theo de Raadt wrote: > please mail details about the bugs asap. The first bug I sent (pending/1759: 2.5.2p2 can't connect using protocol 2 to a 2.3.0p1 server), got sent back as "fixed in current" so hopefully that is taken care of (details at the bottom of this message). I'm happy to try and repro / debug these if necessary. The

Just today I compilied openssh-2.1.1p1 on Debian Slink and Potato both to come out with the same problem. I am compiling them with openssl-0.9.5a.. The configure line I use for openssh is below: ./configure --sysconfdir=/etc/ssh --prefix=/usr --with-ssl-dir=../openssl-0.9.5a So I compile, do a make install restart the sshd daemon and everything seems fine. Then when I do a w at the prompt

Hi, I have the following problem: I have two computers. On the first RedHat 6.2 (Openssh 2.1.1) is installed. The second is an PC with Windows NT 4.0 (SP 6) with Cygwin and Openssh 2.1.1p4. The X-Server running on the WinNT machine is Hummingbird Exceed 6.1 . I have activated X11-Forwarding in the config-files on both machines. I'm sitting in front of the WinNT machine and want to do a