[ale] ssh version 1 and ssh -X
Dow Hurst
dhurst at kennesaw.edu
Tue May 6 19:32:11 EDT 2003
You can read the man page to figure how to setup the command line OR
the simple way out is to grep the Makefiles under the ssh compile for
the auto-key generation line when it runs the installation routines.
That was how I grabbed it quick when I wanted to regenerate the host
key. Just grep for ssh-keygen in the Makefiles and you will eventually
find it.
OFFTOPIC tidbit:
For those not using OpenSSH but using ssh.com's version of ssh and
having need to compile for MIPS-1 or MIPS-2 for an SGI Indy or Indigo2,
you have to take the "-n32" option out of the configure.in script where
compile options are passed. You have to touch the file to the same date
or you will need some configure processing tool that you really don't
need. And, finally you have to set the C_FLAGS and LD_FLAGS variables
to contain "-mips-2" by setting these as environment variables. Only
then can you run configure and make. I was trying to compile on an
Octane which is MIPS-4 and passing "-mips-2" but the "-n32" option
overrides the "-mips-2". Then, you can tar gzip the whole directory
structure, move it to your target machine, gunzip, untar, and run make
install. I imagine the basic procedure could work for other
architectures once the flags were set correctly. I used SGI's cc and
not gcc. Haven't had to deal with this in the Linux world yet.
Dow
Jerry Yu wrote:
> you need to tell it to save to /etc/ssh/ssh_host_key or alike
>(-f outputFileName). By default keygen thinks you wants to generate key
>pair for user instead of for the host/server.
>
>
> On Tue, 6 May 2003, Robert L. Harris wrote:
>
>#
>#
>#Odd:
>#
>#0}:/etc/init.d>ssh-keygen -t rsa1
>#Generating public/private rsa1 key pair.
>#Enter file in which to save the key (/root/.ssh/identity):
>#/root/.ssh/identity already exists.
>#Overwrite (y/n)? y
>#Enter passphrase (empty for no passphrase):
>#Enter same passphrase again:
>#Your identification has been saved in /root/.ssh/identity.
>#Your public key has been saved in /root/.ssh/identity.pub.
>#The key fingerprint is:
>#21:9c:19:1d:66:8b:dc:90:28:63:87:89:c5:92:19:c0 root at wally
>#
>#root at wally
>#{0}:/etc/init.d>./ssh restart
>#Disabling protocol version 1. Could not load host key
>#Restarting OpenBSD Secure Shell server: sshdDisabling protocol version 1.
>#Could not load host key .
>#
>#{0}:/etc/init.d>ls -la /root/.ssh/identity
>#-rw------- 1 root root 525 May 6 10:44 /root/.ssh/identity
>#
>#
>#Any thoughts?
>#
>#
>#Thus spake Jerry Yu (z.yu at voicecom.com):
>#
>#> #{1}:/etc/init.d>./ssh restart
>#> #Disabling protocol version 1. Could not load host key
>#> #Restarting OpenBSD Secure Shell server: sshdDisabling protocol version
>#> #1. Could not load host key
>#> #
>#> #I have RSA and DSA keys...
>#>
>#>
>#> version 2 key can be RSA or DSA type ( -t rsa|dsa switch for
>#> keygen)
>#> version 1 key have to be RSA (use -t rsa1 for keygen).
>#>
>#> _______________________________________________
>#> Ale mailing list
>#> Ale at ale.org
>#> http://www.ale.org/mailman/listinfo/ale
>#
>#:wq!
>#---------------------------------------------------------------------------
>#Robert L. Harris | PGP Key ID: E344DA3B
># @ x-hkp://pgp.mit.edu
>#DISCLAIMER:
># These are MY OPINIONS ALONE. I speak for no-one else.
>#
>#Diagnosis: witzelsucht
>#
>#IPv6 = robert at ipv6.rdlg.net http://ipv6.rdlg.net
>#IPv4 = robert at mail.rdlg.net http://www.rdlg.net
>#
>
>Jerry Yu +1-404-487-8544 (O)
>systems engineer jerry.yu at voicecom.com
>is support, voicecom, llc www.voicecom.com
>
>_______________________________________________
>Ale mailing list
>Ale at ale.org
>http://www.ale.org/mailman/listinfo/ale
>
>
>
--
__________________________________________________________
Dow Hurst Office: 770-499-3428
Systems Support Specialist Fax: 770-423-6744
1000 Chastain Rd. Bldg. 12
Chemistry Department SC428 Email: dhurst at kennesaw.edu
Kennesaw State University Dow.Hurst at mindspring.com
Kennesaw, GA 30144
*****************************************************************
This message (including any attachments) contains confidential *
information intended for a specific individual and purpose, *
and is protected by law. If you are not the intended recipient,*
you should delete this message and are hereby notified that *
any disclosure, copying, or distribution of this message, or *
the taking of any action based on it, is strictly prohibited. *
*****************************************************************
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale
More information about the Ale
mailing list