RE: [Owasp-input-api-developers] Vision Document

[Matt W. <wi...@ce...>]

On Mon, 2002-08-12 at 22:26, Christopher Todd wrote:
[...]
> 3)  What is meant by "correctly 'Huffman Encoded' interfaces"?  This isn't
> an objection so much as a point of clarification -  maybe I'm a total
> ignoramus, but I ususally assume that if I don't know what something means,
> I'm probably not the only one. 
While I know what Huffman Encoding is, wrt text compression, I too fail
to understand what "correctly 'Huffman Encoded' interfaces" really
means.

> 
> 4)  I am not sure I understand the whole boundary filter idea.  I don't
> necessarily want to re-hash something that's already been discussed, but if
> someone could provide a simple description or example, I'd appreciate it.  I
> know what boundary checking is, I'm just not sure you're talking about the
> same thing.

The boundary idea is pretty simple.  Its basically deciding when you
need to filter the data. 

For example, filtering SQL injection is something you would want to do
on input, when the user sends there data. However, filtering XSS might
be something you wish to do when displaying said data.

> 
> 5)  I think we will need to consider a wider character set than UTF-8, for
> I18N reasons.  This may present a porting challenge, as different languages
> have differing levels of support for Unicode (just to cite one possible
> encoding).
Bah.
> 
> 6)  There are numerous typos and grammatical errors that I'll try to fix
> when I convert this to DocBook this weekend.
Here we go again :>

-matt
-- 
Matthew Wirges
Developer, CERIAS Incident Response Database
wi...@ce...