All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Mei <Eric.Mei@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Security issues
Date: Mon, 11 Aug 2008 13:51:48 -0600	[thread overview]
Message-ID: <48A09854.8010401@sun.com> (raw)
In-Reply-To: <C4C5F044.6C46%peter.braam@sun.com>

Peter Braam wrote:
>>> You do need to sign it and encrypt it - for multiple purposes, to secure the
>>> wire transaction and for storage on the server.
>> Sorry I'm still a little confused. To be exactly clear, do you mean: In
>> the future we'll use NASD-style protocol to secure the bulk data's wire
>> transfer & storage on server; and for now we can simply leave the bulk
>> data unprotected?
> 
> No you need to be able to encrypt it.
> 
> I'm just stating that if you the current solution (which gives privacy using
> GSS between client and OSS iirc) is going to be changed, then please change
> it in the correct way to accommodate re-using checksums and re-using the
> encrypted data for storage.  Doing either of these things twice is
> pointless.
> 
> Probably there should be options not to do so as part of the configuration.

Peter, Thanks for clarifying this! Yes that's what we're thinking.

-- 
Eric

  reply	other threads:[~2008-08-11 19:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 18:12 [Lustre-devel] security: rpc message vs bulk data Eric Mei
2008-08-06  2:32 ` Peter Braam
2008-08-06 16:55   ` Eric Mei
2008-08-06 22:48     ` Peter Braam
2008-08-08 14:25       ` James Hughes
2008-08-08 14:45         ` Peter Braam
2008-08-08 17:03           ` [Lustre-devel] Security issues Eric Barton
2008-08-08 17:12             ` Peter Braam
2008-08-08 17:44               ` Eric Mei
2008-08-09  3:47                 ` Peter Braam
2008-08-11 17:14                   ` Eric Mei
2008-08-11 19:33                     ` Peter Braam
2008-08-11 19:51                       ` Eric Mei [this message]
2008-08-13 18:40                       ` James Hughes
2008-08-13 22:26                         ` Peter Braam
2008-08-11 12:56               ` Vitaly Fertman

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=48A09854.8010401@sun.com \
    --to=eric.mei@sun.com \
    --cc=lustre-devel@lists.lustre.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.