LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Configuration of SSH daemon on Slackware 9.1 - Newbie (https://www.linuxquestions.org/questions/slackware-14/configuration-of-ssh-daemon-on-slackware-9-1-newbie-125662/)

BenChase 12-14-2003 12:05 AM

Configuration of SSH daemon on Slackware 9.1 - Newbie
 
Hello folks,

First off, I'm new to Linux. I've got a good background in the Cisco IOS CLI, so I'm familar with a lot of the syntax, and I've written Perl scripts on Windows machines, so I can comprehend regular expressions fairly well. I appreciate any help that can be provided.

Here's my question:

I would like to enable SSH access to my slackware box from the outside world. I have a static IP and NAT enabled, and have already forwarded port 22 through my AP to redirect to my internal IP for the slackware box.
The end result is for me to SSH across the internet to my slackware machine and work on the box and/or transfer files to/from my 2 windows XP machines. I'm not too worried about setting up ftp or sftp right now, I just want to get SSH down well. I have a SSH client on my laptop at work (windows XP).

I have Slackware 9.1 installed on a PIII 600mhz machine. SCSI CD-RW and SCSI 9.1GB HDD.

I've looked at the man pages for SSHD and I am not sure about how to set up the configuration.

I thank you in advance for any assistance.


Ben
:newbie:

DaHammer 12-14-2003 12:44 AM

It should be setup pretty well by default. You shouldn't have to do much of anything to get it working except start the server, unless you need some customization of one aspect or another. The config files for it are in /etc/ssh/. And you can start the server by making it's startup script executable:

chmod 755 /etc/rc.d/rc.sshd

and then start it:

/etc/rc.d/ec.sshd start


By making the startup script executable, it should be started by default when you boot the PC from then on. If not, then check rc.inet2 to make sure it's not commented out.

BenChase 12-14-2003 06:09 PM

I'll give that a try. Thanks!

timdsmith 12-14-2003 07:06 PM

if you still can't connect, your workplace firewall may be blocking port 22. A lot of corp. firewalls block that port. You might have to change the default port it listens on. Most corp. firewalls do not block port 53, 80, or 443.

BenChase 12-14-2003 09:23 PM

Fortunately, I have control over our PIX and routers, so I can ensure that only my IP is allowed to use port 22 outgoing. :)

timdsmith 12-14-2003 10:46 PM

Very nice! Wish they'd give me that control at work. I have to hunt for open ports. :)

BenChase 12-14-2003 10:50 PM

Well, it's the least I can ask for, considering that it's my job :)

Maybe a little nmap -sS is what you need :) I don't know of any better tool to find open ports :)

timdsmith 12-14-2003 10:57 PM

LOL. Well I guess so if that's your job. :)
I have discovered all the open ports I need at the moment, but I will remember that in the future! Thanks!


All times are GMT -5. The time now is 06:56 PM.