full-disclosure - Just a suggestion

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: <200208290925.56745.steve@videogroup.com>
From: steve at videogroup.com (Steve)
Subject: Just a suggestion

On Wednesday 28 August 2002 04:39 pm, Snow, Corey wrote:
>OK, I'll bite. You'll first have to define "intended" and "disrupt". With a
>policy like this, the determination of what is "intended" to "disrupt" is

Yes it would be defined fully and completely. 
I'll read up on how the list is defined and post my sample "rules" and we'll 
see. (I'll keep it off list to those who are interested.)
-- 
 
Steve Szmidt
V.P. Information Technology
Video Group Distributors, Inc.