Re: broke my OpenSSH how?

[Markus Friedl <markus.friedl@informatik.uni-erlangen.de>]

there have been some broken ssl-2.7.xxx packages.

just change the permission of /dev/arandom to 644.


On Thu, Nov 02, 2000 at 10:17:19PM -0800, Rickie Kerndt wrote:
> running OpenBSD2.7-released (patched manually, easily done thankyou), 
> ssl-2.7-intl ssl libs, OpenSSH 2.2.0.
> 
> Somehow i ran into a permissions problem with /dev/arandom which caused all 
> the ssh stuff to break getting errors of no RSA support even though i have 
> the correct libs. sshd continued to do rsa authentication which led me to 
> look into a possible permissions problem after first replacing the libs 
> with fresh copies and upgrading from OpenSSH 2.1.1 to OpenSSH 2.2.2.
> 
> What i can't understand and hence my question is that ssh was working fine 
> up to Oct 27 when a user sent me an email saying scp was broke. Making 
> /dev/arandom group and other readable fixed it. So why work and then not 
> work? Was one of the other random devices being used previously and then 
> arandom selected? I swear i never changed permissions of the device files!
> 
> stubing:dev {161} ll ?random
> 0 crw-------  1 root  wheel  119,   4 Oct 31 18:43 arandom
> 0 crw-r--r--  1 root  wheel  119,   3 Jul 14 20:06 prandom
> 0 crw-r--r--  1 root  wheel  119,   1 Jul 14 20:06 srandom
> 0 crw-r--r--  1 root  wheel  119,   2 Oct 31 18:43 urandom
> 
>