Overview
Updated 20th December 2001: SecureShell 1.2.32 released. Secure shell is a encryption protocol/program for sending and receiving information via possibly insecure networks. This allows you to login to remote machines in a way where the passwords and information are encrypted against possible sniffers/intrusion, that can detect the plain ASCII user names passwords that would normally flow using standard telnet, ftp and other unencrypted protocols. (An old version of this tutorial for Secure Shell 1.2.27 with manual application of patches is still viewable) |
|
|
Bear in mind, some or all of the following could be wrong or non-optimal. Thus this information should
not be considered as a substitute for thinking for yourself.
Download and Install Secure Shell
|
Enhancing the Security of the system by disabling unneccessary deamonsOverall, the idea here is that any unneccessary deamon that runs is a possible entry point for a hacker. Thus only running what you require in a safe manner lessens the chance you system will be compromised and data ruined. The following primarily consists of killing off unneeded deamons in the /etc/inetd.conf. They can always be enabled later on if you find that you do need some of them to run.
Compiling SecureShell on Redhat 6.0 problems. "There are some pb with the compilation of SSH 2 and Redhat 6.0 To fix your problem: step 1 : execute ./configure step 2: edit the sshconf.h file generated by configure step 3: comment out the line #define HAVE_UTMPX_H 1 step 4: save & run make step 5: make install It worked for me. Good luck"(Lachlan's Note 19th May 1999: This could already be fixed as when I compiled up 1.2.27, I did not have a problem)
Problem with compiling up ssh 1.2.27 on an old Indy running IRIX 6.5.xFrom: [email protected] (Greg Bacon) Newsgroups: comp.security.ssh Subject: Re: ssh 1.2.27 failing to decrypy keys on make install? Date: 1 Jun 1999 21:40:38 GMT Organization: The University of Alabama in Huntsville References: [[email protected]> Reply-To: Greg Bacon [[email protected]> In article [[email protected]>, [email protected] (Lachlan Cranswick) writes: : ON an old SGI Indy running IRIX 6.5x, with gcc 2.8.1. : : On make install of ssh 1.2.7 - the make just continuous : generates keys, tests the keys, then gives a : "private+public failed to decrypt" Turning down the optimization level has usually solved this problem for me on IRIX boxen. Greg -- Must one first batter their ears, that they may learn to hear with their eyes? Must one clatter like kettledrums and penitential preachers? Or do they only believe the stammerer? -- Nietzsche
Getting ssh to run on startup on an SGI running IRIXFrom: [email protected] (Andreas Werner) Newsgroups: comp.sys.sgi.admin Subject: Re: sshd Date: 8 Apr 2000 19:42:51 GMT Organization: Comp.Center (RUS), U of Stuttgart, FRG there are lots of ways to do this, but the SGI typical way is: 1. Create a file /etc/init.d/sshd containing the following: ==================================== #! /bin/sh # # start up ssh server at boot # case "$1" in 'start') if /sbin/chkconfig sshd ; then if test -x /usr/local/sbin/sshd; then /usr/local/sbin/sshd fi fi ;; 'stop') /sbin/killall sshd sshd1 ;; *) echo "usage: $0 {start|stop}" ;; esac # ==================================== 2. Create two links: # ln -s ../init.d/sshd /etc/rc0.d/K01sshd # ln -s ../init.d/sshd /etc/rc2.d/S99sshd 3. Create a config variable: # chkconfig -f sshd on That's all, including the possibility to configure the daemon on or off woth the 'chkconfig' command. For the experts: Yes, I know that the 'killall' command will kill user ssh daemons, too, but that's exactly the thing I want when the machine shuts down ;-) |