From: Satyam Sharma <satyam@infradead.org>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: 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 19:42:20 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.0.999.0709191931010.7697@enigma.security.iitk.ac.in> (raw)
In-Reply-To: <DBAB3583-BB6E-48C8-AFC1-0A705D048843@mac.com>
On Wed, 19 Sep 2007, Kyle Moffett wrote:
>
> > [all sorts of crap about spies in washington needing stronger protection
> > than your average consumer]
>
> [snip]
>
> [...] all the bullcrap about foreign intelligence
Hehe, again, *you* started all the "bullcrap" about foreign "governments"
in the first place :-)
> is just drawing
> focus off of how easy it is to achieve *adequate* physical protection where it
^^^^^^^^
> matters.
Ah, so you're qualifying the discussion with the nice and subjective
"adequate" ... (you're still wrong, of course)
> Of course, this also relies on being able to teach the stupid lusers with the
> laptops not to give their boot password to the "service tech on the phone"
Let's stick on-topic here ... remember "securing a system against attacker
with physical access is fairly simple" ?
[ Took the liberty of removing some irrelevant digressions -- didn't see
any solid security scheme that fulfils/justifies your earlier claim over
there. ]
> > > If your system equates end-user with attacker
> >
> > "If"? Was there ever any doubt?
> >
> > Heh, did you even read the thread you just replied to?
>
> Yes I did [...]
No, you didn't -- it was obvious from your reply :-)
> and I wanted to make it *really* clear that with average hardware
> you can properly protect against virtually all of the *common* attack vectors.
^^^^^^
But what gave you the impression we're interested in discussing "common"
or "adequate enough" attack vectors here?
See, if you have something useful/new to contribute to the discussion,
that we don't already know, then please don't hold back and feel free to
do so ...
Satyam
next prev parent reply other threads:[~2007-09-19 14:09 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 [this message]
2007-09-19 15:01 ` J. Bruce Fields
2007-09-20 7:03 ` Satyam Sharma
2007-09-19 16:38 ` Valdis.Kletnieks
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=alpine.LFD.0.999.0709191931010.7697@enigma.security.iitk.ac.in \
--to=satyam@infradead.org \
--cc=bfields@fieldses.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--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®