From: SourceForge.net <no...@so...> - 2008-10-01 16:15:54
|
Bugs item #1892904, was opened at 2008-02-13 17:58 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=1892904&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Adam Crume (adamcrume) Assigned to: Nobody/Anonymous (nobody) Summary: Passwords entered when connecting are stored Initial Comment: In 3.0, if a username but no password was specified for a connection, the user would be prompted for a password when trying to connect. This would not be stored on the filesystem. In 3.5 RC5, if a username but no password was specified for a connection, an error is given when trying to connect, and the user is prompted for a password. This is then stored in the connection profile. My company has a strong policy that passwords not be stored. SQL Explorer 3.5 will have to go back to the old behavior before we can use it. ---------------------------------------------------------------------- >Comment By: Heiko Hilbert (hhilbert) Date: 2008-10-01 18:15 Message: This is fixed in RC6. If you don't check the 'Auto logon' box in the connection profile the password is never stored on filesystem. It is hold in memory after you have entered it on the first connect dialog in the current session and will be reused for further logins on the same profile. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=1892904&group_id=132863 |