similar to: Couldn't obtain random bytes

Hi there, I have a weird problem with OpenSSH 2.9.9p2 on Solaris 8. Whenever I try to use ssh, scp or sftp to connect to the Solaris box, the connection is closed by the server and the following msg logged thru syslog: "sshd[542]: fatal: buffer_get: trying to get more bytes 129 than in buffer 39" I tried from an RH 7.1 client (2.9.9p2), from a Solaris 8 client (2.9.9p2), and an OpenBSD

Hi there, at a school I have two servers and I created a little backup "system" for them. A cron job runs on the first server (fserver), backs stuff up there and then ssh's to the second server to run a backup script there too. (the first server is located in internal network, the second in a DMZ). When I tried everything on console, it worked fine, but when run from cron, the

I just upgraded openssh on my Solaris 8 boxes from 2.9p2 to 2.9.9p2, and scp has stopped working. Remote logins with ssh do work, though. Both client and server run 2.9.9p2. Please let me know if you need more information (configure options, config files etc.). I'm not on the list, so CC's would be appreciated. Thanks! $ scp vsftpd-0.9.2.tar.gz user at server:/usr/local/src/misc/ftp

Hi I think there is a problem is OpenSSH_2.9.9p2. Suppose I have in /etc/ssh/ssh_config just this and nothing more: Host * ForwardX11 yes and in ~/.ssh/config: Host * ForwardX11 no ssh -v tells they are read ok: debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Reading configuration data /home/kaukasoi/.ssh/config debug1: Applying options for

Here's the appropriate output with blow-by-blow explanation embedded... I start by making a connection with X11 forwarding enabled: polycut:~> ssh -v -v -v -X dazel OpenSSH_2.9.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /opt/openssh-2.9.9p2/etc/ssh_config debug3: Reading output from 'ls -alni /var/log' debug3: Time elapsed: 23 msec debug3:

We use OpenSSH 3.5p1 on an embedded system. OpenSSH is configured to not permit password logins, /etc/ssh/sshd_config: ... PasswordAuthentication no ... At the same time, since there is no console and no way to "log in" other than by ssh, /etc/passwd has an "open" root account: root::0:0:root:/root:/bin/sh nobody:x:65534:65534:nobody:/tmp:/usr/bin/bash Apparently

Hello, I have discovered a slight problem with MS-Project4 on a WinDD server, where users are not able to update the *.MPP file. We have all data files stored on a UNIX box, using samba-2.05a, on an RS6000 running AIX 4.2.1, so all *.MPP files are stored there, with the proper UNIX user's userid and permissions. The problem is that userB can not update and save changes in a file that userA

Hello, I have discovered a slight problem with MS-Project4 on a WinDD server, where users are not able to update the *.MPP file. WinDD is Citrix Metaframe on Windows NT 3.51. We have all data files stored on a UNIX box, using samba-2.05a, so all *.MPP files are stored there, with the proper UNIX user's userid and permissions. The problem is that userB can not update and save changes in a

Hello. I've recently switched to OpenSSH from the other ssh's. When I ssh into to a box one at a time, it works fine. However when I want to connect 4 times quickly, none of them ever connect. ie: Doing this four times: xterm -e connect-to-box1 & ssh -v shows the following: It gets to this part on EACH terminal and it hangs forever. ssh -v -l war thebox.com OpenSSH_2.9.9p2, SSH

Not sure which list this should go to, so I'll include both. When I SSH from a 2.9.9p2 client to a OpenSSH 2.1.1 server, it often hangs at this point. It will hang there for days on end. If I open up 9 xterms and run that command, 2-3 will login. I have no problems using ssh1 (commercial). And openssh has no problems logging into newer servers > 2.1.1. Anyone know why this might be?

Hi all, I want to use ssh to protect my traffic, no rsh or direct rsync. But I have a problem here. Of the texts already written, I could not yet recall. Mostly they tell about success in using ssh protocol. I have made some progress by reading them, but I cannot solve the current problem, if not possibly turning to port forwarding, that is also new to me, actually. I have made two kind of

I am running two Red Hat 6.2 servers with the 2.2.16 kernel. I am running OpenSSH_2.9.9p2 (SSH proto 2) and OpenSSL 0.9.5a 1 on both with no problems. I am having problems upgrading to OpenSSH 3.0.2p1 on both systems. After doing a gnu make installation, ssh works fine, but sftp displays fourteen digit numbers instead of file names when you do an ls listing of directory contents. File transfers

When I run a remote xterm, the ssh hangs even after I quit the xterm. Below is the output for the following sequence: client> ssh -v -v -v dazel xterm xterm> exit client> ^C The outcome is always the same - the ssh doesn't exit with I quit the xterm... I have to hit CTRL-C on the client side. polycut:~> ssh -v -v -v dazel xterm OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL

I ran into a weird problem yesterday where Putty can't connect to my OpenSSH/Sol box (and still can't ever since). On the Putty side I get the error message: "internal fault: chaos in SSH 2 transport layer" I've attached the "sshd -d -d -d" syslog output. Any ideas what's going wrong here? From a layman's point of view, it would appear that Putty and

I've recently upgraded some of my machines from an ssh1 environment to an openssh one, and consequently, I'm now using the ssh2 protocol. I can't seem to get it to allow remote logins without prompting for a passphrase or password. Is this possible? I've created id_dsa and id_rsa files etc., using ssh-keygen and have copied the public information to the remote authorized_keys

Hi, There seems to be a problem with the arc4random code on mips/mipsel, producing the following error message: Couldn't obtain random bytes (error 604389476) To quote the bug submitter: "On mips and mipsel, the above error message is frequently seen when calling ssh with a command, usually several times in rapid succession, although that is not always the case. The error appears to

http://bugzilla.mindrot.org/show_bug.cgi?id=231 Summary: ssh-keygen has fatal error while updating comment in RSA1 key Product: Portable OpenSSH Version: 3.1p1 Platform: HPPA OS/Version: HP-UX Status: NEW Severity: normal Priority: P2 Component: ssh-keygen AssignedTo:

Hello Samba, ???????, 30 ??????? 99, you wrote: sso> SAMBA Digest 2359 sso> For information on unsubscribing see http://lists.samba.org/ sso> Topics covered in this issue include: sso> 1) Re: Unix .TXT vs DOS .TXT files sso> by Gerry Creager N5JXS <gerry@cs.tamu.edu> sso> 2) Switching user share on NT and smbd spawning sso>

The hang-on-exit bug still hasn't been fixed in OpenSSH-3.0p1... :-( Here again is the patch to fix this bug under Linux, updated for OpenSSH-3.0p1. This has been exhaustively tested for six months now. It also add an exit delay option that can be useful. The patch does not lead to data loss under Linux. Please see the Secure NFS page (SNFS) for further details:

Hello, I am trying to use rsync (version 2.5.5) in a server client model to distribute software files. When I kick off the rsync client on an AIX 4.3.3 pwr3 platform, I get the following error message. We are in a real bind to get this protocol going; any help/insight/suggestions would be "greatly" appreciated. rsync: getaddrinfo: grp4c 873: Host not found rsync error: error in