full-disclosure - SNMP Broadcasts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <3996AE5EBEF964418D80953BDCABFF560993999D@ex1.asurite.ad.asu.edu>
From: Stephen.Blass at asu.edu (Stephen Blass)
Subject: SNMP Broadcasts

>Actually, please point me to the SSH standard document and section that lists that sshd *must* run on TCP port 22 to be a valid SSH server. 

It doesn't.  It (http://www.ietf.org/internet-drafts/draft-ietf-secsh-transport-18.txt) says
"4.1  Use over TCP/IP

   When used over TCP/IP, the server normally listens for connections on
   port 22.  This port number has been registered with the IANA, and has
   been officially assigned for SSH.
"

Note that it says the server _normally_ listens for connections on port 22.  It does not say MUST or even SHOULD.   

-
Steve Blass
sblass@....edu