From: "Lluís Batlle" <viriketo@gmail.com>
To: fernanbolando@mailc.net,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] gnupg or pgp for plan9?
Date: Mon, 27 Mar 2006 15:10:00 +0200 [thread overview]
Message-ID: <45219fb00603270510l7167f70eh@mail.gmail.com> (raw)
In-Reply-To: <1d5d51400603270118n7ac6441en71a34f893950f635@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
You can take a look at ccrypt (ccrypt.sf.net) if it's about file encryption,
but I don't know if it wil work on plan9. I've only compiled it with the
called "gnu configure machinery".
2006/3/27, Fernan Bolando <fernanbolando@mailc.net>:
>
> On 3/27/06, Steve Simon <steve@quintile.net> wrote:
> > If you are just looking for file encryption then
> > auth/aescbc will do that for you. A little script
> > would allow you to validate a locally held md5sum
> > digest of the file to inform you of any tampering.
> > Aescbc is not portable outside of plan9 - p9p not
> > withstanding.
> >
> > -Steve
> >
>
> I am trying to get some sort of encyption. Protability between p9, linux
> and
> windows is a bit critical for my application ( I am paranoid ).
>
> I am currently considering blowfish because it's available on most
> machines.
>
> Of course gnupg would be best.
>
> ,Fernan
> --
> Public PGP/GnuPG key (http://www.fernski.com)
> pub 1024D/3576CA71 2006-02-02 Fernan Bolando
> Key fingerprint = FDFE C9A8 FFED C1A5 2F5C EFEB D595 AF1C 3576 CA71
>
[-- Attachment #2: Type: text/html, Size: 1484 bytes --]
next prev parent reply other threads:[~2006-03-27 13:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-03-27 17:26 ` Fernan Bolando
2006-03-28 0:38 ` Anthony Sorace
2006-03-28 13:59 ` Eric Grosse
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-29 1:13 erik quanstrom
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=45219fb00603270510l7167f70eh@mail.gmail.com \
--to=viriketo@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=fernanbolando@mailc.net \
/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).