From: Kurt Lieber <klieber@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] locking user accounts doesn't really lock them.
Date: Fri, 31 Oct 2003 16:27:31 -0500 [thread overview]
Message-ID: <20031031212727.GZ2395@mail.lieber.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
Right now, at least on Gentoo, if you lock a user's account with passwd -l
<username>, that user is still able to access their account if they have
ssh keys set up. This is, in my mind, a fairly big security hole.
Googling, I found an issue related to the Solaris implementation of PAM[1]
that was fixed in a later version.
Does anyone know if there is a way to fix this in Gentoo and/or Linux? (I
don't have access to any non-Gentoo linux boxen atm, so I can't say for
sure if this issue exists on other distros) A tweak to PAM, perhaps?
--kurt
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-10-31 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 21:27 Kurt Lieber [this message]
2003-10-31 21:55 ` [gentoo-dev] locking user accounts doesn't really lock them Kevyn Shortell
2003-10-31 22:01 ` Kurt Lieber
2003-10-31 22:18 ` Kurt Lieber
2003-11-01 2:47 ` Lisa Seelye
2003-11-01 11:50 ` Eldad Zack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031031212727.GZ2395@mail.lieber.org \
--to=klieber@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox