SSH / PAM / Kerberos / password aging
Nicolas.Williams at ubsw.com
Thu Mar 28 07:23:41 EST 2002
On Tue, Mar 26, 2002 at 05:39:09PM -0500, Nicolas Williams wrote:
> On Tue, Mar 26, 2002 at 05:26:09PM -0500, Nicolas Williams wrote:
> > On Tue, Mar 26, 2002 at 02:13:26PM -0800, Frank Cusack wrote:
> > > Qualified good. Wouldn't it be better to do pam_acct_mgmt() before kbdint
> > > et al complete? Your solution requires a rewrite of all PAM modules.
> > Indeed. Fine. So move pam_acct_mgmt() into do_pam_authenticate() and
> > also pam_chauthtok().
> > Fine idea. I like it.
> > > /fc
> I'll post a patch tomorrow.
As you can see from my latest attachement to bug 188 the patch is a bit
more intricate than I'd hoped for. It's very simple for kbd-interactive
userauth, and not so simple for password userauth.
For password userauth support for SSH2_MSG_USERAUTH_PASSWD_CHANGEREQ
must be added or password aging support (in password userauth) must be
dropped altogether. My patch disables password aging in password
userauth. There's more code in session.c and auth-pam.c worth ripping
out if tty-based password aging is removed.
At this point the OpenSSH maintainers need to weigh in and I exit stage left.
On a different, but related, note, is it possible for SSHD to reject
passord userauth altogether if keyboard-interactive userauth was tried
and failed? It's kind of silly to allow the client two different go's at
ultimately the same userauth just because there's two different ways to
do it in the SSHv2 protocol.
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
More information about the openssh-unix-dev