mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Landley <landley@trommello.org>
To: jw schultz <jw@pegasys.ws>, linux-kernel@vger.kernel.org
Subject: Re: Why are exe, cwd, and root priviledged bits of information?
Date: Fri, 8 Nov 2002 06:28:24 +0000	[thread overview]
Message-ID: <200211080628.24210.landley@trommello.org> (raw)
In-Reply-To: <20021108015533.GC2249@pegasys.ws>

On Friday 08 November 2002 01:55, jw schultz wrote:

> I painted with too broad a brush.  I apologize.
>
> I'm afraid i'll never consider shared secrets to be secure.

Don't use SSH then, or any SSL derivative.  They only use public key 
cryptography at the start of the session, primarily to exchange a pair of 
symmetric keys, which are then used to encrypt the bulk data transmitted 
during the rest of the session.

Public key cryptography is computationally expensive.  Symmetric key 
cryptography is quick and easy, and provably breakable only by brute force if 
you know they haven't got the key.

And of course, the data you're transmitting is itself a shared secret, isn't 
it?  At the end of the session, anyway.  That's the whole point.

> They may provide privacy but not security.

You can have security without privacy?

How?

Privacy is "necessary but not sufficient" to security.  All cryptography boils 
down to there being something you don't want somebody else to know.

Rob

-- 
http://penguicon.sf.net - Terry Pratchett, Eric Raymond, Pete Abrams, Illiad, 
CmdrTaco, liquid nitrogen ice cream, and caffienated jello.  Well why not?

  reply	other threads:[~2002-11-08  6:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07 15:57 Calin A. Culianu
2002-11-07 16:05 ` Daniel Jacobowitz
2002-11-07 22:16   ` jw schultz
2002-11-07 22:28     ` Daniel Jacobowitz
2002-11-07 22:41       ` Jesse Pollard
2002-11-08  1:55         ` jw schultz
2002-11-08  6:28           ` Rob Landley [this message]
2002-11-07 22:44     ` David Wagner

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=200211080628.24210.landley@trommello.org \
    --to=landley@trommello.org \
    --cc=jw@pegasys.ws \
    --cc=linux-kernel@vger.kernel.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 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®