Re: [Full-Disclosure] InfoSec sleuths beware ...
From: michael williamson (michael_at_puffin.tamucc.edu)
Date: 02/19/04
- Previous message: Paul Schmehl: "Re: [Full-Disclosure] Re: Second critical mremap() bug found in all Linux kernels"
- In reply to: Exibar: "Re: [Full-Disclosure] InfoSec sleuths beware ..."
- Next in thread: Gregory A. Gilliss: "Re: [Full-Disclosure] InfoSec sleuths beware ..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: full-disclosure@lists.netsys.com Date: Thu, 19 Feb 2004 15:22:12 -0600
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
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
- Previous message: Paul Schmehl: "Re: [Full-Disclosure] Re: Second critical mremap() bug found in all Linux kernels"
- In reply to: Exibar: "Re: [Full-Disclosure] InfoSec sleuths beware ..."
- Next in thread: Gregory A. Gilliss: "Re: [Full-Disclosure] InfoSec sleuths beware ..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
