Bug 361 - PRNGD not yet seeded & SSH banner stills show previous banner
Summary: PRNGD not yet seeded & SSH banner stills show previous banner
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: -current
Hardware: SPARC Solaris
: P3 normal
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-19 10:06 AEST by mcclain
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mcclain 2002-07-19 10:06:46 AEST
1. I have successfully added the most current packages such as PRNG, ZLIB, 
Openssl and Openssh3.4p1 on SPARC Solaris 7 with no problem.
However I've been having problems on the Intel/Sparc Solaris 8 platforms.
Packages installed: openssh-3.4p1, openssl-0.9.6d, zlib-1.14 and prngd.0.9.25
When Generating either keys either line below, I would received an
error: PRNG not seeded. It appears theirs a missing link or path. 
    ssh-keygen -t rsa1 -f /etc/ssh/ssh_host_key -N ""
    ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key -N ""
    ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key -N ""

First I've seeded it with the following command:
/usr/local/sbin/prngd /var/spool/prngd/pool
Then tried running the ssh-keygen with no luck. /usr/local/sbin 
and /usr/local/bin are in its patch and sourced in addition to Rebooting the 
systems. I've also unpackaged PRNG and everything associated with it and added 
the Sunsolve Patch 112438-01 however after installing it, It appears the patch 
conflicted with an IDS
software. Once uninstalled, the software was able to run

Do I need to to build it versa adding the package?

2. After adding Openssh3.4p1 onto Solaris 7 Sparc platform, wanted
to see if the system updating by running ssh -V
The out was correct, however if I telnet to port 22, it shows
the previous version of ssh. Why? How can I fix this?
Comment 1 Lutz Jänicke 2002-07-19 17:37:19 AEST
OpenSSH's "configure" command will only pick up a new installation of PRNGD,
when it is running during the call to configure. Thus make sure to
* install prngd first and check its proper operation.
* then run OpenSSH's configure command and check the output at the end:
  it should show the correct entropy source.
* then compile and install OpenSSL
Finally make sure to stop the daemon listening on port 22 and start the new one,
otherwise it will not become active until reboot
Comment 2 Damien Miller 2002-09-10 21:36:48 AEST
Point 1 has already been answered by Lutz (and the INSTALL doc)

Point 2: Make sure you have restarted the server. Besides, the bug tracking
system is not the place to ask support questions.
Comment 3 Damien Miller 2004-04-14 12:24:18 AEST
Mass change of RESOLVED bugs to CLOSED