Search Issue Tracker
Fixed in 5.4.2
Votes
1
Found in
4.5.4p2
Issue ID
642194
Regression
No
Version Control passwords can be accessed by calling GetConfigValue()
To Reproduce:
1. Open the attached project ( or create and empty project) and connection to perforce.
2. The password now can be accessed by calling:
Debug.Log(EditorUserSettings.GetConfigValue("vcPerforcePassword"))
('Output Password' menu in the attached project).
EditorUserSettings.asset obviously doesn't store the password in plaintext, but should it be so easily accessible?
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
jfperusse_bhvr
Jul 06, 2016 18:49
We have a solution here which does not store the password and instead relies on tickets (already supported by the P4API): https://bitbucket.org/jfperusse_bhvr/versioncontrolplugins. However, for a proper implementation (not using tinyfiledialog), this would require a new command to be implemented on the Unity side so the plugin can request for a password prompt.