9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gnupg or pgp for plan9?
Date: Tue, 28 Mar 2006 19:13:26 -0600	[thread overview]
Message-ID: <78568fc3f80d553218d86e389700eb0f@quanstro.net> (raw)

somehow you understood the opposite of what i ment.
the point is that using encrypted/signed s/mime with upas
should be transparent.  i would think the easiest way to do that would
be to do the translation as  close to the edges of the system as possible.
those edges would be upas/fs -- which presents a mail box as a filesystem
and upas/marshal which builds an rfc-2822 message for sending.

i had not thought of using s/mime for general encrypted storage.
mime is not a particularly friendly or easy-to-parse format.
i would think that using, say, blowfish in cbc mode would be
plenty compatable.  mcrypt/mhash (http://(mcrypt|mhash).sourceforge.net/),
for example, could decrypt this on a unix-like machine.
(not that either is svelt.)

what would be the advantage of using s/mime outside of email?

- erik

On Tue Mar 28 09:00:28 EST 2006, anothy@gmail.com wrote:
> Erik Quanstrom wrote:
> // i think a better route would be to build s/mime compatable signatures
> // and encryption into upas/fs and upas/marshal so applications without
> // a need to know would not have to know.
>
> i'm not really sure what you mean by that. certainly we shouldn't
> require the content-producing programs (like, say, 'cat') to know
> anything about encryption, but that idea's already totally foreign to
> plan 9 (cat --enable-encryption-with-aes-cbc?).
>
> having s/mime in upas would be wonderful, but doesn't fully address
> the needs being discussed. i want to be able to store files on disk
> securely, including across platforms. for that, i want a stand-alone
> program (hopefully, one which could then be used in upas).



             reply	other threads:[~2006-03-29  1:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29  1:13 erik quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-28  0:48 erik quanstrom
2006-03-28 14:59 ` Anthony Sorace
2006-03-28 15:23   ` Bruce Ellis
2006-03-28 15:57 ` Gabriel Diaz
2006-03-28 17:29   ` Charles Forsyth
2006-03-28 17:47     ` Gabriel Diaz
2006-03-29  0:27       ` Fernan Bolando
2006-03-29  2:49         ` geoff
2006-03-29  7:29           ` geoff
2006-03-29  2:07     ` Paul Lalonde
2006-03-29  3:17       ` quanstro
2006-03-29  3:56         ` Paul Lalonde
2006-03-29  9:09       ` Taj Khattra
2006-03-29 16:02         ` uriel
2006-03-29 22:03           ` Taj Khattra
2006-03-27  4:30 Fernan Bolando
2006-03-27  6:50 ` geoff
2006-03-27  7:25 ` Steve Simon
2006-03-27  9:18   ` Fernan Bolando
2006-03-27 13:10     ` Lluís Batlle
2006-03-27 17:26       ` Fernan Bolando
2006-03-28  0:38     ` Anthony Sorace
2006-03-28 13:59   ` Eric Grosse

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=78568fc3f80d553218d86e389700eb0f@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).