similar to: FreeBSD 4.0 and openssh 2.1.0p3

On Thu, Jan 13, 2000 at 17:34:10, Andre Lucas wrote: > Subject: /dev/urandom > On Thu, Jan 13, 2000 at 09:24:01AM -0700, SysProg - Nathan Paul Simons wrote: > > On Thu, 13 Jan 2000, Ben Taylor wrote: > > > > > On Thu, 13 Jan 2000, Max Shaposhnikov wrote: > > > > why ssh1.27 doesn't requre /dev/urandom on solaris? > > > > i think the

Further to my original question about PAM on OpenBSD for OpenSSH, it may be non-trivial to get any PAM stuff onto OpenBSD (Thanks to Ben Lindstrom for his suggestion, which I'll try, using a gnu/loonucks PAM package, any suggestions for which one to use, or where to get it from? I'm not very clueful when it comes to GNU/linux). So, I remember in a past life hacking suport for other auth

I have a need to set up an ssh login server that groks both ssh1 and ssh2. I'm trying to build openssh-2.1.0p3 on NetBSD 1.4.2. Configure fails when it tries to build the test program conftest. It's not obvious fron config.log exactly what is going wrong. Has anyone built that latest openssh under NetBSD 1.4.2? Thanks in advance. -- Rick Kelly rmk at rmkhome.com www.rmkhome.com

I'd like to install openssh across an Irix cluster where I work, but its dependency on an "entropy pool" like /dev/urandom is making this problematic -- especially because EGD has issues with Irix that making it largely unusable. Obviously, the original ssh relied on its own random number generator. While this may not have provided the same degree of randomness that is provided by

Is this bug? % runsocks ssh HOST.DOMAIN.COM Segmentation fault (core dumped) My environemnt: Solaris2.6 for Sparc gcc-2.95.2 perl.5.005_03 openssl-0.9.5a zlib-1.1.3 egd-0.7 socks5-v1.0r10 (`runsocks' is a tool in it.) --- entropy.c.ORIG Tue May 30 18:34:31 2000 +++ entropy.c Tue May 30 18:49:45 2000 @@ -82,8 +82,6 @@ c = atomicio(read, egd_socket, buf,

Yo All! Sorry if this is obvious but I am new to openssh. I have used the original ssh for a while and am familiar with it (and it's restrictive license). I am trying to port openssh-1.2.1pre24 on to SCO UnixWare 7.1.0. I will post the small patches when it is really running. Two problems, SCO has no /dev/random so I installed egd-0.6. It usually works but sometimes dies. I have sent

Hi all, I have just successfully ported openssh-2.1.0p3 to Cygwin. As you may know, Cygwin is a GPLed POSIX layer for Windows OSes. To be serious: I don't _like_ Windows systems and sometimes I really hate that STUPID concessions which are necessary when trying to get U*X software working on Windoze but for some reason that's exactly the reason, why I love to work on Cygwin! Porting to

Hi, when running OpenSSH with EGD as entropy source, the sshd server connects to the EGD socket and leaves it open to re-seed on the fly. Unfortunately the connection is not checked when re-seeding, so that a failure or restart of EGD will lead to a "fatal()" abort of the sshd server process. Since a dying server process can not be accepted, I would recommend to not have sshd call it

I have just uploaded a test release of portable openssh to http://violet.ibs.com.au/openssh/files/test This release includes some major changes picked up from OpenBSD CVS. It also includes inbuilt random number gathering support which should remove the need for EGD on systems that lack /dev/random. This support is very preliminary. Please treat it as alpha and don't use it on production

Regarding /tmp/random: Someone has made the same quick&dirty fix as my AIX compile fix, for a lack of /dev/urandom. ssh expects some random bytes to be available in that file. I, or someone else should probably create a more portable way of generating entropy. ;) //Tor-?ke >From: Niels Provos <provos at outguess.org> >To: openssh-unix-dev at mindrot.org >Subject: Fwd: Re:

The 2.1.0p2 and 2.1.0p3 RPMS try to fall back to the r* commands in /usr/kerberos/bin. I'm not sure under which distribution that path is valid, but it just gives an error on my machines (RedHat 6.1 and 6.2). It's no big deal to tweak the SRPM and build my own packages, but it does make me wonder if the fallback path should be configurable. -- Jason L Tibbitts III - tibbs at uh.edu -

My ISP supports connections via ssh. I was using OpenSSH 1.2.3 (portable) on Solaris 2.5.1 (with EGD), and I could connect to my ISP just fine. They're using the proprietary sshd version 1.2.26 as far as I can tell. A connect session looks like: $ ssh-1.2.3 -v -l foobar xx.xx.xx.xx SSH Version OpenSSH-1.2.3, protocol version 1.5. Compiled with SSL. debug: ssh_connect: getuid 390

Morning all ... using the following command to sync up the binaries on several machines: rdist -P /usr/slocal/bin/ssh -Rf /root/sync-systems generates the following error message(s): jasper: updating host jasper hermes: updating host hermes attila: updating host attila hercules: updating host hercules ".rcules: LOCAL ERROR: Unexpected input from server: "Couldn't initialise

Hello, I have just installed a fresh copy of FreeBSD 4.0-RELEASE on a P75, and want to compile openssh-2.1.1p2, but the compile fails with: gcc -g -O2 -Wall -I/usr/local/ssl/include -DETCDIR=\"/usr/local/etc\" -DSSH_PROGRAM=\"/usr/local/bin/ssh\" -DSSH_ASKPASS_DEFAULT=\"/usr/local/libexec/ssh/ssh-askpass\" -DHAVE_CONFIG_H -c loginrec.c loginrec.c: In function

Hello, while openssh-1.2.1pre25 ran out-of-the box, in openssh-1.2.1pre27 the sshd fails to start with: "Host not found" returned... (gcc 2.9.5.2 under AIX 4.3.2 ML 2) Incompatibility of AIX-getaddrinfo ???? Since I'm not familiar with getaddrinfo, I've got no idea what goes wrong ??? Does the code below work on other architectures? Demo-Code built with values taken from a

I've got a problem that I'm hoping the list can help with, otherwise ... Heres the problem, I've got OpenSSH 1.2.2p1 running on my Intel Linux box as the secure server. I can connect from another Intel Linux box using scp and it all seems to work fine. Another box tries to connect and it gets a warning about the host keysize not matching. I'm thinking this could be some byte

Greetings, While attempting to build openssh for Solaris 2.6, I ran into a minor problem that should probably be corrected in the next release of openssh. The file pty.c does not #include <stropts.h> to define I_PUSH even though I_PUSH is used when HAVE_DEV_PTMX is defined. Platform: SunOS test01 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-60 Using: zlib 1.1.3

Hello, I used the sshd under SCO 5, and always get the error that the deamon couldn't allcoate a pseudo tty. This depends on that SCO use a different method to create the tty's in the /dev directory. The pseudo tty line looks like: /dev/ttypXXX where XXX depends on the number of pseudo tty's entered in the scoadmin Tool for the network interface. So I change the allocation routine in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple of silly errors, and one dangerous bug were in the pre26 release. This release corrects them. http://violet.ibs.com.au/openssh/files/openssh-1.2.1pre27.tar.gz If you want RPMs or any of the other files, please use a mirror: http://violet.ibs.com.au/openssh/files/MIRRORS.html Changes: - Using __snprintf is *NOT SAFE* on old Solaris.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple of silly errors, and one dangerous bug were in the pre26 release. This release corrects them. http://violet.ibs.com.au/openssh/files/openssh-1.2.1pre27.tar.gz If you want RPMs or any of the other files, please use a mirror: http://violet.ibs.com.au/openssh/files/MIRRORS.html Changes: - Using __snprintf is *NOT SAFE* on old Solaris.