SFTP setup on openVMS question

[SAMI AHMAD]

i checked the server log file and its saying 'client send bad key'

and on the vms client the debug shows follows:

debug(20-NOV-2008 02:00:45.93): Constructing and sending signature in publickey authentication.
debug(20-NOV-2008 02:00:45.93): Ssh2AuthPubKeyClient/AUTHC-PUBKEY.C:869: ssh_client_auth_pubkey_send_signature: reading /DISK$ORACLE
Passphrase for key "/DISK$ORACLE/ORACLE9I/ssh2/ID_DSA_2048_A" with comment "2048-bit dsa, oracle@SUNNY2.to.dot.state.fl.us, Thu Nov
20 2008 06:14:49":

debug(20-NOV-2008 02:02:18.43): Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug(20-NOV-2008 02:02:18.43): Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 50 to connection
debug(20-NOV-2008 02:02:18.46): server offers auth methods 'publickey'.
debug(20-NOV-2008 02:02:18.46): Ssh2AuthPubKeyClient/AUTHC-PUBKEY.C:1899: Server rejected the signature.

[Steven Schweda]

> [...] do I still need to convert ?

What does the documentation for "freeSSHD"
say?

If you make keys using the "freeSSHD" key
generator (assuming that it has one), do they
look the same as or different from the keys
made using the TCPIP key generator?

[SAMI AHMAD]

The freeSSHD doesnt have a key generator of their own they ask to use puttygen which I used. The key I have inlcuded in my previous post and if you compare it with VMS key there is one extra line at top called 'subject'.
but freeSSHD is saying 'openvms sent a bad key' .. so shouldnt we be looking into how the key is generated at the vms side and how we can make it acceptable at the windows side?

[Steven Schweda]

> The key I have inlcuded in my previous post
> [...]

Those would seem to be the public keys. I
assume that there are also private keys.

I wouldn't publish the full content of all
these key files.

> but freeSSHD is saying 'openvms sent a bad
> key' [...]

I don't know whether that means that the key
data being sent were bad, or simply that the
key data being sent don't match any key data
on the server. (I can't see very much of the
server's log file.)

[SAMI AHMAD]

I fix the problem , the Identification file was missing and protection was wrong .
there is no conversion needed between keys on vms and windows so I am not sure why so many people are talking about key conversion here, this totally threw me off track.
thanks for all your help n suggestions

[Steven Schweda]

> there is no conversion needed between keys
> on vms and windows so I am not sure why so
> many people are talking about key
> conversion here,

Probably because so many other people (using
OpenSSH) need to convert their keys. Here, I
see only one person who said that "the key
format needs to be converted", and one who
suggested that you _might_ need to convert
them. Is that "so many"?

> this totally threw me off track.

That was easy.

If the different SSH software products use
different key formats, then you need to
convert the keys. If not, then you don't.
People who know nothing about "freeSSHD on
windows" probably don't know which key format
it uses. Some, apparently, would assume that
it would match OpenSSH, which, apparently, it
doesn't. It was pretty deep into the
discussion before we got to see only one of
the "freeSSHD" key formats. Better questions
often lead to better answers.