Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
5.1 Security Considerations for Implementers
Collapse the table of content
Expand the table of content

5.1 Security Considerations for Implementers

Sensitive information, such as the cleartext password for accounts, is communicated through this protocol; therefore, implementers must pay special attention to the secrecy of this data. Although this protocol does not use transport-level encryption (with the exception of SamrValidatePassword), it does rely on the key strength of the SMB transport for encrypting cleartext data.

Using SamrSetInformationUser2 with UserInternal4InformationNew and UserInternal5InformationNew is the best choice that a client can make for setting a cleartext password through this protocol, because the cryptography used is the strongest in this protocol.

Creating a user object is a multi-step process in this protocol. These steps are outlined in the example in section 4.1. After completing these steps correctly, the server creates a user object in its abstract database. However, the user object is not usable for authentication in this state. The user object needs to be enabled for authentication. The steps for enabling a user object are outlined in the example in section 4.2. Optionally, a password can be set on the user object. As specified in the previous paragraph, SamrSetInformationUser2 with UserInternal4InformationNew and UserInternal5InformationNew is the best choice for setting a cleartext password in this protocol.

Show:
© 2015 Microsoft