Hi

I'm trying to access a windows 2003 server from a linux node.
I need the ssh to logon without the password to run some automated
scripts. It's a secure system so the password is not an issue.

I can get logged in if I supply the password, however
I need to get login with out the password.

Has anyone tried this from a Linux node?

I have copied the rsa and dsa public keys from the linux box to the
ssh_public_key file and set all of the other settings as described in this mail thread.

Any other ideas

thanks

-ken

i need free ssh access can any one help me

Free SSH access???

I'm on a windows 2003 server which also acts domain controller. (research project only).

I've create Public And Private keys and i know they are correct and placed in the right folder.

When i try to logon however i do get a Access Denied, (with a passphrase or not, i've tried both). I tend defaults to normal pass.user and this does work.

I've used puttygen and copy pasted the openssh one as public (also tried the export openssh key).

One small issue: is it just more convenient to use pub/pri .. as long as it's just as safe to tunnel traffic i don't really care coz short timeline. Yet seems strange i did get cygwin to work...

Maybe there is a setting in Active Directory i need to change coz quite frankly if there is no password in the pub/pri how on earth will it verify me as Admin when i logon?

I had a similar issue to the comment below, if you are using private key and password required. and have setup as directed at the start of this topic, copied key straight to notpad from puttygen. Named the file as the username etc.

Then tried to connect

You entered the login name.

It asks for Key password (assuming this was set).
You definately typed the password correctly
but it displays 'Denied'

and re prompts for a password.

However I noticed this is no longer the Key password, but the user password.

Entering the user password now and the connection works. Basically what I am trying to get across is that if you have a private key and password set to require. Dont be put off by the first denied message. It is purely because it still needs the user password so denies the connection at that stage.

If you use Pageant and add the key first. I dont get the denied message at all. Just authenticates the key and asks for the user password.

Hope this helps someone.

Quote:

---

Ah... Finally got it to work. In FreeSSHd, Under 'SSH', Under 'Authentication', Password Authentication has to be set to 'Allowed' and Public key Authentication has to be set to 'Required'.

If both are set to 'Required', I get the 'Access Denied' problem.

Any explanation?


-Mike

[quote]I've had the same experience as 'unf' in regards to freesshd and the key passphrase. What is strange, however, is when I log in and type the correct passphrase, I get 'Access denied.'. If I type in an incorrect passphrase, I get: 'Wrong passphrase.'. So technically, the passphrase is working, however it won't allow access. Could it have something to do with permissions? I'm stumped.

-Mike

[quote]unf.... it says "myusername"... there's no dot, or an extension. If your username is unf then your public key file should be named "unf".

BTW, if your username is 'unf', then your public key should be in "C:\Documents and Settings\Unf\ssh_public_keys", not "C:\Documents and Settings\Administrator\ssh_public_keys"... it's says that in that little step-by-step tutorial you're referring to.

---

[/quote]
[/quote]

well lets hope its true about access denied message, but it still does make users worry about the server not accepting the key.

With my configuration the problem was the format off the key.

Format :
---- BEGIN SSH2 PUBLIC KEY ----
Comment: "imported-openssh-key"
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==
---- END SSH2 PUBLIC KEY ----

is NOT understand by freeSSHd

I had to translate it to :
ssh-rsa xxxxxxxx ... xxxxxxxx== rsa-key-20061218

Quote:

---

Hi

I'm trying to access a windows 2003 server from a linux node.
I need the ssh to logon without the password to run some automated
scripts. It's a secure system so the password is not an issue.

I can get logged in if I supply the password, however
I need to get login with out the password.

Has anyone tried this from a Linux node?

I have copied the rsa and dsa public keys from the linux box to the
ssh_public_key file and set all of the other settings as described in this mail thread.

Any other ideas

thanks

-ken

---

I'm having the same problem using OpenSuSE PPC. I can connect if password is set, but when I try to set up shared key, I get this:

---snip---
ssh -v -i /root/.ssh/cypress cypress2@cypress
OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to cypress [172.31.14.72] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/cypress type 1
debug1: Remote protocol version 2.0, remote software version WeOnlyDo 1.3.5
debug1: no match: WeOnlyDo 1.3.5
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.4
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host 'cypress' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:5
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /root/.ssh/cypress
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: read PEM private key done: type RSA
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).
---/snip---

Going to keep slogging through it, but figured I'd see if anyone else had figured this out.

Quote:

---

With my configuration the problem was the format off the key.
is NOT understand by freeSSHd

I had to translate it to :
ssh-rsa xxxxxxxx ... xxxxxxxx== rsa-key-20061218

---

THANK YOU!!!

This really should be documented! Even better, don't let FreeSSH accept public keys in a format it can't understand. Or, better yet, accept the PuTTY format...

Try reading the step-by-step tutorial at the beginning of this thread. It clearly states you need to use a key in OpenSSH format.