Why don't you create a new session with all the changes you want and save it?
To save a session: first go through the rest of the configuration box setting up all the options you want. Then come back to the Session panel. Enter a name for the saved session in the ‘Saved Sessions’ input box. (The server name is often a good choice for a saved session name.) Then press the ‘Save’ button. Your saved session name should now appear in the list box. When connecting to the server, click on the session name you just created to load the saved options.
To automate the logon process, you need to use ssh key sharing. Create public-private key-pair using PuTTYgen (check this link for details: Using public keys for SSH authentication ) and save the private key somewhere.
Then, copy the public key from the "Public key for pasting into OpenSSH authorized_keys file" text filed and paste it in the /home/username/.ssh/authorized_keys file. Now, execute the following:
Now, load the previously saved private key in Pageant (can be downloaded from the same putty download site) and you are good to go.
Ok I've lost myself and hit a brick wall.
What I am trying to do is avoid the login screen when the machine is turned on. So no login screen is needed unless you turn the machine on and log out to login and change users. But as I said before I've hit a brick wall. I got not an idea of what I... (4 Replies)
Hey all,
I'm trying to configure a system so when it reboots it'll automatically log as a user I have selected. I've never done this nor' as I to sure on how to. This is teh best I have found on teh web and well I've changed a few things. but does anyone who has done this know if it'll work... (1 Reply)
Hi All,
We have some HP unix servers and sometimes we logon there thru a dedicated Windows server that has Reflection X on it in case we need X. In this case we always need to export DISPLAY=winservername:0.0
I want to automate this thing in .profile file. If e.g. $TERM = hpterm (thru... (2 Replies)
Hi,
I am having small query and wheather it is possible ? that user can transfer the files using ftp client examples (filezilla) , but he can not use putty to login using ftp and run the commands,
Regards,
Manoj (2 Replies)
I am changing root password by passwd. Now I can directly log into the system but I can not log in using puttytel.
It will show an error "Incorrect Password":rolleyes: (1 Reply)
Hello Everybody,
I have a question on the UNIX server login with putty.
Can this login procedure into PUTTY be automated with a macro or vbs or batch file?
Kindly help me in directing me for the above.
Thanks for the help,
Regards, (3 Replies)
I've created a .bat file with this line:
start C:\USERS\Putty\putty.exe -ssh user@server.com -pw password
That opens a putty session and logged in it with the user and password i've already specified. But now, I want to enter a simple command like "ls -l" for example.. How can I do that?
I've... (3 Replies)
Hi all,
I am able to login via putty to a fedora 10 workstation.
But when i try to login via physical screen connected to workstation, it just gives me a blank screen and i cant see any options to enter username and passwd. How do i get the physical GUI to work.
$ who -r
... (4 Replies)
Hi Guys ,
I am using putty.exe file to login to servers . I heard that there is way to save my username and password in putty so that i no need to give my creds while logging into putty . If so please provide me th way to do so .
Please note : I am not talking about keyfile .
Thanks in... (6 Replies)
Hello,
I was wondering, we have multiple servers where we login from Putty.
Is there some way we get automatically loged in after giving server name and password(by saving it in some file or like that)
Just a thought (2 Replies)
Discussion started by: mirwasim
2 Replies
LEARN ABOUT SUSE
ssh-keyconverter
SSH-KEYCONVER(1) BSD General Commands Manual SSH-KEYCONVER(1)NAME
ssh-keyconvert -- convert ssh v1 keys and authorization files
SYNOPSIS
ssh-keyconvert [-k] [-o output_file] identity_file ...
ssh-keyconvert [-a] [-o output_file] authorization_file ...
DESCRIPTION
ssh-keyconvert converts RSA public and private keys used for public key based user authentication with protocol version 1 to the format used
with protocol version 2.
When using RSA user authentication with SSH protocol version 1, the client uses the private key from $HOME/.ssh/identity to provide its iden-
tity to the server. The server grants or denies access based on whether the public part of this key is listed in $HOME/.ssh/authorized_keys.
SSH protocol version 2 supports both DSA and RSA keys, but the way RSA keys are stored are differently. On the client, the default file name
is .ssh/id_rsa rather than .ssh/identity, and the file's format is different as well. On the server, the public porting of the key can still
be stored in .ssh/authorized_keys, but the key notation has changed as well. Therefore, when switching from protocol version 1 to version 2,
you either have to create a new identity key using ssh-keygen(1) and add that key to the server's authorized_keys file, or you need to con-
vert your keys using ssh-keyconvert.
By default, ssh-keyconvert will try to guess the type of file that is to be converted. If it fails to guess correctly, you can tell if what
type of conversion to perform by specifying the -k option to convert the private key, or the -a option to convert an authorisation file.
When converting your private keys stored in .ssh/identity, ssh-keyconvert will read the private key, prompting you for the pass phrase if the
key is protected by a pass phrase. If the -o option is given, it will write the private key to the specified file, using version 2 syntax. If
the key was protected by a pass phrase, it will use the same pass phrase to protect the new file. It will also write the public portion of
the key to a second file, using the specified file name with ``.pub'' appended. If the -o option was not given, private and public key will
be written to id_rsa and id_rsa.pub, respectively, relative to the directory of the input key file.
If the destination file already exists, ssh-keyconvert will prompt the user for confirmation before overwriting the file, unless the -f
option is given.
When converting your authorized_keys file, ssh-keyconvert will ignore any keys in SSH version 2 format. Any public keys in version 1 format
will be converted and appended to the output file using the new syntax. If the -o option is given, keys are appended to the specified file.
If it is not given, ssh-keyconvert will append all keys to the input file.
Note that ssh-keyconvert does not check for duplicate keys, so if you run it on .ssh/authorized_keys more several times, the converted keys
will show up several times.
OPTIONS -k Convert private key file(s). The default is to guess the type of file that should be converted.
-a Convert authorized_keys file(s). The default is to guess the type of file that should be converted.
-o outfile
Specify the name of the output file. When converting an authorization file, all public keys will be appended to this file. For pri-
vate key conversion, the private and public components of the key will be stored in outfile and outfile.pub, respectively. Note that
since every key must be stored in a separate file, you cannot use this option when you specify several input files.
-f When converting a key file, and the output file already exists, ssh-keyconvert will ask the user whether to overwrite the file. Using
this option forces overwriting.
AUTHORS
OpenSSH is a derivative of the original and free ssh 1.2.12 release by Tatu Ylonen. Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
Theo de Raadt and Dug Song removed many bugs, re-added newer features and created OpenSSH. ssh-keyconvert was contributed by Olaf Kirch.
SEE ALSO ssh(1), ssh-add(1), ssh-agent(1), sshd(8)
J. Galbraith and R. Thayer, SECSH Public Key File Format, draft-ietf-secsh-publickeyfile-01.txt, March 2001, work in progress material.
BSD February 2, 2002 BSD