Skip to main content

Timeline for Web-based CMS for passwords

Current License: CC BY-SA 3.0

10 events
when toggle format what by license comment
Jun 26, 2018 at 21:50 history tweeted twitter.com/StackSoftRecs/status/1011728430445023232
May 27, 2018 at 1:28 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Apr 26, 2018 at 19:52 answer added Juanga Covas timeline score: 1
Apr 26, 2018 at 9:18 answer added Scott timeline score: 1
Apr 24, 2018 at 19:34 comment added Basil Bourque @Kodiologist I see. The Question should clarify that they are tracking passwords they have been given, not passwords that they are handing out.
Apr 24, 2018 at 18:42 comment added Kodiologist @BasilBourque I believe this question is about storing passwords that are needed for authenticating with other services, rather than authenticating one's own users. So the original password is needed, not a hash.
Apr 24, 2018 at 3:08 comment added Basil Bourque As Izzy commented, you should never store passwords as such. Learn about hashing, salting, and proper ways to handle passwords and user-authentication.
Apr 23, 2018 at 13:48 history edited unor CC BY-SA 3.0
deleted 11 characters in body; edited tags
Apr 23, 2018 at 10:28 comment added Izzy Storing passwords plaintext on whatever server is a security disaster (what if someone breaks in and gets hold of the list?) Would a secure variant where the password file is stored encrypted (e.g. on a network share) be an option? That's what I found used in most companies I've worked with. Using e.g. KeePass, you could continue storing the (encrypted) database on your NAS – and the structure/forms that application offers would also allow for the additional infos you mention. And it is cross-platform, so one could even use it on a mobile device if wanted ;)
Apr 23, 2018 at 8:58 history asked Norman CC BY-SA 3.0