Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Proper wording for a document which will be signed - WoT related question
1 view
Skip to first unread message
Stefan Claas
Nov 3, 2018, 7:46:01 AM11/3/18
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi all,
I am no native English speaker and have a question for you.
My current GnuPG public key is signed by Governikus, a german
PGP CA, run on behalf of Germany's BSI.
Because i strongly assume that people outside of Germany don't know
what Governikus is, nor do they know the signing procedure and would
therefore probably not trust this sig3 on my pub key i thought to
prepare a little .pdf document, signed with my qualified and eIDAS
conform X.509 certificate, so that people, at least in Europe, could be
assured that the .pdf and my pub key, belongs to *me* The document
will then be uploaded to my keybase account.
O.k. so far so good... How would you formulate and name such a
little .pdf document, so that it is accepted by the PGP community?
I will also timestamp this document, as an additional protection layer
and may consider to GnuPG detach sign it as well, with my current
GnuPG key.
Any help would be greatly appreciated!
Regards
Stefan
- --
https://www.behance.net/futagoza
https://keybase.io/stefan_claas
-----BEGIN PGP SIGNATURE-----
iHUEARMIAB0WIQQO9e6Txc/tQ7dAcgrcCkx+JZpcNwUCW92KeAAKCRDcCkx+JZpc
N9WPAP9pv0OA5ucH7Uj2RF5PEG6x9aZCBH6e+B65TcAM2wEq/QD/UqE+2Hn33a4w
oTuCVk9KYEpo8pPtPxCy1KDEeCPL8Ew=
=fo7b
-----END PGP SIGNATURE-----
Hash: SHA256
Hi all,
I am no native English speaker and have a question for you.
My current GnuPG public key is signed by Governikus, a german
PGP CA, run on behalf of Germany's BSI.
Because i strongly assume that people outside of Germany don't know
what Governikus is, nor do they know the signing procedure and would
therefore probably not trust this sig3 on my pub key i thought to
prepare a little .pdf document, signed with my qualified and eIDAS
conform X.509 certificate, so that people, at least in Europe, could be
assured that the .pdf and my pub key, belongs to *me* The document
will then be uploaded to my keybase account.
O.k. so far so good... How would you formulate and name such a
little .pdf document, so that it is accepted by the PGP community?
I will also timestamp this document, as an additional protection layer
and may consider to GnuPG detach sign it as well, with my current
GnuPG key.
Any help would be greatly appreciated!
Regards
Stefan
- --
https://www.behance.net/futagoza
https://keybase.io/stefan_claas
-----BEGIN PGP SIGNATURE-----
iHUEARMIAB0WIQQO9e6Txc/tQ7dAcgrcCkx+JZpcNwUCW92KeAAKCRDcCkx+JZpc
N9WPAP9pv0OA5ucH7Uj2RF5PEG6x9aZCBH6e+B65TcAM2wEq/QD/UqE+2Hn33a4w
oTuCVk9KYEpo8pPtPxCy1KDEeCPL8Ew=
=fo7b
-----END PGP SIGNATURE-----
Stefan Claas
Nov 5, 2018, 11:36:25 AM11/5/18
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Sat, 3 Nov 2018 12:45:59 +0100, Stefan Claas wrote:
> O.k. so far so good... How would you formulate and name such a
> little .pdf document, so that it is accepted by the PGP community?
>
> I will also timestamp this document, as an additional protection layer
> and may consider to GnuPG detach sign it as well, with my current
> GnuPG key.
>
> Any help would be greatly appreciated!
Here is a little example, i did, for a revocation statement:
> O.k. so far so good... How would you formulate and name such a
> little .pdf document, so that it is accepted by the PGP community?
>
> I will also timestamp this document, as an additional protection layer
> and may consider to GnuPG detach sign it as well, with my current
> GnuPG key.
>
> Any help would be greatly appreciated!
<https://keybase.pub/stefan_claas/Public_Key_Revocation_Statement/>
The .pdf is signed with with qualified electronic signature (QES) and
time stamped and additionally detached signed with my GnuPG key.
The last file is then the .ots time stamp file, from opentimestamps.org
Regards
Stefan
- --
https://www.behance.net/futagoza
https://keybase.io/stefan_claas
-----BEGIN PGP SIGNATURE-----
N1NVAQC5mUXa8xcMxVCqGwFEL5ugWXs0W/EisxLwX7O7s6v+9AD/V49TD9CuqqeC
y2xUA0FvzwDJcW2mm01+UULToGNaPEU=
=+IK3
-----END PGP SIGNATURE-----
0 new messages