Security Basics mailing list archives
Re: Re[3]: HTTP Headers
From: List Spam <listspam () gmail com>
Date: Wed, 18 Jan 2006 10:24:06 -0800
On 1/17/06, Thierry Zoller <Thierry () zoller lu> wrote:
LS> I would seriously caution against relying upon data presented by a LS> service banner - whether it be HTTP, FTP, SSH, whatever. AFAIK, the banner of SSH is part of protocol negotiation, changing it would result in problems. Thus for ssh you can rely on banners most of the time..
The protocol version needs to be present, but the server daemon version can be changed. While it is true that some clients interpret the daemon specific banner information to determine how they will communicate to a given daemon, the only required component is the protocol version portion of the banner. One example would be an edit to version.h in the OpenSSH source. Thanks for the clarification though as I wasn't concise with my info. --------------------------------------------------------------------------- EARN A MASTER OF SCIENCE IN INFORMATION ASSURANCE - ONLINE The Norwich University program offers unparalleled Infosec management education and the case study affords you unmatched consulting experience. Tailor your education to your own professional goals with degree customizations including Emergency Management, Business Continuity Planning, Computer Emergency Response Teams, and Digital Investigations. http://www.msia.norwich.edu/secfocus ---------------------------------------------------------------------------
Current thread:
- HTTP Headers wshepherd (Jan 13)
- <Possible follow-ups>
- Re: HTTP Headers jbearce (Jan 13)
- Re: HTTP Headers List Spam (Jan 13)
- Re: Re: HTTP Headers wshepherd (Jan 16)
- RE: Re: HTTP Headers Rubin, Greg (Jan 16)
- Re: Re: HTTP Headers List Spam (Jan 17)
- Re[3]: HTTP Headers Thierry Zoller (Jan 18)
- Re: Re[3]: HTTP Headers List Spam (Jan 20)
- Re: Re: HTTP Headers List Spam (Jan 17)
- Re: HTTP Headers wshepherd (Jan 17)
- Re: HTTP Headers Byron Sonne (Jan 20)
- Re: HTTP Headers insecure (Jan 20)