<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 587: Password encrypted with a hardcoded password</title><link href="https://sourceforge.net/p/squirrel-sql/feature-requests/587/" rel="alternate"/><link href="https://sourceforge.net/p/squirrel-sql/feature-requests/587/feed.atom" rel="self"/><id>https://sourceforge.net/p/squirrel-sql/feature-requests/587/</id><updated>2020-01-23T18:14:04.453000Z</updated><subtitle>Recent changes to 587: Password encrypted with a hardcoded password</subtitle><entry><title>#587 Password encrypted with a hardcoded password</title><link href="https://sourceforge.net/p/squirrel-sql/feature-requests/587/?limit=25#0974" rel="alternate"/><published>2020-01-23T18:14:04.453000Z</published><updated>2020-01-23T18:14:04.453000Z</updated><author><name>Gerd Wagner</name><uri>https://sourceforge.net/u/gerdwagner/</uri></author><id>https://sourceforge.neta0a3b075a6c1f7417700f079ba1f31340fe9b445</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Just to mention: There's a simple and secure workaround: In your Alias definition do not enter any password and uncheck "Auto logon".&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Password encrypted with a hardcoded password</title><link href="https://sourceforge.net/p/squirrel-sql/feature-requests/587/" rel="alternate"/><published>2020-01-23T14:47:36.627000Z</published><updated>2020-01-23T14:47:36.627000Z</updated><author><name>Pedro Miguel</name><uri>https://sourceforge.net/u/pedromiguel23/</uri></author><id>https://sourceforge.netb5d5a35472d4885f660d70aee57f4b59e51c8d96</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It was added the possibility to encrypt the passwords used to connect to database. But the encryption key is hardcoded in code. Therefore, someone with access to code (or decompiled) can discover the encryption key and decrypt the passwords. Nevertheless, if I copy the configuration file from other machine, I can use its configuration, and without knowing the password, connect to the database.&lt;/p&gt;
&lt;p&gt;The password should be encrypted/decrypted by a master key, defined by the user. The user must enter the key on application startup (or on first use of a connection with encrypted password) and the password keep in memory for future use (to not reduce user experience).&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>