01-11-2007
i am unfamiliar with the software you are using, but ssh1/scp1 coupled with the term "compatibility mode" sounds like the protocol version error with ssh? Perhaps your ssh server only allows ssh v2 (which is good) but your client may not support ssh v2.
Check the SSH server config and see if it allows v1 and v2, and check your client to see what it's compatible with. Maybe your client has to be specifically told to negotiate ssh v2 with a command line option (if it's graphical, there should be a setting for that also).
I wouldnt change the ssh server to allow v1 if it doesnt already. v2 is the way to go.
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello All,
I was wondering if the titlebar in "F-Secure SSH Client for Windows" is changeable. Currently I see the host name in the title bar. I would like to add "user@host" to the title. So when I log on to a particular box and do a ssh to another box the title should dynamically... (3 Replies)
Discussion started by: ssikhar
3 Replies
2. HP-UX
How to ftp file to secure server. Can somebody pls guide. (1 Reply)
Discussion started by: rkkiran
1 Replies
3. Solaris
Hi,
I would like to login from a Sun server running ssh:
Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
to
ssh: SSH Secure Shell 3.0.1 on sparc-sun-solaris2.6
How can I achieve this?
Thanks a million in advance (1 Reply)
Discussion started by: newbewie
1 Replies
4. UNIX and Linux Applications
Folks
I am on a quest....
I am looking for a lightweight FTP client capable of FTPS and or SFTP that has good audit and logging capabilities without requiring a central server component. My platforms are Linux, Solaris, AIX, and Windows Server.
The kicker is I have found things that meet the... (3 Replies)
Discussion started by: ArtF
3 Replies
5. UNIX for Advanced & Expert Users
hi,
what is the difference between logging into unix through f-secure ssh client and telnet
is there any more security check is involved
can any one explain
thanks in advance (1 Reply)
Discussion started by: trichyselva
1 Replies
6. Cybersecurity
Dear all,
I am instructed to use a licensed software on network. There are several ways of doing it, one of which includes using AFS, getting modules, etc.
I am not so sure about the security. I would not like the situation where people actually can see my data. Being an apprentice, I need... (2 Replies)
Discussion started by: apprentice
2 Replies
7. UNIX for Advanced & Expert Users
Hi,
I am facing problems whie trying to do a passwordless ssh to Unix box from windows. Public key was generated using F-secure. When the F-secure client attempts it connects without password but when I try to use sftp2 in command line it prompts for password.
I have tried several options and... (0 Replies)
Discussion started by: dhrajj
0 Replies
8. Linux
Hi,
I am facing problems whie trying to do a passwordless ssh to Unix box from windows. Public key was generated using F-secure. When the F-secure client attempts it connects without password but when I try to use sftp2 in command line it prompts for password.
I have tried several options and... (3 Replies)
Discussion started by: dhrajj
3 Replies
LEARN ABOUT POSIX
ssh-keysign
ssh-keysign(1M) ssh-keysign(1M)
NAME
ssh-keysign - ssh helper program for host-based authentication
SYNOPSIS
ssh-keysign
ssh-keysign is used by ssh(1) to access the local host keys and generate the digital signature required during host-based authentication
with SSH protocol version 2. This signature is of data that includes, among other items, the name of the client host and the name of the
client user.
ssh-keysign is disabled by default and can be enabled only in the global client configuration file /etc/ssh/ssh_config by setting Host-
basedAuthentication to yes.
ssh-keysign is not intended to be invoked by the user, but from ssh. See ssh(1) and sshd(1M) for more information about host-based authen-
tication.
/etc/ssh/ssh_config
Controls whether ssh-keysign is enabled.
/etc/ssh/ssh_host_dsa_key
/etc/ssh/ssh_host_rsa_key
These files contain the private parts of the host keys used to generate the digital signature. They should be owned by root, readable
only by root, and not accessible to others. Because they are readable only by root, ssh-keysign must be set-uid root if host-based
authentication is used.
ssh-keysign will not sign host-based authentication data under the following conditions:
o If the HostbasedAuthentication client configuration parameter is not set to yes in /etc/ssh/ssh_config. This setting cannot be overri-
den in users' ~/.ssh/ssh_config files.
o If the client hostname and username in /etc/ssh/ssh_config do not match the canonical hostname of the client where ssh-keysign is
invoked and the name of the user invoking ssh-keysign.
In spite of ssh-keysign's restrictions on the contents of the host-based authentication data, there remains the ability of users to use it
as an avenue for obtaining the client's private host keys. For this reason host-based authentication is turned off by default.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsshu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
ssh(1), sshd(1M), ssh_config(4), attributes(5)
AUTHORS
Markus Friedl, markus@openbsd.org
HISTORY
ssh-keysign first appeared in Ox 3.2.
9 Jun 2004 ssh-keysign(1M)