full-disclosure - RFC 3514 released

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

Message-ID: <000601c2f813$aae7a4d0$0400a8c0@main.gaddis.org>
From: jeremy at gaddis.org (Jeremy Gaddis)
Subject: RFC 3514 released

> -----Original Message-----
> From: full-disclosure-admin@...ts.netsys.com 
> [mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of 
> Darren Reed
> Sent: Monday, March 31, 2003 9:10 PM
> To: full-disclosure@...ts.netsys.com
> Subject: Re: [Full-Disclosure] RFC 3514 released
> 
> 
> > RFC 3514: The Security Flag in the IPv4 Header
> 
> I suppse we'll be expected to implement featurisms to support 
> this now...
> 
> sigh...where will it end ???

BAHAHAHAHAHA

Perhaps you'll want to look into implementing the security
flag in IPv4 packets sent over avian carriers? (RFC2549)

*grins and looks at the clock*

j.

--
Jeremy L. Gaddis   <jeremy@...dis.org>   <http://www.gaddis.org>