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: rpc message vs bulk data
Date: Tue, 05 Aug 2008 12:12:49 -0600	[thread overview]
Message-ID: <48989821.3090904@sun.com> (raw)

Hi,

Currently we use different security transformation: on RPC message we 
use gssapi/kerberos; on bulk data we use separate hash + cipher 
mechanism. And to some extend the 2 parts can be configured 
independently. For example, you can use "krb5p" on RPC message while use 
some light-weight hash/cipher on bulk data for performance or whatever 
reasons.

Now we're thinking about using gssapi for both RPC and bulk data. But 
this way we won't be able to configure them separately. What we're not 
sure is: is it necessary to be able to set different security level for 
RPC message and bulk data?

Thanks!
-- 
Eric

             reply	other threads:[~2008-08-05 18:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 18:12 Eric Mei [this message]
2008-08-06  2:32 ` [Lustre-devel] security: rpc message vs bulk data 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
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=48989821.3090904@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.