|
Jon Paris wrote:
And so far I still have no idea why my User was disabled.
This would be my guess: When PASE_USRGRP_LIMITED=N is not set, somewhere
during the initiation of a new connection ssh ends up seeing a mismatch
between the > 8 character userid it was asked to create a session for and
the information returned by OS routines like geteuid, getpwuid, etc. With
that mismatch, sshd concludes something funky is going on and bails out on
that connection attempt -- logging an invalid connection attempt along the
way. Eventually those invalid attempts add up and disable the userid.
--
-----
Walt Madden
IBM i software development
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.