login about faq

Please help to setup passwordless authentication on SSH Tectia Client 6.0.12.

asked Dec 07 '10 at 08:39

Sathya's gravatar image

Sathya
1

edited Dec 08 '10 at 10:45

Roman's gravatar image

Roman ♦♦
7735817


Hi,

Is the server are you trying to connect to a Tectia server or OpenSSH (or other) ?

The answers on this question show some examples on how to check the version of the server: http://answers.tectia.com/questions/29/i-am-connected-using-tectia-client-on-windows-to-a-remote-server-how-can-i-tell

If the server is a Tectia Server 6.0 or newer you could try the following:

Note that for this to work, public key authentication needs to be allowed in the server. It's enabled by default on Tectia server but of course it may have been disabled by the administrator

1. Generate a public key pair on the client using keygen, such as:

ssh-keygen-g3 mykey

It will prompt you for a passphrase.

It's possible to enter an empty passphrase by just pressing enter so that you won't get prompted at connection time. However, bear in mind that anyone with access to this key (private part) will be able to connect to the server without further authentication, so be sure to properly secure the private key if you use an empty passphrase.

This will create two files on the client, the private part (mykey) and the public (mykey.pub) part of the key pair. Make sure that the permissions on your private key are secure (only you should have read/write access to it). The public part is the one you can share to the server.

2. Open a remote terminal connection to the Tectia server and create the following directories on your home directory:

.ssh2/authorized_keys

Make sure the permissions on those are so that only you have read/write/execute access:

chmod -R 700 .ssh2/authorized_keys

3. Finally copy the public key (mykey.pub) you just generated in step 1 to the directory you just created on the server in step 2. Such as:

scpg3 mykey.pub user@server:.ssh2/authorized_keys/

You'll get prompted for password since the key is not setup yet. But after coping the key, further connections from clients that have access to the private key should use public-key authentication without passphrase.

And you're done. You should now be able to connect using public key authentication:

sshg3 user@server

This should prompt for the passphrase of your key (or no prompt if you chose an empty passphrase) and authenticate you to the server.

link

answered Dec 08 '10 at 10:43

Roman's gravatar image

Roman ♦♦
7735817

if is a tectia windows server, what is the directory path? .ssh2/authorized_keys ?

(Nov 16 '11 at 06:44) siakhooi siakhooi's gravatar image

@siakhooi If the server is a Tectia Server on Windows the steps are the same (minus the chmod command). The .ssh2/authorized_keys directory should be created under the user's profile directory: %USERPROFILE%\.ssh2\authorized_keys\

(Nov 16 '11 at 21:39) Roman ♦♦ Roman's gravatar image
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×80
×63
×54
×38

Asked: Dec 07 '10 at 08:39

Seen: 37,190 times

Last updated: Nov 16 '11 at 21:39

All user contributed content licensed under the cc-by-sa license.
Powered by OSQA.