full-disclosure - Corsaire Security Advisory - Multiple vendor MIME field multiple occurrence issue

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87wtyxpb54.fsf@deneb.enyo.de>
From: fw at deneb.enyo.de (Florian Weimer)
Subject: Corsaire Security Advisory - Multiple vendor MIME field multiple occurrence issue

> The first of the four would be the correct behaviour for a security 
> conscious product, but based on empirical research this is not the 
> common result. 

Of course, this violates the robustness principle.

Are there any estimates how much (corporate) mail contains one of the
format violations you described?  I could image that you can't reject
some of them because they are too widespread.