full-disclosure - Responsibility

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: <4475B379.80707@csuohio.edu>
Date: Thu May 25 14:40:37 2006
From: michael.holstein at csuohio.edu (Michael Holstein)
Subject: Responsibility

> My question then is - if you have done the utmost to lock down your
> customer
> but someone connects an infected machine and somehow it gets in, is the
> customer right in suing you? 

Doesn't matter. In the U.S. you can sue anybody for anything .. no 
matter how stupid or frivolous it might be.

Jury(n) : 12 people who decide who hired the better lawyer.

/mike.