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 behavior: > > Scenario: > I have a secret object with old and new secret values set and both > have timestamps indicating when the values were last updated/set. I > then make a call to LsarSetSecret passing in null for new secret value > and a value I choose for old secret value. > > This will null out the new secret value and update the old secret > value. I should also observe that the timestamps for both old/new > secret values would be set to current server time. The table you > reference shows this to be the behavior. > > Please let us know if you have further questions regarding this issue.
I will note that the new logic is *much* easier to implement than the old... Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
