full-disclosure - InfoSec sleuths beware ...

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: <1077225732.32618.23.camel@puffin.tamucc.edu>
From: michael at puffin.tamucc.edu (michael williamson)
Subject: InfoSec sleuths beware ...

And you think this could be reliably implemented on a mickeysoft
platform?  

On Thu, 2004-02-19 at 08:07, Exibar wrote:
--snip--
>    I would think that a more controllable environment would be a laptop that
> must phone home every 5 minutes of activity or gets securely wiped.  Better
> yet, an encrypted laptop where access to the sourcecode is limited to 5
> minutes and then you must FOB authenticate back into it.  After 30 minutes
> of activity and no FOB re-entry you must call back to Microsoft for a new
> software FOB.  After one hour of activity and no FOB authentication the
> whole laptop becomes irreversibly encrypted and must be sent back to
> Microsoft to be re-built.
> 
>    Ok maybe that's TOO secure :-)
--snip--

Michael