Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better password protection #24

Open
jedbrown opened this issue Mar 31, 2013 · 3 comments
Open

Better password protection #24

jedbrown opened this issue Mar 31, 2013 · 3 comments
Labels

Comments

@jedbrown
Copy link

The password field currently displays the password in clear text. I see a couple mentions of getpass, but it seems there is more than one code path to enter a password. A better system is to support running a process to return the password, as in gpg -d mypass.gpg, or even just .netrc.

@skarra
Copy link
Owner

skarra commented Mar 31, 2013

I just pushed 41963ad Have a look at the commit comments to see how to use this. Let me know what you think.

@unhammer
Copy link

+1 on .netrc.gpg, however, if you want to "lazily" include _all_methods, just let the user define a hook like offlineimap does (grep remotepasseval http://docs.offlineimap.org/en/latest/MANUAL.html).

With offlineimap, I have a function get_password(host,port) that decrypts my .netrc.gpg and fetches my user/password (via emacsclient, because I somehow found that easier). Before I switched to .netrc.gpg, I used the python keyring module with kwallet, again via the remotepasseval hook.

@unhammer
Copy link

unhammer commented Aug 5, 2013

My current method for using ~/.netrc.gpg (or, as emacs expects, ~/.authinfo.gpg): https://gist.github.com/unhammer/6158705 in case it's useful for anyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants