9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <plan9fans@ntlworld.nospam.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] cryptographic signatures & factotum
Date: Fri, 12 Mar 2004 09:23:50 +0000	[thread overview]
Message-ID: <004b01c40813$bb9261b0$df756f51@ntlworld.com> (raw)
In-Reply-To: <76cc93f6db46e7ad7bd84bceb250ba14@collyer.net>

Hi,

Thanks to all who replied.
I realised I didn't say why I want to do this.

At work my plan9 system is very carefully screened behind a
firewall. The only way I can make somthing happen on it is
either cron or emai (via pipeto).

My idea was to send just a plaintext email that contains two attachements.
One being an rc script and the other an authenticating
signature for that command. I think this is secure enough as the
signature (hash) would need a shared secret to be validated.

The idea of hashing a sequence count is interesting but in the context
of email as a transport (and our unreliable pop3 server) I am wary of
going down this route.

The real questions are:
Should I attempt to add a non-standard (not PGP) signature verification
algorithm to factotum? Or, should I just do a quick bodge and not
worry, because no-one else would ever want such a thing?

Another question:

At home my plan9 system is straight onto broadband but I believe it's
secure - it only listens on the cpu and exportfs, am I being naieve (again
:-), tell me I don't need to buy a firewall...

-Steve




  reply	other threads:[~2004-03-12  9:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 23:03 steve-simon
2004-03-11 23:41 ` andrey mirtchovski
2004-03-11 23:57 ` 9nut
2004-03-12  0:03   ` George Michaelson
2004-03-12  0:09     ` boyd, rounin
2004-03-12  0:30       ` George Michaelson
2004-03-12  9:07         ` Bruce Ellis
2004-03-12 11:49           ` boyd, rounin
2004-03-12 12:14             ` boyd, rounin
2004-03-12  1:18     ` bs
2004-03-12  0:27 ` matt
2004-03-12  0:49 ` a
2004-03-12 19:52   ` rog
2004-03-12  1:02 ` Geoff Collyer
2004-03-12  9:23   ` Steve Simon [this message]
2004-03-12 13:03     ` David Presotto
2004-03-12 13:14       ` boyd, rounin
2004-03-12 13:35         ` David Presotto
2004-03-12 14:02           ` boyd, rounin
2004-03-12 16:23             ` John Kodis
2004-03-12 19:08               ` boyd, rounin
2004-03-14  3:39     ` Nick Jamieson
2004-03-14  3:53       ` boyd, rounin
2004-03-14  5:31         ` Nick Jamieson
2004-03-14  5:37           ` boyd, rounin

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='004b01c40813$bb9261b0$df756f51@ntlworld.com' \
    --to=plan9fans@ntlworld.nospam.com \
    --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).