Re: To detect weak or blank password?
From: Larry Smith (no_spam_at__nospam.com)
Date: 10/15/05
- Previous message: Robert Oeffner: "Re: CryptVerifyCertificateSignature fails with NTE_BAD_SIGNATURE"
- In reply to: Vladimir Nechipurenko: "Re: To detect weak or blank password?"
- Next in thread: Sam Hobbs: "Re: To detect weak or blank password?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 15 Oct 2005 07:30:05 -0400
> Nobody knows? :(((((
The only function I know of is "NetValidatePasswordPolicy()" but it's good
for Win2003 only. Other options are to call "NetUserChangePassword()" (or
"NetUserSetInfo()" passing "USER_INFO_1033) and check for
"NERR_PasswordTooShort" which is returned if the password policy isn't met.
Depending on what you're doing, you may have to create a temporary (dummy)
account first and call it against that account which you can then delete
afterwards. It's ugly and may require certain administrator (or power user)
rights (you'll have to check) but I'm not sure if there's another way.
- Previous message: Robert Oeffner: "Re: CryptVerifyCertificateSignature fails with NTE_BAD_SIGNATURE"
- In reply to: Vladimir Nechipurenko: "Re: To detect weak or blank password?"
- Next in thread: Sam Hobbs: "Re: To detect weak or blank password?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
