mirror of
https://github.com/samba-team/samba.git
synced 2025-01-08 21:18:16 +03:00
b7d1c5aae8
This is not related to PSOs at all, but there's a minor discrepancy between Windows and Samba password-history-length behaviour that I noticed during PSO testing. When the pwdHistoryLength changes from zero to non-zero, Windows includes the user's current password as invalid immediately, whereas Samba only includes it as invalid *after* it next changes. It's a fairly obscure corner-case, and we might not care enough about it to fix it. However, I've added a test case to highlight the difference and marked it as a known-fail for now. I also added a general pwdHistoryLength test case to show that the basics work (this didn't seem to be tested anywhere else). Signed-off-by: Tim Beale <timbeale@catalyst.net.nz> Reviewed-by: Andrew Bartlett <abartlet@samba.org> Reviewed-by: Garming Sam <garming@catalyst.net.nz>
4 lines
196 B
Plaintext
4 lines
196 B
Plaintext
# highlights a minor corner-case discrepancy between Windows and Samba
|
|
samba4.ldap.password_settings.python.password_settings.PasswordSettingsTestCase.test_domain_pwd_history_zero\(ad_dc_ntvfs\)
|
|
|