similar to: Will OpenSSH fallback to internal PRNG?

I upgraded from OpenSSH_3.0.2p1 to OpenSSH 3.4p1. Starting SSHD or ssh-keygen I'm getting the "PRNG is not seeded". I have verified that prngd is running and "egc.pl /var/spool/prngd/pool get" runs just fine reporting 32800 bits of entropy. My platform is Solaris 8 (sparc) and I downloaded binaries from www.sunfreeware.com. My guess is the build of OpenSSH 3.4.p1 is

Just for peace of mind, can someone who knows the openssh code better than I do, confirm that openssh doesn't use (in any circumstances) the openssl prng (since the code in versions prior to 0.9.6b is rather weak). My understanding is that it doesn't (using either /dev/random, egd, prngd or the builtin code), but I may have missed some other use of the openssl prng elsewhere... -- Jon

Hi when i restart sshd I get PRNG is not seeded # /etc/init.d/sshd restart PRNG is not seeded # No idea as what is going on Thanks and Regards Kaushal

Hi all Am i doing this right? Is this the right list to post to? If not, a quick lesson in ettiquette for me would not hurt. As I am both just starting to use newsgroups and SSH, I am not entirely familiar with the processes. I have a question about ssh-rand-helper. First an outline: I am currently using the SSH packages for Solaris 2.8 available at sunfreeware.com. The environment is

http://bugzilla.mindrot.org/show_bug.cgi?id=968 Summary: OpenSSH 3.8p1 PRNG seed extraction failed error Product: Portable OpenSSH Version: 3.8p1 Platform: UltraSparc OS/Version: SunOS Status: NEW Severity: major Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org

Over the holidays, I intend to finally rid portable OpenSSH of the builtin entropy collection code. Here's what I intend to do: When init_rng is called, we'll check OpenSSL's RAND_status(). If this indicates that their PRNG is already seeded, we'll do nothing. This effectively detects platforms which have /dev/urandom (or similar) configured into OpenSSL. If OpenSSL isn't

[NOTE: I'm new to this list and this is my first approach to OpenSSH code.] I've enhanced "--with-prngd-port=PORT" flag to accept an optional hostname as in "myhost:myport", e.g.: % ./configure --with-prngd-port=example.com:12345 Although I'm certain that this may cause big trouble if remote gatherer isn't online (ssh will refuse to open any connection) I

This is likely a linux or ssh problem, but perhaps someone else on this list may have encountered it. I have run about 15,000 instances of rsync in the last year, (about 500 total hours of rsyncing) using ssh as a transport mechanism ( actually, I am running the dirvish backup wrapper, www.dirvish.org, around rsync). In all cases, I am pulling filesystems from a linux client to a linux backup

Hello all, I tried OpenSSH versions 2.1.1p4, 2.2.0p1 and the latest snapshot briefly on 64-bit Irix 6.5.7f an 6.5.9m. Both times, no matter what I do, I'll get 'PRNG initialization failed -- exiting'. This happens with ssh-keygen (the keys aren't even generated yet, ssh binary etc.) It's clear that Irix etc. don't have a proper entropy pool like *BSD and Linux do, but

I have successfully compiled OpenSSH 3.1p1 for the following systems: Solaris 8 Solaris 7 Irix 6.5.14 Irix 6.5.4 SunOS 4.1.3_U1 Unfortunately, the new sshd is not working on any of the above systems with the exception of Solaris 7. (I then put the Solaris 7 executables on Solaris 8, and they worked there too.) This is the error I'm getting: $ /usr/etc/sshd -D -d -d -d debug3: Seeing PRNG

So I decided to dump Samba 2.2.0 on Solaris 8 due to the problems I had getting it to connect to Vista, so I installed Samba 3.4.2 as downloaded from Sunfreeware.com, with prereqs; krb5-1.7-sol8-sparc-local openssl-1.0.0-sol8-sparc-local libgcc-3.4.6-sol8-sparc-local popt-1.14-sol8-sparc-local libiconv-1.13.1-sol8-sparc-local readline-5.2-sol8-sparc-local

Heya, I have compiled and installed OpenSSH on a Solaris/Sparc machine and whenever I try to start any of the ssh programs I get "fatal: PRNG initialisation failed -- exiting" Now, I have looked through the mailing lists and have seen some mention that this indicates it can't open the ssh_prng_cmds file, which entropy.c also seems to indicate the problem is. However, this snippet

hi I am using Solaris 8 and installing the 3.8 openssh software that I received from www.sunfreeware.com I following the installation instruction see attachment but when I get to ssh-keygen -t rsa1 -f /usr/local/etc/ssh_host_key -N "" I get a PRNG is not seeded could you help me in this matter. Thank you for your cooperation. Spencer Crim

http://bugzilla.mindrot.org/show_bug.cgi?id=328 Summary: starting sshd yeilds PRNG not seeded Product: Portable OpenSSH Version: -current Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P1 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

I just upgraded to Solaris 8, and downloaded the the following binary package from www.samba.org <http://www.samba.org> : samba-2.2.7-sol8-suncc-64bit.pkg.gz When trying to gunzip it, here is my output: /home/ccampbell # gunzip samba-2.2.7-sol8-suncc-64bit.pkg.gz gunzip: samba-2.2.7-sol8-suncc-64bit.pkg.gz: not in gzip format /home/ccampbell # file samba-2.2.7-sol8-suncc-64bit.pkg.gz

I did this as a project back in the early 2002, and I had a nice little how-to to walk me through it. Many work places and moves, and I've lost it. I have a friend who asked me about this recently, and I can't seem to find anything on the web, or the how-to I used (not surprised). If I remember correctly, you needed an up-to-date zlib, egd (or prng), OpenSSL, tcpwrappers, and OpenSSH.

Hello! I am running openSSH 2.9x on an IRIX 6.5.x platform. This was recently installed using SGI-supplied "freeware" binaries. I find that as time goes on, it takes more attempts to establish an ssh connection from the IRIX platform to another machine, as it fails with "not enough entropy in PRNG." I posted a note asking for assistance, and received a reply suggesting I

Hello everyone! I work for a company that uses OpenSSH to remotely support systems we've sold. Since some of our clients are US Dept. of Defense hospitals, our access to these servers needs to comply with a whole range of requirements and standards. At this point it's looking like the SSH daemon needs to be FIPS 140-2 compliant, and the only package that is certified is F-Secure.

http://bugzilla.mindrot.org/show_bug.cgi?id=968 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #760| |ok? Flag| | ------- Additional Comments From djm at mindrot.org 2005-02-16 11:24 -------

I'm trying to configure and build the current bits from the CVS tree, I've used autoconf (GNU Autoconf) 2.52 to generated configure from the configure.ac file. When I run configure on Solaris 9 I get a failure thus: $ ./configure .... checking for OpenSSL directory... /usr/local/ssl checking for RSA support... yes checking whether OpenSSL's headers match the library... yes checking