Full Disclosure mailing list archives
Re: SNMP Broadcasts
From: Mohit Muthanna <mohit.muthanna () gmail com>
Date: Fri, 16 Jul 2004 17:52:35 -0400
No, not at all. There's a big difference between a *standardized service* and it's underlying protocols. In order to be SSH, it must comply with all of the standards for SSH. Otherwise, you get a M$ Windows product.
I was trying to stay away from this thread, but anyhow: If you've ever read RFCs before, you would be familiar with terms like MUST, SHOUD, MAY, MANDATORY etc. There is no document that says that in order to be "standard" SSH the listen port MUST be 22. Or tcp/22 is the MANDATORY port for SSH. The document only says that SSH "normally" uses port 22. The IANA has assigned port 22 for ssh, but this doesn't mean that you're not complying with the SSH standard by listening on an alternate port. That's it. For all practical purposes, no matter what port the daemon listen's on, it _IS_ SSH. -- Mohit Muthanna [mohit (at) muthanna (uhuh) com] "There are 10 types of people. Those who understand binary, and those who don't." _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- Re: SNMP Broadcasts, (continued)
- Re: SNMP Broadcasts Mohit Muthanna (Jul 14)
- Re: SNMP Broadcasts Martin Wasson (Jul 15)
- Re: SNMP Broadcasts J.A. Terranson (Jul 15)
- Re: SNMP Broadcasts tshilson (Jul 15)
- Re: SNMP Broadcasts Barry Fitzgerald (Jul 16)
- Re: SNMP Broadcasts J.A. Terranson (Jul 16)
- Re: SNMP Broadcasts Barry Fitzgerald (Jul 16)
- Re: SNMP Broadcasts J.A. Terranson (Jul 16)
- Re: SNMP Broadcasts Barry Fitzgerald (Jul 19)
- RE: SNMP Broadcasts Yaakov Yehudi (Jul 19)
- Re: SNMP Broadcasts J.A. Terranson (Jul 15)
- Re: SNMP Broadcasts Mohit Muthanna (Jul 16)
- Re: SNMP Broadcasts tshilson (Jul 16)