The current implementation of the statekeys command in SharpChrome does not take into account the target parameter, so it just iterates through known paths. This commit adds quick support for the Microsoft Teams state file.
-Default elevated SharpChrome triage behavior is to triage the current user unless additional masterkey material is supplied
-/target:X can now be a user folder
-Bug fixes
-CNG certificate private key support
-/nowrap added to `backupkey`
-key component error fix
-combined `machinecerts` to `certificates /machine`
-fixed SHA1 "hash" calculation for entropy
-only decrypted certs now display by default, `/showall` will show all
-User certificate extraction corrected
-Added more certificate information on extraction (including Enhanced Key Usages)
-Fixed a few formatting issues
-Added /target option for machinecertificates command
Added Chromium-based Edge support for SharpChrome
Added /consoleoutfile support for SharpDPAPI/SharpChrome
Added "statekeys" command to SharpChrome
Fixed SharpChrome cookie bug for expires times of 0
-Landed @leftp's PR for user and machine certificate private key extraction
-Added cert triage to the "triage" and "machinetriage" commands
-Using /password:X now causes the DPAPI masterkey cache to be output
-Combined TriageUserMasterKeysWithPass into TriageUserMasterKeys
-'/password:X' now properly works in SharpDPAPI while elevated, as well as remotely
-'/password:X' now works for SharpChrome, elevated + remotely
Will