Timeline for Is it ok for software to store passwords locally in plain-text?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 6, 2014 at 14:30 | comment | added | Andrew Hoffman | However it technically isn't much worse than how a web-browser stores passwords. If the device is trusted to be hack-free then it isn't a big risk. The bigger risk would be applications that the user installs, like game hacks and warez. | |
| Oct 6, 2014 at 14:27 | comment | added | Andrew Hoffman | Ah, ok. Well I was browsing through this thread stackoverflow.com/questions/180870/… and looked at a few of the library APIs. Crypto++ seems to be easy enough. Ok so since it isn't a password manager, it probably shouldn't save passwords anywhere at all. And if it does, should at least warn the user that any other app can access the saved passwords. | |
| Oct 3, 2014 at 16:26 | comment | added | Selali Adobor | The application isn't a password manager, saving the password is just meant to be an "ease of use" feature, so the idea is the user doesn't need to provide anything (otherwise whatever they provide just "aliases" the process of entering original password). And as the question states, storing the passwords needs to be done in a cross-platform environment (the main language used is C++, with Qt for the front-end framework). The only relatively secure methods I know are all OS-specific. | |
| Oct 2, 2014 at 21:35 | history | edited | Andrew Hoffman | CC BY-SA 3.0 |
added 226 characters in body
|
| Oct 2, 2014 at 21:25 | history | edited | Andrew Hoffman | CC BY-SA 3.0 |
added 164 characters in body
|
| Oct 2, 2014 at 21:18 | history | answered | Andrew Hoffman | CC BY-SA 3.0 |