Putty

Putty is a Telnet/RSH/SSH client with a simple interface. Sometimes, too simple. No tabbed interface for multiple sessions. The main advantage  is the ability use public/private key authentication. But doing without 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.

1. Create public and private key on Unix/Linux  - just as you have, for example

   ssh-keygen -t rsa 

2. Add the public key to $HOME/.ssh/authorized_keys on the Unix/Linux  box. Server to which you are connecting is  interested only in $HOME/.ssh/authorized_keys.

   cd .ssh
   cp identity.pub authorized_keys
   chmod 600 authorized_keys

3. Ensure the keys and authorized_keys are -rw-------
4. Transfer the private key to Windows
5. Use puttygen to create a putty type key identity.ppk  -- import it in puttygen  and save to the folder
6. Launch putty using
   putty -l your_user_name -i private_key_generated_by_putty <server>

See also How To Fix “Server Refused Our Key” Error That Caused By Putty Generated RSA Public Key

NEWS CONTENTS

• 20181205 : How can I scroll up to see the past output in PuTTY? ( Dec 05, 2018 , superuser.com )
• 20090702 : How To Configure SSH Keys Authentication With PuTTY And Linux Server In 5 Quick Steps HowtoForge - Linux Howtos and Tutorials ( How To Configure SSH Keys Authentication With PuTTY And Linux Server In 5 Quick Steps HowtoForge - Linux Howtos and Tutorials, Jul 2, 2009 )
• 20090702 : How to set up SSH keys Frustration with Server refused our key ( How to set up SSH keys Frustration with Server refused our key, )

Old News ;-)

[Dec 05, 2018] How can I scroll up to see the past output in PuTTY?

Dec 05, 2018 | superuser.com

Ask Question up vote 3 down vote favorite 1

user1721949 ,Dec 12, 2012 at 8:32

I have a script which, when I run it from PuTTY, it scrolls the screen. Now, I want to go back to see the errors, but when I scroll up, I can see the past commands, but not the output of the command.

How can I see the past output?

Rico ,Dec 13, 2012 at 8:24

Shift+Pgup/PgDn should work for scrolling without using the scrollbar.

> ,Jul 12, 2017 at 21:45

If shift pageup/pagedown fails, try this command: "reset", which seems to correct the display. – user530079 Jul 12 '17 at 21:45

RedGrittyBrick ,Dec 12, 2012 at 9:31

If you don't pipe the output of your commands into something like less , you will be able to use Putty's scroll-bars to view earlier output.

Putty has settings for how many lines of past output it retains in it's buffer.

^{before scrolling}

^{after scrolling back (upwards)}

If you use something like less the output doesn't get into Putty's scroll buffer

^{after using less}

David Dai ,Dec 14, 2012 at 3:31

why is putty different with the native linux console at this point? – David Dai Dec 14 '12 at 3:31

konradstrack ,Dec 12, 2012 at 9:52

I would recommend using screen if you want to have good control over the scroll buffer on a remote shell.

You can change the scroll buffer size to suit your needs by setting:

defscrollback 4000

in ~/.screenrc , which will specify the number of lines you want to be buffered (4000 in this case).

Then you should run your script in a screen session, e.g. by executing screen ./myscript.sh or first executing screen and then ./myscript.sh inside the session.

It's also possible to enable logging of the console output to a file. You can find more info on the screen's man page .

,

From your descript, it sounds like the "problem" is that you are using screen, tmux, or another window manager dependent on them (byobu). Normally you should be able to scroll back in putty with no issue. Exceptions include if you are in an application like less or nano that creates it's own "window" on the terminal.

With screen and tmux you can generally scroll back with SHIFT + PGUP (same as you could from the physical terminal of the remote machine). They also both have a "copy" mode that frees the cursor from the prompt and lets you use arrow keys to move it around (for selecting text to copy with just the keyboard). It also lets you scroll up and down with the PGUP and PGDN keys. Copy mode under byobu using screen or tmux backends is accessed by pressing F7 (careful, F6 disconnects the session). To do so directly under screen you press CTRL + a then ESC or [ . You can use ESC to exit copy mode. Under tmux you press CTRL + b then [ to enter copy mode and ] to exit.

The simplest solution, of course, is not to use either. I've found both to be quite a bit more trouble than they are worth. If you would like to use multiple different terminals on a remote machine simply connect with multiple instances of putty and manage your windows using, er... Windows. Now forgive me but I must flee before I am burned at the stake for my heresy.

EDIT: almost forgot, some keys may not be received correctly by the remote terminal if putty has not been configured correctly. In your putty config check Terminal -> Keyboard . You probably want the function keys and keypad set to be either Linux or Xterm R6 . If you are seeing strange characters on the terminal when attempting the above this is most likely the problem.

[Jul 2, 2009] How To Configure SSH Keys Authentication With PuTTY And Linux Server In 5 Quick Steps HowtoForge - Linux Howtos and Tutorials

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).

Now type:

su autotimesheet
cd /home/autotimesheet
mkdir .ssh
chmod 700 .ssh
cd .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 [email protected] 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:

ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAIBzPeFQv+295iKzuuPH0jA9449pSHVpCwXvCR9EstmYh...

Type:

chmod 600 authorized_keys2

How to set up SSH keys Frustration with Server refused our key

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 like

  pubkey

• saved the private key to something like

  privatekey.ppk

• moved your public key up to the server
• (maybe even) converted the format of the key from putty to openssh with something like

  ssh-keygen -if pubkey > pubkey_openssh_format

• changed some permissions like

  chmod 700 .ssh

• added your pubkey to the authorized_keys file with something like

  cat pubkey >> .ssh/authorized_keys

• changed some more permissions like

  chmod 600 authorized_keys

• changed your putty settings under "connection > SSH > auth" to use

  privatekey.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 like

  ssh-keygen -t dsa

  (or rsa - read the man pages if your don't know how to use ssh-keygen

• accept the file names it wants to use
• enter a strong passphrase
• add the pub key to the authorized_keys file with something like

  cat 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
  

  pivatekey.ppk

• NOW change your putty settings under "connection > SSH > auth" to use
  

  privatekey.ppk

• 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 ;-)

Recommended Links

Softpanorama Recommended

Top articles

Sites

PuTTY User Manual

• Configuring PuTTY

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

Etc

Society

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

Quotes

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

Bulletin:

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

History:

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

Classic books:

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 Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

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 Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: April 26, 2021