Access Sourceforge.net Shell services using PuTTY on Windows
by Pål Brattberg on November 12, 2008
Shell services at SourceForge have been changing recently and it’s not entirely intuitive how to access your shell account (at least it wasn’t for me).
Here’s how to log in to your shell account for your project using the excellent PuTTY package in Windows.
- Download and install PuTTy
- Run
plink shell.sourceforge.net create - Enter your sourceforge username and projectname using the form:
username,projectname - Enter your sourceforge password
- Run
putty - Enter host name as
shell.sourceforge.net - Set Connection > SSH > Remote command to
create - Set Session > Saved Sessions to
shell.sourceforge.net - Click Save
- Double-click shell.sourceforge.net and enter username and projectname using the same form again:
username,projectname - Enter your password
- Enjoy!
This will work for several projects, just change the project name in step 10.
To give SourceForge feedback on the new Shell changes see the SourceForge shell service survey.
The information above is pulled from the support request PuTTY accesses restricted shell – ID: 2175546
3 comments
Thanks for the tips!
I spent the last 30 mins trying to get this to work, but couldn’t. Read your article, and found the missing link in precisely 30 seconds.
Thanks for sharing this
Regards,
Hasnain
by Hasnain Saleem on Monday, December 29, 2008 at 10:04 pm #
First of all, you forgot a “little” step called creating public/private keys…
Also, step 7 is not true. The whole point is you already ran plink.
Last but not least, in step 10 Putty accepts “username” (without “,project”) just as well.
So here are improved steps + no unneeded GUI usage:
2) plink.exe -l username,projectname -pw password shell.sourceforge.net create
3) putty -l username -pw password -i sourceforge.ppk
4) Enjoy!
by Joe on Tuesday, December 30, 2008 at 1:39 am #
[...] login to the project shell space using PuTTY (Follow this article for an excellent guide to configuring PuTTY for SourceForge.net). Execute the following [...]
by Sourceforge Joomla fix on Thursday, April 2, 2009 at 1:06 am #