Re: Need urgent help regarding security

ray_at_redshift.com
Date: 11/21/05

  • Next message: Andriy Gapon: "mount -u -r drops nosuid ?" 
    Date: Mon, 21 Nov 2005 04:37:23 -0800
To: Marian Hettwer <MH@kernel32.de>, Peter Jeremy <PeterJeremy@optushome.com.au>

    At 10:15 AM 11/21/2005 +0100, Marian Hettwer wrote:
    | Hi there,
    |
    | Peter Jeremy wrote:
    | > On Mon, 2005-Nov-21 09:33:07 +0100, Marian Hettwer wrote:
    | >
    | >>ray@redshift.com wrote:
    | >>
    | >>>Also, if you have access to the router, it's handy to re-write
    | >>>traffic from a higher public port down to port 22 on the server,
    | >>>since that will trip up anyone doing scans looking for a connect on
    | >>>port 22 across a large number of IP's.
    | >>>
    | >>
    | >>No. That's security by obscurity and doesn't make your system even a wee
    | >>bit more secure.
    | >
    | >
    | > It depends what you are guarding against. If someone wants to get into
    | > _your_ system then it's worthless. OTOH, "you don't have to run faster
    | > than the bear, just faster than someone else": Moving your ssh access
    | > off port 22 means that someone doing a network scan of port 22 won't
    | > see your system. This is reasonable protection against script kiddies.
    | >
    | Where is the protection, or rather the danger in being "visible" to
    | script kiddis? There's no security issue valid for script kiddis which
    | wouldn't be valid for any other attacker too.
    | The main question is: Where is the danger in script kiddies with their
    | brute force attacks?
    | I guess it's mainly the annoying fact that your logfile get's
    | unreadable. If that's the problem: use logsurfer or something similar to
    | analyze the logfile.
    | You just don't get more secure by moving the sshd to a different port
    | than port 22.

    The point isn't to get more secure. You are correct by saying that moving the
    port # doesn't make anything more secure. But why make it easy for someone that
    might be doing a scan to find your SSH prompt during a scan that may be focused
    on ports 21, 22, 25, 80 and 110?

    Along these same lines, we used to even re-compile sshd and remove the welcome
    message/version number in the connect. I know there are two schools of thought
    on broadcasting your version numbers on connections, but in the mid 90's, we did
    do that from time to time.

    Anyway, to each their own :)

    Ray

    _______________________________________________
    freebsd-security@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-security
    To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"

  • Next message: Andriy Gapon: "mount -u -r drops nosuid ?"

    Relevant Pages

    • Re: Created on Access 2003, but.......................
      ... But that's not secure under any scenario, as any port scanner ... Well, you still need a userid, password and database name. ... You're assuming the server remains in a secured configuration. ...
      (comp.databases.ms-access)
    • Re: 553 sorry, relaying denied from your location
      ... connection on port 465. ... Newly created server is on port 465, ... iterations of secure, always secure, 128 bit encryption, etc. ... that doesn't appear to be an Exchange response. ...
      (microsoft.public.exchange.setup)
    • RE: RE: break in? - terminal services on alternate port
      ... Some thoughts on moving ports. ... Moving the TS port is for the most part unnecessary, ... Services to authorized users of your network. ... do use terminal services you should enable both successful and failed ...
      (Focus-Microsoft)
    • Re: Help, my machine has been hacked
      ... > being used to perform port scans on a bank. ... > closed HTTP) ... > DSLReports and they all report that my machine is secure. ... > 4) Recommendations for a hardware firewall? ...
      (comp.os.linux.security)
    • RE: Remote Desktop & Terminal Services Security
      ... RDP is as secure as your password policy, i.e. if users have strong passwords ... RDP is natively encrypted via 128-bit, ... one port is required for TS to operate, ... I have never seen or heard of a cracked network due to vulnerability in the ...
      (microsoft.public.windows.terminal_services)