- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SSH PRNG not seeded
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2004 09:13 PM
тАО05-24-2004 09:13 PM
SSH PRNG not seeded
We use SSH on our servers and have been running a script which triggers numerous ssh connections to be established over a small period. This script works fine in the day however at 4 am in the morning we get the above error "PRNG not seeded"
I am aware this means that it cannot establish the pseudo random number generator and this is required for the encryption for SSH. From the reading I have done I believe the problem is the fact that there is not enough activity on the system at the time the script is ran (not enough entropy, therefore randomeness).
I'm happy this is the cause but I feel the only solution would be to install a random number generator on the server. I'm aware this is available on 11i but is it available on 11.00.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2004 05:03 AM
тАО05-25-2004 05:03 AM
Re: SSH PRNG not seeded
http://www.josvisser.nl/hpux11-random/
Another method is to run a dedicated daemon, one is called EGD(Entropy Gathering Daemon):
http://www.lothar.com/tech/crypto/
Of the two listed above, I would go with the first. The kernel method which builds a /dev/random device.
An interesting note, I read yesterday that a dedicated Random Number Generator (instead of the psuedo one that hpux uses by default) will increase the speed of some secure applications dramaticaly. Such as, if you have many users using Secure Shell, a dedicated Random Generator will increase performance of the SSH connections.
Regards,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2004 05:04 AM
тАО05-25-2004 05:04 AM
Re: SSH PRNG not seeded
mstm and make sure the NIC is solid.
Problems on the target NIC do not usually cause this symptom.
If booting helps, take a hard look at NIC and cabling.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2004 05:06 AM
тАО05-25-2004 05:06 AM
Re: SSH PRNG not seeded
http://hpux.cs.utah.edu/hppd/hpux/Maths/Misc/prngd-0.9.26/
hope this helps,
-denver
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2004 08:16 PM
тАО05-25-2004 08:16 PM