From: steve-simon@ntlworld.nospam.com
To: 9fans@cse.psu.edu
Subject: [9fans] cryptographic signatures & factotum
Date: Thu, 11 Mar 2004 23:03:01 +0000 [thread overview]
Message-ID: <559b5ec89e2cfd991a8152e0ceddc88c@snellwilcox.com> (raw)
Hi,
I want to reinvent a wheel.
I want to be able to send an email from home to work
which will cause my work machine to cpu(1) back to me.
To prevent mistakes and nasty people this should be
cryptographicially signed, PGP already does this, but
I don't fancy implementing or porting PGP.
I was thinking of just an email with 2 attachements
one being the command to execute, the other being an
SHA1 hash of this command followed by a shared secret.
The neatest way to check the has would be to pass the hash
of the command to factotum and let it hash the secret and
reply yea or nay.
I could write a seperate program and use proto=pass
to query factotum but why make it release secrets it needn't?
Anyone see any flaws?
Anyone know of facilities in factotum that do this already?
Other (relevant :-) thoughts?
-Steve
next reply other threads:[~2004-03-11 23:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 23:03 steve-simon [this message]
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
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=559b5ec89e2cfd991a8152e0ceddc88c@snellwilcox.com \
--to=steve-simon@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).