Re: lost ssh access - where is a log?

[Sergey Bugaev]

On Tue, Nov 29, 2022 at 7:34 AM Guy-Fleury Iteriteka
<gfleury@disroot.org> wrote:
> There is a thread from bugaev that explain the issue and a partial fix :
>
> https://floss.social/@bugaevc/109422269238549581

Well, I guess that's my cue to wave hi to this list :)

Hello everyone!

I am indeed out of the army, alive and in one piece. I've been out for
two weeks already, and in this time I've managed to build myself a
mostly working cross-toolchain targeting the Hurd, and set up a new
Debian GNU/Hurd box (the old one is gone along with the laptop that
hosted it — that was a work laptop, and I had to give it back when
leaving).

As for the SSH/arc4random issue: I believe a better workaround would
be for glibc to cache the /dev/urandom port between calls to getrandom
(), the same way that it caches socket server ports (see
hurd/hurdsock.c). The main motivation for such caching would be
performance, and indeed getrandom is expected to be _very_ fast, and
walking the filesystem on every call is anything but fast; but this
would also satisfy sshd's reasonable expectation that arc4random keeps
working inside a chroot if "pre-warmed" before chrooting.

Sergey