Mekk / mercurial_keyring
Mercurial extension to securely save HTTP and SMTP authentication passwords in password databases (Gnome Keyring, KDE KWallet, OSXKeyChain, specific solutions for Win32 and command line). Uses and wraps services of the keyring library (http://pypi.python.org/pypi/keyring) Bugs? Report them here, on bitbucket. Ideas? Discuss them on the mercurial mailing list (http://www.gmane.org/info.php?group=gmane.comp....), but CC me (Marcin.Kasperski on mekk.waw.pl) so I don't miss the thread.
Clone this repository (size: 53.2 KB): HTTPS / SSH
$ hg clone http://bitbucket.org/Mekk/mercurial_keyring/
| commit 53: | 5924ec5addc5 |
| parent 52: | 9cb5c9856566 |
| branch: | default |
readme note about using ~/.hgrc
Changed (Δ538 bytes):
raw changeset »
README.txt (15 lines added, 0 lines removed)
| … | … | @@ -123,6 +123,21 @@ extension will use them without using th |
123 |
123 |
username is not given, extension will prompt for credentials every |
124 |
124 |
time, also without saving the password. |
125 |
125 |
|
126 |
Finally, if you are consistent about remote repository nicknames, |
|
127 |
you can configure the username in your `~/.hgrc` (`.hgrc` in your |
|
128 |
home directory). For example, write there: |
|
129 |
||
130 |
[auth] |
|
131 |
acme.prefix = hg.acme.com/repositories |
|
132 |
acme.username = johnny |
|
133 |
acme.schemes = http https |
|
134 |
||
135 |
and as long as you will be using alias `acme` for repositories like |
|
136 |
`https://hg.acme.com/repositories/my_beautiful_app`, username |
|
137 |
`johnnny` will be used, and the same password reused. |
|
138 |
||
139 |
The advantage of this method is that it works also for `clone`. |
|
140 |
||
126 |
141 |
Repository configuration (SMTP) |
127 |
142 |
=============================== |
128 |
143 |
