From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Status of GPG support?
Date: Mon, 10 Dec 2007 14:13:42 -0800 [thread overview]
Message-ID: <1197324612-sup-4789@south> (raw)
In-Reply-To: <475DB454.5020501@therning.org>
Excerpts from Magnus Therning's message of Mon Dec 10 13:49:08 -0800 2007:
> 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?
Excellent timing on this question. SVN currently has a mocked-up
interface for choosing sign/encrypt/sign+encrypt for each message, and
as of last night I have most of the code necessary for signing outgoing
messages in my local repository. It needs a little polishing but should
be committed soon. (And encrypt/sign+encrypt should be pretty easy after
that.) (Also, this is all gpg-specific at this point.)
I will send an announcement when it's in.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-12-10 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 21:49 Magnus Therning
2007-12-10 22:13 ` William Morgan [this message]
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=1197324612-sup-4789@south \
--to=wmorgan-sup@masanjin.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