On 06/28/2010 11:10 PM, DJ Lucas wrote:
> On 06/28/2010 10:20 PM, Bruce Dubbs wrote:
>
>> We probably need to also mention:
>
>> # Note: If you use PAM, it is recommended to use a value consistent with
>> # the PAM modules configuration.
>
>> Other opinions?
>
>>-- Bruce
>
>
> Despite the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2010 10:20 PM, Bruce Dubbs wrote:
> We probably need to also mention:
>
> # Note: If you use PAM, it is recommended to use a value consistent with
> # the PAM modules configuration.
>
> Other opinions?
>
>-- Bruce
Despite the comment
On 6/28/2010 11:20 PM, Bruce Dubbs wrote:
> I'm not sure I want to change it to SHA512 in the actual instruction,
> but we might mention in the text that SHA256 and SHA256 are other options.
>
> We probably need to also mention:
>
> # Note: If you use PAM, it is recommended to use a value consisten
Kevin White wrote:
> The sed command in the instructions for shadow (in both the 6.6 and SVN)
> sets the password encryption to MD5.
>
> Just by modifying that sed, I changed it to SHA512, which is just one of
> the options that should be more secure than MD5. Everything just worked
> once I m
The sed command in the instructions for shadow (in both the 6.6 and SVN)
sets the password encryption to MD5.
Just by modifying that sed, I changed it to SHA512, which is just one of
the options that should be more secure than MD5. Everything just worked
once I made that change.
Would changin