SSH 3.1.0 non-comercial

[W3iRd0]

Please tell me that there is a way to configure it to actually run on OS X, I can connect to other servers, but not start up my own (unless I replace OpenSSH's sshd with sshd2 from SSH 3.1.0 and it still doesn't do what I tell it...), my friends computer won't even start up the OpenSSH daemon...

Please help.

[mervTormel]

w31rd0,

more info please. what do you tell it to do? what does it say it did/is doing?

any illuminating console messages? system.log msgs?

this faq:

http://www.ssh.com/faq/index.cfm?product=1

regards ssh -V to be a good starting point after resolving any connectivity issues.

[W3iRd0]

I downloaded the SSH 3.1.0 non-commercial package, compiled and installed. The only way I could get the sshd2 deamon to start up, was to copy it over the sshd deamon that comes with Mac OS X.
I tried to start it any other way, this came:
-----------------------
sshd2[26496]: WARNING: Parsing of value for AllowedAuthentications failed.
sshd2: SSH Secure Shell 3.1.0 (non-commercial version) on powerpc-apple-darwin5.2
sshd2[26496]: WARNING: Host key pair is not specified, trying to use default 'hostkey'.
sshd2[26496]: FATAL: Creating listener failed: port 22 probably already in use!
-----------------------
When my friend tried to start SSH up (using my method), he gets:
------------------
/etc/hostconfig : unmatched[30]
------------------
in the console (The problem was there before the upgrade to SSH 3.1.0).

Another thing is, that no matter what I try, I can't figure out which config file it uses, none of my changes have had any effect...
Any thoughts?

p.s. why would checking the version on the client do me any good? As i said, connecting is not a problem, setting up the deamon is....

[mervTormel]

w31rd0,

z. stop making changes that you can't put back to how they were before your changes or you could make it worse than before your changes were changed :D

a. your friend's hostconfig has a typo in it

b. ssh -V is not the version switch, it's the Verbose switch, very useful for debugging

and

c. don't these secure tools like you to generate authorized key files with ssh-keygen or some such and tell the daemon where they are in sshd_config or else they go to stick their fingers in yer key pool and flat out die horrible and stinky deaths and don't tell you much about it cuz that's how security works, and if it went and told you then, well, how secure is that?

i claim ignorance up front about this, but the fatal error may be false and due to an accumulation of previous warnings and just plain can't turn the corner because so many pieces are missing (or changed ;=)

the man pages on my sshd install (fink) are very illuminating, so is the sshd_config file. perhaps google for a how-to sshd2 ?

where are your ssh hostkey files that your installation can't find?

% ll /etc/ssh*
-rw-r--r-- 1 root wheel 1.0k Sep 2 20:47 /etc/ssh_config
-rw------- 1 root wheel 672 Dec 12 21:35 /etc/ssh_host_dsa_key
-rw-r--r-- 1 root wheel 599 Dec 12 21:35 /etc/ssh_host_dsa_key.pub
-rw------- 1 root wheel 524 Dec 12 21:35 /etc/ssh_host_key
-rw-r--r-- 1 root wheel 328 Dec 12 21:35 /etc/ssh_host_key.pub
-rw------- 1 root wheel 883 Dec 12 21:35 /etc/ssh_host_rsa_key
-rw-r--r-- 1 root wheel 219 Dec 12 21:35 /etc/ssh_host_rsa_key.pub
-rw-r--r-- 1 root wheel 1.7k Sep 2 20:47 /etc/sshd_config

[W3iRd0]

The hostkeys are where they should be, the problem is of a different nature. I installed SSH and I want to use that instead of OpenSSH. The only way I know how, is to copy /usr/local/sbin/SSHD2 over /usr/sbin/SSHD. Then my SSH deamon starts up via the System Prefs app. But I can't figure out how to configure the deamon, I have tried Google, and the ssh.com web page. I posted my problem here because I need help and can't find answers anywhere else. The Fatal error I get is because inetd reserves ALL port numbers that I know of, even if they are not in use. I can't figure out how to circumvent that either.

[W3iRd0]

----------------------------
Usage: ssh [options] host [command]
Options:
-l user Log in using this user name.
-n Redirect input from /dev/null.
-F config Config file (default: ~/.ssh/config).
-A Enable authentication agent forwarding.
-a Disable authentication agent forwarding (default).
-X Enable X11 connection forwarding.
-x Disable X11 connection forwarding (default).
-i file Identity for public key authentication (default: ~/.ssh/identity)
-t Tty; allocate a tty even if command is given.
-T Do not allocate a tty.
-v Verbose; display verbose debugging messages.
Multiple -v increases verbosity.
-V Display version number only.
-P Don't allocate a privileged port.
-q Quiet; don't display any warning messages.
-f Fork into background after authentication.
-e char Set escape character; ``none'' = disable (default: ~).
-c cipher Select encryption algorithm
-m macs Specify MAC algorithms for protocol version 2.
-p port Connect to this port. Server must be on the same port.
-L listen-port:host:port Forward local port to remote address
-R listen-port:host:port Forward remote port to local address
These cause ssh to listen for connections on a port, and
forward them to the other side by connecting to host:port.
-D port Enable dynamic application-level port forwarding.
-C Enable compression.
-N Do not execute a shell or command.
-g Allow remote hosts to connect to forwarded ports.
-1 Force protocol version 1.
-2 Force protocol version 2.
-4 Use IPv4 only.
-6 Use IPv6 only.
-o 'option' Process the option as if it was read from a configuration file.
-s Invoke command (mandatory) as SSH2 subsystem.
-b addr Local IP address.
----------------------------
I just had to..