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?
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
- The mouse cursor is positioned in the center when Cursor.LockState is set to CursorLockMode.Confined and changing the mouse position
- Undefined symbol errors appear when building Xcode project using BuildPipeline.BuildPlayer
- Building a Player fails when using special characters in “Product Name” field
- [VFXG] Clicking on Allow Instancing box resets exposed properties to default values
- [iOS] Unable to select streaming apps when using broadcasting on iOS device
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.