Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, I <strong>can</strong> work with pageant without being asked about password more one once</p> <p>my ssh line</p> <pre><code>ssh = "c:\Program Files\_Tools\TortoiseHg\TortoisePlink.exe" </code></pre> <p>and running Pageant (with loaded private key /PuTTY-User-Key-File/) will give me ability to communicate with repo without re-authentication</p> <p><strong>Note 1:</strong> Keyring doesn't help in your case at all, debug pageant functionality with pure-ssh connection (ssh or plink)</p> <p><strong>Note 2:</strong> To start Pageant with key (only password needed) you can use extended <a href="http://the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter9.html#pageant-cmdline-loadkey" rel="nofollow noreferrer">command-line</a></p> <blockquote> <p>Pageant can automatically load one or more private keys when it starts up, if you provide them on the Pageant command line. Your command line might then look like:</p> <p><code>C:\PuTTY\pageant.exe d:\main.ppk d:\secondary.ppk</code></p> <p>If the keys are stored encrypted, Pageant will request the passphrases on startup.</p> <p>If Pageant is already running, this syntax loads keys into the existing Pageant.</p> </blockquote> <h2>Add-on</h2> <p>Tried push with my current ssh-settings for TortoiseHG 2.6 (XP SP3 x86), <a href="https://sourceforge.net/u/bigbadger/code/" rel="nofollow noreferrer">Mercurial repo</a></p> <pre><code>c:\TEMP\Fiver&gt;hg push sf pushing to ssh://bigbadger@hg.code.sf.net/u/bigbadger/code searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 7 changesets with 39 changes to 19 files remote: &lt;Repository /hg/u/bigbadger/code&gt; refresh queued. </code></pre> <p>Local repo hgrc</p> <pre><code>[paths] ... sf = ssh://bigbadger@hg.code.sf.net/u/bigbadger/code </code></pre> <p>Private key loaded into Pageant, public key registered on SF, in my profile</p> <p>Mercurial.ini (relevant part)</p> <pre><code>[ui] merge = &lt;irrelevant&gt; username = &lt;irrelevant&gt; ssh = "c:\Program Files\_Tools\TortoiseHg\TortoisePlink.exe" </code></pre> <p>(note none of additional arguments for TortoisePlink)</p> <p>and <strong>nothing</strong> <em>more special</em> was done</p> <p><strong>Screenshot of pure THG push with log output</strong></p> <p><img src="https://i.stack.imgur.com/ZdAmZ.png" alt="Push"></p> <p>Log of <em>good plink+pageant session</em> for SF-SSH</p> <pre><code>&gt;Plink.exe -v -agent bigbadger@hg.code.sf.net Looking up host "hg.code.sf.net" Connecting to 216.34.181.156 port 22 Server version: SSH-2.0-OpenSSH_5.3 Using SSH protocol version 2 We claim version: SSH-2.0-PuTTY_Release_0.62 Doing Diffie-Hellman group exchange Doing Diffie-Hellman key exchange with hash SHA-256 Host key fingerprint is: ssh-rsa 2048 86:7b:1b:12:85:35:8a:b7:98:b6:d2:97:5e:96:58:1d Initialised AES-256 SDCTR client-&gt;server encryption Initialised HMAC-SHA1 client-&gt;server MAC algorithm Initialised AES-256 SDCTR server-&gt;client encryption Initialised HMAC-SHA1 server-&gt;client MAC algorithm Pageant is running. Requesting keys. Pageant has 1 SSH-2 keys Using username "bigbadger". Trying Pageant key #0 Authenticating with public key "github/lazybadger" from agent Sending Pageant's response Access granted Opened channel for session Allocated pty (ospeed 38400bps, ispeed 38400bps) Started a shell/command Last login: Tue Nov 20 03:20:48 2012 from 85.249.33.17 Server sent command exit status 1 Disconnected: All channels closed Welcome to hg.sourceforge.net This is a restricted Shell Account You cannot execute anything here. </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload