From: magnus@therning.org (Magnus Therning)
Subject: [sup-talk] Status of GPG support?
Date: Mon, 10 Dec 2007 21:49:08 +0000 [thread overview]
Message-ID: <475DB454.5020501@therning.org> (raw)
I haven't had time to keep up-to-date on sup development, so I'm sorry
if I'm asking something that's obvious to everyone else. A few weeks
ago there was only support for using GPG on received messages (signature
verification and I believe decryption); support for signing and
encrypting was lacking. Has this changed by now, or are there
well-known (external to sup) workarounds?
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus?therning?org Jabber: magnus?therning?gmail?com
http://therning.org/magnus
What if I don't want to obey the laws? Do they throw me in jail with
the other bad monads?
-- Daveman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071210/d6f1a105/attachment.bin
next reply other threads:[~2007-12-10 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 21:49 Magnus Therning [this message]
2007-12-10 22:13 ` William Morgan
2007-12-14 1:01 ` William Morgan
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=475DB454.5020501@therning.org \
--to=magnus@therning.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