Riccardo Mottola, le mer. 30 nov. 2022 21:08:23 +0100, a ecrit: > Hi Samuel, > > Samuel Thibault wrote: > > > It is one year old. > > ? No, it's 2 days old. See the workaround he posted there. > > Sorry, I was somehow misled, I don't know. Not accustomed to microblogging I > gues. > > I see the several hacks about accessing /dev/urandom as well as having > comments about arc4random
See this post: https://toot.aquilenet.fr/@bugaevc@floss.social/109422315762760554 > > > On Devuan, which is systemd-less, I have ssh logs found in : auth.log > > > > > > So I guess we can have on HURD too. Of all the ssh issues, having logs is > > > important, I apparently miss most logs when lloking in /var/log > > Do you have inetutils-syslogd running? > > no I did not have! darn! that was it, just installed... and now I have > auth.log and I also get an error message, which shows a pam issue, in my > opinion: > > Nov 30 19:47:07 osgiliath runuser: PAM unable to dlopen(pam_keyinit.so): > /lib/security/pam_keyinit.so: cannot open shared object file: No such file > or directory That's only a warning, we get that in working systems as well. > Nov 30 19:47:07 osgiliath runuser: PAM adding faulty module: pam_keyinit.so > Nov 30 19:47:07 osgiliath runuser: pam_unix(runuser:session): session opened > for user man(uid=6) by (uid=0) > Nov 30 19:47:09 osgiliath runuser: pam_unix(runuser:session): session closed > for user man > Nov 30 19:52:00 osgiliath sshd[707]: Server listening on 0.0.0.0 port 22. > Nov 30 19:52:00 osgiliath sshd[707]: Server listening on :: port 22. > > however, no log is appended when attempting failing ssh logins. Probably because it's the ssh within the chroot which has troubles, and from the chroot it can't talk with syslogd. Samuel
