Distribute 2 Secrets
| 2 Votes |
Description
Varient: This variation also includes, a second hardcoded secret. This is not secure on the console or database, but would be secure "in flight" and "on the endpoint" and "in all client logs". If you require "console secure" then you should only use the first method where the taker of the action has to type in the secret when taking the action.
Property Details
| 3678 | |
| Beta - Preliminary testing ready for more | |
| Distribute 2 Secrets | |
| BESC | |
| Internal | |
| 7/31/2012 12:00:00 AM | |
| TakeSecureFixletAction Secret Encrypted Password | |
| brolly33 on 12/21/2013 6:59:31 AM | |
| brolly33 on 12/21/2013 6:59:31 AM | |
| 8238 Views / 229 Downloads | |
* Average over 0 ratings.
** Log In or Register to add your rating.
|
Relevance
Actions
Action 1 (default)
Action Link Click
here to deploy this action.
Script Type
BigFix Action Script
dos echo {parameter "secret" of action} > c:\secret
dos echo {parameter "secret2" of action} >> c:\secret
// uncomment this line to "clean up" the the secret in normal usage.
// delete c:\secret
// You may prefer to use the secret directly in commands instead of inserting it into a script file.
// if you choose this method, the plaintext secret will only exist briefly in memory on the endpoint during execution.
// dos net user adminstrator {parameter "secret" of action}
Success Criteria
This action will be considered successful when the applicability relevance evaluates to false.
Sharing
| Social Media: |
