thanks Wesley Landaker (Closes: #370566).
git-svn-id: svn://svn.debian.org/pgp-tools/trunk@288
b513b33f-fedd-0310-b452-
c3deb5f4c849
signing-party (0.4.6-3) unstable; urgency=low
* Update my maintainer address.
signing-party (0.4.6-3) unstable; urgency=low
* Update my maintainer address.
+ * gpg-mailkeys: use right content-type for attached key,
+ thanks Wesley Landaker (Closes: #370566).
-- Thijs Kinkhorst <thijs@debian.org> Tue, 4 Jul 2006 15:33:53 +0200
-- Thijs Kinkhorst <thijs@debian.org> Tue, 4 Jul 2006 15:33:53 +0200
User-Agent: gpg-mailkeys/$VERSION
MIME-Version: 1.0
Content-Type: multipart/mixed; micalg=pgp-sha1;
User-Agent: gpg-mailkeys/$VERSION
MIME-Version: 1.0
Content-Type: multipart/mixed; micalg=pgp-sha1;
- protocol="application/pgp-signature"; boundary="$BOUNDARY"
Content-Disposition: inline
Content-Disposition: inline
cat << EOM >> $TEMPFILE
--$BOUNDARY
cat << EOM >> $TEMPFILE
--$BOUNDARY
-Content-Type: text/plain; charset=us-ascii
-Content-Disposition: attachment; filename="$1.sig"
+Content-Type: application/pgp-keys
+Content-Disposition: attachment; filename="$1.asc"
`gpg --armor --export $1`
`gpg --armor --export $1`
sends the owners of the keys listed on the command line a mail each,
containing their public key. After signing, you can use this tool to send
everyone the new signatures they just got.
sends the owners of the keys listed on the command line a mail each,
containing their public key. After signing, you can use this tool to send
everyone the new signatures they just got.
+
+If you're interested in encrypting the signature before it's sent, in order
+to verify that the associated address actually belongs to the key owner,
+you should check out
+.B caff
.SH OPTIONS
None
.SH ENVIRONMENT
.SH OPTIONS
None
.SH ENVIRONMENT