Re: [Full-Disclosure] Re: Re: open telnet port

From: Andrew Haninger (ahaning_at_gmail.com)
Date: 09/09/04

  • Next message: Todd Towles: "RE: [Full-Disclosure] Re: Re: open telnet port" 
    To: ktabic <lists@ktabic.co.uk>
Date: Thu, 9 Sep 2004 09:41:20 -0400

    > How about, as a service to enable as you are updating SSH remotely from
    > the other side of the country to fix the most recent problem security
    > problem and need a backup system to get into the server in the event
    > that something goes wrong?
    Maybe it would work as well, to start a ssh daemon on a high port,
    login on that high port, update the current sshd, start it up on port
    22, logout of the high port, login on port 22, and kill the high-port
    sshd.

    So,

    [foo@box.com ~] sshd -p 6000
    [bar@xob.com ~] ssh foo@box.com -p 6000
    [foo@box.com ~] [kill sshd running on port 22]
    [foo@box.com ~] [make and install new sshd]
    [foo@box.com ~] sshd
    [bar@xob.com ~] ssh foo@box.com
    [kill sshd running on port 6000]

    This would nearly eliminate any danger due to your insecure version of
    sshd since it would be running on a non-standard port for a brief
    period of time, and you would not be passing any passwords in the
    clear.

    -Andy

    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.netsys.com/full-disclosure-charter.html

  • Next message: Todd Towles: "RE: [Full-Disclosure] Re: Re: open telnet port"

    Relevant Pages

    • How did this happen?
      ... May 12 06:50:43 localhost sshd: Failed password for illegal user ... cgi from 212.93.149.205 port 2265 ... Starting sshd: ...
      (comp.os.linux.security)
    • Re: [Full-Disclosure] Re: Re: open telnet port
      ... > login on that high port, update the current sshd, start it up on port ... So the solution to not run a backup telnet server for updating SSH is to ...
      (Full-Disclosure)
    • Re: bypassing employers proxy to surf anonymously
      ... port 443, so it's harder to distinguish from an https server. ... through the remote sshd. ... You have an option to go with a managed service or an enterprise software. ...
      (Pen-Test)
    • RE: possible ssh hack
      ... What version of SSHD were you running, ... Apache and we can help you out. ... Subject: possible ssh hack ... port 4207 ...
      (Incidents)
    • Re: Possible New Security Tool For FreeBSD, Need Your Help.
      ... We just want to hide the sshd port until we need it. ... >> the Internet where would they put the sniffer? ... Do a traceroute between the host you're ...
      (FreeBSD-Security)
    Loading