Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Bugtraq: Re: base64

Re: base64

From: Andrew Church <achurch_at_achurch.org>
Date: Thu, 25 Sep 2003 14:20:44 JST

>On Wed, Sep 24, 2003 at 03:13:57PM -0400, MightyE wrote:
>> I agree, I don't think it's unreasonable to reject improperly formatted
>> messages.
>
>> Take the low road
>> catchall, and simply reject them as a matter of course.
>
>this runs counter to the maxim of Postel
><http://www.postel.org/postel.html>:
>
>"Be liberal in what you accept, and conservative in what you send."

     It depends how you interpret it. I'd interpret the rejection as being
conservative on the sending side--leaving the data as is would violate
_that_. I could see an argument for correcting malformed data where
possible (e.g. cutting off all data after the first = sign), but that
raises the question of how to know that you're transmitting the same
content that the sender intended. Particularly in cases like this, where
the standard is ambiguous, the only "safe" options with respect to
preserving the content are to send the data on as is or reject it entirely,
and in that case I think Postel's maxim would lean toward rejection; the
"liberal" part is only for data you can accurately interpret.

  --Andrew Church
    achurch_at_achurch.org
    http://achurch.org/
Received on Sep 25 2003

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]