Logging into a Mercurial repository on Sourceforge with an SSH private key

 Mercurial  Comments Off on Logging into a Mercurial repository on Sourceforge with an SSH private key
Mar 272014

I was just about to post the following to stackexchange.com:

I have got a mercurial repository on sourceforge.net, generated an ssh key with PuttyGen and uploaded it to Shell Services Configuration as described in the relevant site documentation. I then started Pageant and entered my passphrase.

Now, I can connect to shell.sourceforge.net without entering a password and create a session there that works fine. So, the key has been generated correctly and uploading the public key also worked fine.

As I understand it, I should now also be able to use the command

hg pull

on a sourceforge repository without the need to enter my password. I therefore added the following line to my mercurial.ini file, in the ui section:

ssh="C:\Program Files (x86)\PuTTY\plink.exe" -ssh -agent -v -i "D:\path\to\my\private_key.ppk"

Unfortunately any hg command that requires a connection to the sourceforge repository times out. If I remove that line again, everything works fine, but I have to enter my password.

hg --debug pull

emits the following lines:

And then I tried it again to get the error messages for posting into the question. Guess what? This time it worked. I swear, I didn’t do anything different than before and I haven’t changed anything. All previous attempts failed with the error “Server refused our key”. So I guess sourceforge changed something. Maybe it was a case of synchronizing the public key to all servers taking forever (several days) or maybe they came around to reading my support request and doing something about it.

Don’t you hate it when things start working without you knowing what caused it to fail in the first place? I certainly do!

 Posted by on 2014-03-27 at 21:51

Using MSConfig to disable autostart

 Windows  Comments Off on Using MSConfig to disable autostart
Mar 272014

I guess most of you know that you can use msconfig (Start->Run->”msconfig”) to disable programs that are automatically started by Windows. And you might have wondered where these entries go, when you disable them. Especially it looks like magic if entries in the start menu’s Startup folders are concerned: You disable them in msconfig and the shortcuts disappear from the folder. You enable them, and the shortcuts reappear again. So how does msconfig know about these disabled entries?

Googling brought me (after lots of irrelevant entries, Google search seems to be getting worse by the day) to
this Stackoverflow question which also contains the answer:

They are stored in the registry under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\MSConfig\startupreg

for programs that are started through the registry autostart and under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\MSConfig\startupfolder

for programs started from the startup folder.

Thanks to my colleague Steffen who brought this up. Learned something useful today.

 Posted by on 2014-03-27 at 12:46