Changing ports

[Gene Dascher]

Thanks for all the suggestions.  I'll go home tonight and see how badly i
can screw things up!

Gene

> -----Original Message-----
> From: Brian Densmore [mailto:DensmoreB at ctbsonline.com]
> Sent: Wednesday, April 03, 2002 2:49 PM
> To: Gene Dascher
> Subject: RE: Changing ports
>
>
> > -----Original Message-----
> > From: Gene Dascher [mailto:gedascher at multiservice.com]
> > Sent: Wednesday, April 03, 2002 2:09 PM
> > To: Brian Densmore
> > Subject: RE: Changing ports
> >
> >
> > > Yes. no.
> > > But do be careful and check /etc/services first. Also if
> > you are using
> >
> > 	All I need to check /etc/services for is to verify that
> > another service is
> > not using that port, correct?
> No, the port needs to be listed and uncommented in /etc/services (I
> think, maybe that is only the privileged ports. Or maybe only inetd
> needs it). (It may also indicate a program that uses that port, nothing
> to worry about if you don't have the program) From what I understand.
>
> >
> > Can you be more clear about inetd?  What do I need to
> > check/do with that
> > (I'm assuming that would involve the inetd.conf file)?
> Yes. Make sure the port is not disabled there or that there is not some
> program attached to it (like /usr/bin/hookyservice). I think.
>
> >
> > > Changing default ports can become a hairy mess, if not handled and
> > > documented well. I don't do it, because security through
> > obscurity isn't
> > > really the best method.
> >
> > 	I am not trying to be obscure, just to be able to get
> > into my Home machine
> > from work, as the standard sshd port is blocked by our firewall.
> That's just nuts why block that port? So you're going to use an
> unprivileged port like port 2022? You should be fine then. And I forgot
> about the killall -SIGHUP . You may also be able to run /etc/init.d/sshd
> reload (or whatever & wherever your sshd boot script is)
>
> I'm not all sure about all this. I've never really messed with this
> stuff. You may be able to just change the config, killall and go. try
> it. If it works you got nothing to worry about. I just add all that
> paranoia stuff so if something doesn't work you where to start looking.
> Pick an obscure port and you likely won't have an issue.
>
> Good luck,
> Brian