[cifs-protocol] RE: Secret 'last set times' doc incorrect in 2008 - 600578

2008-09-07 Thread Andrew Bartlett
On Wed, 2008-09-03 at 12:38 -0700, Richard Guthrie wrote: Andrew, I have completed my research on LsarSetSecret. The documentation provides information when you have an exception case such as when one updates EncryptedCurrentValue. I have included a scenario that might help clarify the

[cifs-protocol] RE: Secret 'last set times' doc incorrect in 2008 - 600578

2008-09-03 Thread Richard Guthrie
Andrew, I have completed my research on LsarSetSecret. The documentation provides information when you have an exception case such as when one updates EncryptedCurrentValue. I have included a scenario that might help clarify the behavior: Scenario: I have a secret object with old and new

[cifs-protocol] RE: Secret 'last set times' doc incorrect in 2008 - 600578

2008-08-26 Thread Richard Guthrie
Andrew, I will be working with you to resolve your issue. I had a quick question to help with our research: If you have a secret object with old/new secret values set. They also both have a timestamp indicating when the values were last updated/set. You call LsarSetSecret passing in null

[cifs-protocol] RE: Secret 'last set times' doc incorrect in 2008 - 600578

2008-08-26 Thread Andrew Bartlett
On Tue, 2008-08-26 at 14:21 -0700, Richard Guthrie wrote: Andrew, I will be working with you to resolve your issue. I had a quick question to help with our research: If you have a secret object with old/new secret values set. They also both have a timestamp indicating when the values

[cifs-protocol] RE: Secret 'last set times' doc incorrect in 2008 - 600578

2008-08-26 Thread Andrew Bartlett
On Wed, 2008-08-27 at 08:50 +1000, Andrew Bartlett wrote: On Tue, 2008-08-26 at 14:21 -0700, Richard Guthrie wrote: Andrew, I will be working with you to resolve your issue. I had a quick question to help with our research: If you have a secret object with old/new secret values