Re: Proposal for uri for gnupg messages

--===============1212767902==
Content-Type: multipart/signed;
  boundary="nextPart4214657.G2jQ8pufEe";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart4214657.G2jQ8pufEe
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

On Thursday 21 May 2015 at 14:45:49, mofo syne wrote:
> Is there a standard way to encode gpg keys or messages as a uri ? If
> not, here is a proposal for one.
[..]=20

a better place for this email was gnupg-devel oder gnupg-users
where you did send it.

@all, I think for lack of traffic (last post July 2012) we should remove th=
is=20
mailinglist. And redirect traffic to gnupg-devel@.

Best,
Bernhard


=2D-=20
www.intevation.de/~bernhard (CEO)    www.fsfe.org (Founding GA Member)
Intevation GmbH, Osnabr=FCck, Germany; Amtsgericht Osnabr=FCck, HRB 18998
Owned and run by Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

--nextPart4214657.G2jQ8pufEe
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAABCAAGBQJV5AzAAAoJEDxD9Mjv9dQqxaEH/2S7Avgu6+lKTJAZxgSxq3Mm
B6AMdfpwj1dCH3f2LtAun4zbCTLKUYfarpDBQnGre6Pag/ZSKKPx2U3WMdwRyqt7
NxzJjZCPqM+rzqq5u0YLJMAK3Fun0yxx23B5dJfEgMjsq5L1+9uzw+waWYNEB876
BYCula7A637370+vk+tw372TAf4ebso23VszUCzDBshLxVrVoHid05BtXSmBnC5B
3rxCNHYbQ6CFiAdOMZL4JBgYU8GUf6sWSfV1vtmE9ycRVXSeEtOZMXGiJGNTxCj8
a2hTPigBIw+aYjqqgB4tNx3bdD0bnkO6QdgFz2Q8/FHYzYKS6sy74Sx+zKBpq0E=
=uRb0
-----END PGP SIGNATURE-----

--nextPart4214657.G2jQ8pufEe--


--===============1212767902==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gpa-dev mailing list
[email protected]
http://lists.gnupg.org/mailman/listinfo/gpa-dev

--===============1212767902==--