Tru64 ssh login through certificate

[Rakesh Jha_1]

I am running Tru64 V5.1B-4. I am trying ssh login to Linux ftp server using certificate. I have succesfully tested two users loggin to linux server using certificate but when I try the third one, whatever I do ssh/sftp login does not work and keep getting messages -
debug: Ssh2AuthClient/sshauthc.c:330: Method 'publickey' disabled.

I even tried to copy the working set of certificate from one user to other on both end but I kept on receiving the same error.

Any clue what I might be missing?

[Steven Schweda]

"certificate" or public key file?

"ftp server" or SSH/SFTP server?

Actual "ssh -v [...]" output might be more
useful than "does not work", which is pretty
uninformative.

Have you looked in the system log file(s) on
the server?

Are the key files in the right format?
Ownership? Permissions?

With only vague descriptions of what you did,
and what happened when you did it, it's hard
to say much.

[Ivan Ferreira]

Ensure that you have:

AllowedAuthentications hostbased,publickey,password

In the /etc/ssh2/sshd2_config file. Restart the service if you changed the value.

[Rakesh Jha_1]

I have been using publickey authentication. I tried publickey login to anothe user id on destination host it worked.

So situation is from a sourec I can do ssh/sftp to a account 'aaa' but not to 'aba' on same destination host.

Only difference between the two IDs is that the home directory of 'aba' has been put in share unde smaba.

Can this cause problem for publickey based authentication. As of now I have bypassed the porblem by doing sftp to aaa and then copying file from aaa to aba.

Thanks

[Ivan Ferreira]

The SAMBA home may be the problem, SSH is very strict with HOME directory permissions.

See man sshd2_config for the StrictModes parameter. Try setting StrictModes to NO.

[Steven Schweda]

> Try setting [...]

Or, as already suggested (with no apparent
effect), add "-v" to your "ssh" command, and
try to SEE WHAT'S HAPPENING, instead of
guessing.

Also, as usual, showing actual commands and
their actual output can be more helpful than
vague descriptions.