trinker
commented
12 years ago I agree Dason. The code is a bit ugly too but worked. I don't have time to do anything with it until the end of the semester. Having it ask for a password each time is easy enough to do. I like the separate talkstats repo though and if so we could fork this one and I'd shut it down after we load it into the talkstats repo.
On Sat, Nov 3, 2012 at 2:32 PM, Dason Kurkiewicz notifications@github.comwrote:
I don't think it's very good to save the passwords in plaintext. I also don't like having to have passwords be visible when typing them.
Personally I think it would be best to ask for the password every time to validate the user and using something similar to what is proposed here: http://stackoverflow.com/questions/2917202/r-way-to-securely-give-a-password-to-r-applicationfor password input.
At some point I think I'm going to fork this repo and make some changes but I've been too lazy lately. I actually made a TalkStats organization on github a while ago and it might make the most sense to have that own the repository so we can have any members adding to the package that want.
— Reply to this email directly or view it on GitHubhttps://github.com/trinker/talkstats/issues/1.
I don't think it's very good to save the passwords in plaintext. I also don't like having to have passwords be visible when typing them.
Personally I think it would be best to ask for the password every time to validate the user and using something similar to what is proposed here: http://stackoverflow.com/questions/2917202/r-way-to-securely-give-a-password-to-r-application for password input.
At some point I think I'm going to fork this repo and make some changes but I've been too lazy lately. I actually made a TalkStats organization on github a while ago and it might make the most sense to have that own the repository so we can have any members adding to the package that want.