full-disclosure - Re: OpenBSD Paradox

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: <AANLkTinZkmm5F4XTROu5SswOgc-oTGGF4ECNibTHD=sF@mail.gmail.com>
Date: Mon, 20 Dec 2010 16:29:06 -0800
From: coderman <coderman@...il.com>
To: Marsh Ray <marsh@...endedsubset.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: OpenBSD Paradox

On Mon, Dec 20, 2010 at 4:20 PM, Marsh Ray <marsh@...endedsubset.com> wrote:
> ...
> RFC 4301 (ahem, please watch your capitalization) says:
>>
>>  The spelling "IPsec" is preferred and used throughout this and all
>>   related IPsec standards.  All other capitalizations of IPsec (e.g.,
>>   IPSEC, IPSec, ipsec) are deprecated.  However, any capitalization of
>>   the sequence of letters "IPsec" should be understood to refer to the
>>   IPsec protocols.


iPsEc makes me sad in stack.

REGARDING PROOF; I CONCUR. OCCAM OVER.

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/