Your message dated Fri, 4 Mar 2016 23:10:25 +0100
with message-id <[email protected]>
and subject line Re: Bug#115767: I see this too on x86 user-mode-linux on etch
has caused the Debian Bug report #115767,
regarding openssh: Couldn't obtain random bytes (error 604389476)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
115767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=115767
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openssh
Version: 2.9p2-6
Severity: important
On mips and mipsel, the above error message is frequently seen when calling
ssh with a command, usually several times in rapid succession, although that
is not always the case. The error appears to come from the OpenBSD compat code
for arc4random, even if arc4 is not the cipher in use!
What the error number means I am not sure of, as it comes from inside
SSL, and I can't tell what it means from a quick glance at the code.
A call to one of the more descriptive error calls at this point may be
a good idea.
So I can see two possible things to help the problem:
1. report a more verbose error message so that one might understand why it
is failing so it might be fixed.
2. don't initialize the arc4 random routines if arc4 is not used.
I will attempt to do #1, but as the problem is intermittent, it may take
awhile to collect the information. I think a more descriptive error message
in this failure case would be a good idea either way.
--- End Message ---
--- Begin Message ---
On 2016-02-29 17:33:32 [+0100], Bernhard M. Wiedemann wrote:
> I have switched from UML to KVM and have not seen this bug anymore since
> years.
I hereby close the bug. Nobody seem to be able to reproduce anymore. The
current linux UML maintainer (Richard Weinberger) can not recall to have
ever seen such a bug (but then he wasn't around 2001).
Feel free to reopen the bug with more info once someone is able to
trigger it again.
> Ciao
> Bernhard M.
Sebastian
--- End Message ---
