mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Satyam Sharma <satyam@infradead.org>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NFS4 authentification / fsuid
Date: Wed, 19 Sep 2007 12:38:58 -0400	[thread overview]
Message-ID: <31390.1190219938@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 19 Sep 2007 01:16:28 EDT." <A5318C25-7864-453A-B09A-00232D9EAF2A@mac.com>

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

On Wed, 19 Sep 2007 01:16:28 EDT, Kyle Moffett said:

> I am assuming that if the laptop has sufficiently important data on  
> it to warrant the above steps then I am also clueful enough to:
>    (A)  Not carry the laptop around unsecured areas,
>    (B)  Keep a close enough eye on it and be aware that it's gone by  
> the time they get to step 2, OR
>    (C)  Pay somebody to build me a better physical chassis for my laptop

Building a better chassis can be a challenge when the threat model really
*does* include attacks by a well-funded TLA.

http://www.epic.org/crypto/scarfo/murch_aff.pdf

The FBI did an *initial* entry to survey the hardware, and then a total of
*five* other entries before they actually installed it.  Note the technical
and legal requirements required on the KLS (it had to, among other things,
capture PGP passphrases but *not* anything that was typed online).

>                                       Besides, if some government  
> wanted the data on your laptop that bad they'd just pick you up in  
> the middle of the night and torture your password out of you.

See above.  Though I *will* note that several years ago, a Department
of Justice filing regarding the use of wiretaps and similar tools reported
that in every single case that the FBI encountered encryption, it in fact
didn't stop the FBI from getting the info it was looking for.  Presumably,
they either used Scarfo-type devices, or they rolled somebody for the key.

They never *did* break Anthony Pellicano's PGP key, as far as I know....

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2007-09-19 16:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 14:12 Jan Engelhardt
2007-08-30 14:29 ` Trond Myklebust
2007-08-30 14:32   ` Trond Myklebust
2007-08-30 14:42     ` Jan Engelhardt
2007-08-30 15:04       ` Trond Myklebust
2007-08-30 21:44         ` J. Bruce Fields
2007-09-06  8:14           ` Satyam Sharma
2007-09-06  8:29             ` Satyam Sharma
2007-09-06 15:11               ` J. Bruce Fields
2007-09-06 23:21                 ` Trond Myklebust
2007-09-06 23:32                   ` Trond Myklebust
2007-09-07 15:34                     ` J. Bruce Fields
2007-09-18 23:27                       ` Satyam Sharma
2007-09-18 23:12                 ` Satyam Sharma
2007-09-06 15:06             ` J. Bruce Fields
2007-09-06 23:30               ` Kyle Moffett
2007-09-06 23:35                 ` Trond Myklebust
2007-09-07  0:56                   ` Kyle Moffett
2007-09-07  5:14                     ` Trond Myklebust
2007-09-07  5:47                       ` Kyle Moffett
2007-09-07  6:37                         ` Bernd Eckenfels
2007-09-18 23:48                         ` Satyam Sharma
2007-09-18 23:44                     ` Satyam Sharma
2007-09-19  5:16                       ` Kyle Moffett
2007-09-19 12:16                         ` Satyam Sharma
2007-09-19 13:49                           ` Kyle Moffett
2007-09-19 14:12                             ` Satyam Sharma
2007-09-19 15:01                               ` J. Bruce Fields
2007-09-20  7:03                                 ` Satyam Sharma
2007-09-19 16:38                         ` Valdis.Kletnieks [this message]
2007-09-20  7:15                           ` Satyam Sharma
2007-08-30 15:12       ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=31390.1190219938@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=bfields@fieldses.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=satyam@infradead.org \
    --cc=trond.myklebust@fys.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®