|Contents||Bulletin||Scripting in shell and Perl||Network troubleshooting||History||Humor|
|News||Telnet protocol||Recommended Links||Teraterm Macros||Reference for macrolanguage||LogMeTT||TTPMenu|
|CygTerm+||Cygwin||Expect||SSH||Password-less SSH login||TTSSH||Usage of SCP with Teraterm|
|GNU Screen||Exceed HostExplorer||Putty||Telnet protocol||Tips||Humor||Etc|
Putty is a simple Telnet/RSH/SSH client with a simple interface. Sometimes, too simple. I use Putty a lot and have often some concurrent connections. No tabbed interface. The main advantage is the ability use public/private key authentication. But doing with reading manual often backfires ;-)
If you see the message Server refused our public key, it means that PuTTY has sent a public key to the server and offered to authenticate with it, and the server has refused to accept authentication.
The problem here is that you probably exported putty generated key to the server you are trying to connect. that's an error: putty generate keys in a slightly different format. The correct way is cut and paste the key directly from the puttygen window.
alternatively and you can generate them on the server and then convert private key into putty-compatible format.
The other thing you should do is check your server configuration carefully. Also, read the PuTTY Event Log; the server may have sent diagnostic messages explaining exactly what problem it had with your setup.
ssh-keygen -t rsa
cd .ssh cp identity.pub authorized_keys chmod 600 authorized_keys
See also How To Fix “Server Refused Our Key” Error That Caused By Putty Generated RSA Public Key
Configure your Linux server (create user, save public key)
For this guide let's assume you regular login name is autotimesheet (replace it with one that you use regularly).
As root, on the shell, type:
adduser autotimesheet --disabled-password
You will be asked to fill in some details such as the user's real name (empty string is fine).
chmod 700 .ssh
Then in that folder, create and edit a file called authorized_keys2.
In there, cut/paste your public ssh key, on ONE LINE (That is very important!!!)
Do not add the firstname.lastname@example.org at the end of the line.
Do not add the BEGIN PUBLIC KEY or END PUBLIC KEY.
Do not add the rsa-key-20090614 at the end.
Make sure, there is ssh-rsa at the beginning.
It should be something like:
chmod 600 authorized_keys2
Submitted by andre on Fri, 2006-06-30 01:34.Geeky
So you're trying to set up ssh keys on your windows box with putty and you keep getting "Server refused our key". Read on, I've got your solution... but first lets take a look at what you've done so far.
Chances are you have done some/none/all of the following:
- opened up puttygen.exe
- generated a key after wiggling your mouse
- entered a strong passphrase
- saved the public key to something likepubkey
- saved the private key to something likeprivatekey.ppk
- moved your public key up to the server
- (maybe even) converted the format of the key from putty to openssh with something likessh-keygen -if pubkey > pubkey_openssh_format
- changed some permissions likechmod 700 .ssh
- added your pubkey to the authorized_keys file with something likecat pubkey >> .ssh/authorized_keys
- changed some more permissions likechmod 600 authorized_keys
- changed your putty settings under "connection > SSH > auth" to useprivatekey.ppk
- tried to connect and...
"Server refused our key"
Well - from what I have read that's supposed to work... but it didn't work for you did it?
Your problem has nothing to do with how well you followed these well documented procedures for getting ssh keys to work.
The solution to the problem is...
(brace yourself, its really simple) to try generating the keys on the server (unix, linix, bsd etc.) instead of the client (i.e. in windows).
Try the following:
- ssh to your server using good old user name and password
- do check permissions on your ~/.ssh folder and make sure to
chmod 700 .ssh
if they are wrong
- do check permissions on your ~/.ssh/authorized_keys file and make sure to
chmod 600 authorized_keys
if they are wrong
- generate the keys on the server with something likessh-keygen -t dsa
- accept the file names it wants to use
- enter a strong passphrase
- add the pub key to the authorized_keys file with something likecat id_dsa.pub >> .ssh/authorized_keys
- copy the private key (id_dsa) to your local windows machine (use winscp or sftp or some such tool)
- NOW open puttygen.exe
- under actions select "load" and load the id_dsa file
- enter the passphrase you set when you generated the key on the server. Puttygen will now convert the key to something that putty will understand
- save that file to something like
- NOW change your putty settings under "connection > SSH > auth" to use
- NOW try and connect
- enter the passphrase when prompted
- pat yourself on the back. You're connected to the server (I hope)
Now all you have to do is figure out a way to not have to always enter that passphrase. Well that will require setting up puttyagent. But, I'll let you figure that out for yourself.
I really hope this helped you out. I wasted too much of my life figuring this out this evening and I hope I saved you hours of aggravation.
Have comments? Want to say thanks? Leave a comment. Or if you feel really generous send me a buck or three ;-)
How To Fix “Server Refused Our Key” Error That Caused By Putty Generated RSA Public Key
Phone System Tech Support macros in puTTY
Look into Tunnelier and Plink if you're using the SSH abilities of puTTY. An official "scripting" language for puTTY is reportedly only half-written at this point. If using the telnet aspect only, then consider using ProComm Plus. It has an increadibly powerful scripting language.
Here is one killer of a bet. It's a free utility called AutoHotKey, which automates keyboard and mouse actions AND has been tested with puTTY.
PuTTY hacking guide
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes. If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner.
ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least
Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.
Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: February 19, 2014