public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rooted/compromised Gentoo, seeking advice
Date: Thu, 12 Aug 2010 13:56:16 +0100	[thread overview]
Message-ID: <69CC61AA-F54C-4FAE-AE2D-20E6E3ED3E67@stellar.eclipse.co.uk> (raw)
In-Reply-To: <4C62E90A.20601@gmail.com>


On 11 Aug 2010, at 19:16, Dale wrote:
> Stroller wrote:
>>
>> On 10 Aug 2010, at 20:22, Hazen Valliant-Saunders wrote:
>>> ...
>>> Good Luck getting people to change them frequently and haveing  
>>> your techs and it departments meeting complexity and length policy.
>>
>> I'm pretty sure that's a trivial setting for expiration policy and  
>> a PAM plugin or option to enforce complexity.
>
> Thing about changing passwords to often, the person forgets what the  
> password is.

Then don't change it with frequency.

It was Mr Valliant-Saunders who seemed to be saying that that is  
difficult to enforce, and I was merely replying to him.

Stroller.




  parent reply	other threads:[~2010-08-12 13:03 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09 16:25 [gentoo-user] Rooted/compromised Gentoo, seeking advice Paul Hartman
2010-08-09 16:48 ` Alan McKinnon
2010-08-09 18:48   ` Paul Hartman
2010-08-09 18:59 ` [gentoo-user] " 7v5w7go9ub0o
2010-08-09 19:08   ` Paul Hartman
2010-08-09 19:46   ` Mick
2010-08-10 13:50     ` Kyle Bader
2010-08-09 19:09 ` [gentoo-user] " Mick
2010-08-09 20:08   ` Robert Bridge
2010-08-09 20:20     ` Bill Longman
2010-08-10  0:30       ` Kevin O'Gorman
2010-08-10  1:18         ` William Hubbs
2010-08-10  6:42           ` Alan McKinnon
2010-08-10 13:03           ` Kevin O'Gorman
2010-08-10 18:50             ` Alan McKinnon
2010-08-10 19:22               ` Hazen Valliant-Saunders
2010-08-10 23:23                 ` Peter Humphrey
2010-08-11 16:55                 ` Stroller
2010-08-11 18:16                   ` Dale
2010-08-11 20:30                     ` Alan McKinnon
2010-08-11 22:11                       ` [gentoo-user] Rooted/compromised Gentoo, seeking advice - AKA passwords Bill Longman
2010-08-11 23:09                         ` Alan McKinnon
2010-08-12  4:30                           ` Bill Longman
2010-08-12 13:01                       ` [gentoo-user] Rooted/compromised Gentoo, seeking advice Stroller
2010-08-12 19:21                         ` Alan McKinnon
2010-08-12 19:43                           ` Peter Humphrey
2010-08-12 20:14                             ` Alan McKinnon
2010-08-12 12:56                     ` Stroller [this message]
2010-08-13  2:11                       ` Dale
2010-08-11 16:58               ` Stroller
2010-08-11 20:26                 ` Alan McKinnon
2010-08-09 20:25     ` Dale
2010-08-09 21:22       ` Mick
2010-08-09 22:19         ` Dale
2010-08-09 21:17     ` Philip Webb
2010-08-09 23:07   ` Paul Hartman
2010-08-10  2:14     ` Frank Steinmetzger
2010-08-10  2:24       ` Indexer
2010-08-11  1:05       ` Walter Dnes
2010-08-11  2:16         ` Dale
2010-08-11  4:36           ` Walter Dnes
2010-08-11  5:37             ` Dale
2010-08-10  2:30     ` Keith Dart
2010-08-10  3:06 ` Adam Carter

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=69CC61AA-F54C-4FAE-AE2D-20E6E3ED3E67@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.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