annotate help/a-34.html @ 698:52b8a499f379

Further packaging/signing fixes
author Chris Cannam
date Mon, 10 Dec 2018 17:52:27 +0000
parents 2c106ea908b5
children
rev   line source
Chris@531 1 <link rel="stylesheet" type="text/css" href="help.css"/>
Chris@531 2
Chris@531 3
Chris@578 4 <h2>Every time I push some changes, I have to type my password again</h2>
Chris@531 5
Chris@578 6 <p>When you push to a remote repository with an &ldquo;https:" prefix on its
Chris@578 7 URL, EasyMercurial's password dialog should ask whether you want to
Chris@578 8 remember your login details.</p>
Chris@531 9
Chris@578 10 <p>If you say yes, the details will be stored until EasyMercurial
Chris@578 11 exits&mdash;so you won't have to enter them if you push or pull again
Chris@578 12 while the present EasyMercurial session is running. Your password will
Chris@578 13 be stored, encrypted with a session key, in a file which is deleted
Chris@578 14 when EasyMercurial exits.</p>
Chris@531 15
Chris@578 16 <p><b>If this option does not appear</b></p>
Chris@531 17
Chris@578 18 <p>... and if you're using OS/X, then you need to install the PyCrypto
Chris@578 19 library before EasyMercurial will be able to store encrypted passwords
Chris@578 20 for you.</p>
Chris@531 21
Chris@578 22 <p>Try running <code>sudo easy_install pycrypto</code> in a terminal window.</p>
Chris@532 23
Chris@578 24 <p><b>Not using an https repository?</b></p>
Chris@532 25
Chris@578 26 <p>If your remote repository uses ssh or some other protocol, then
Chris@578 27 EasyMercurial won't be able to help. You might consider using ssh
Chris@578 28 public key authentication and an ssh agent&mdash;talk to the admin of your
Chris@578 29 remote repository for more details.</p>
Chris@532 30