2007-September Archive by Thread
Messages are ordered newest-to-oldest in this index. The newest
threads will be at the top of this page, the oldest will be at the bottom.
Within a single thread, the first mail note is the START of the
thread; the notes following that are in the chronological order of
when they were received. So globally, newest messages are at the top,
but within a thread, the oldest (the start of the thread) is at the
top.
If you think about it, it is confusing. Just go with the flow and everything will be all right.
- Tracking down limit issues,
Michael Gale
- Two independant auth's desired for imap,
D G Teed
- Feature request: alternate '/' for pam_unix,
Jozsef Kadlecsik
- pam_group and user matching,
Matthieu CASTET
- pam_authenticate problem,
Jonathon Coombes
- pam_access: repatch,
Julien Lecomte
- RLIMIT_NICE xtests,
Julien Lecomte
- Re: Pam-list Digest, Vol 43, Issue 13,
Andreas Schindler
- Restrict list of users under KDE Advanced Permissions,
Murray Trainer
- pam_get_data() can get data when using in SSHD,
Ian jonhson
- modifying pam_namespace,
Jan Kasprzak
- Conversation function with both user and password prompt,
Richter , Jörg
- 2 instances of ssh,
J Adams
- passwd prompts for new password only once when a short password is entered,
PoWah Wong
- Module Idea,
B.J. Black
- How to limit disk quota with PAM,
Ian jonhson
- openssh and pam_ldap,
Michael Thomas
- pam_env: per-user environment file?,
Kees Cook
- Use specific PAM configuration.,
Sridhar Bandi
- Still unknown problems with CRON and PAM (How does pam determine its state?),
DI Roman Fiedler
- Re: How to stack PAM without pam_stack,
Andrew Morgan
- Passing information from app to module by pam_*env,
Tobias Heide
- Re: pam_set_cred vs. pam_close_session,
Ian jonhson
- how to prohibit user 's operation,
Ian jonhson