Re: lost ssh access - where is a log?

[Riccardo Mottola]

Hi Samuel,


Samuel Thibault wrote:
> See this post:
> https://toot.aquilenet.fr/@bugaevc@floss.social/109422315762760554

indeed, the

mkdir /run/sshd/dev
settrans -ac /run/sshd/dev/urandom /hurd/random

trick gave me a working ssh, probably unsecure  as Sergey writes, but at 
least it proves we have the same issue.

> > 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.

Ah ok... well sometimes warnings can be meaningful.

> > 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.

understandable, but inconvenient, somehow remove the purpose of logging.

Riccardo