key_confusion

[mizett at elude.in]

*******************************************************
hi all,

i do not clearly understand the difference between .asc , .gpg , .sign ,
.sig , cert and do not know the official_usage & conventions.
i made my own research before but ... unsuccessfully.

i built my curve keys using these commands_options (added a sign subkey
and gnupg auto-signed it), armor my public one then export it as file :
$ gpg --expert --full-gen-key
> long_upperlowernumberspecial
$ gpg --quick-add-key fpr ed25519 sign
> S
$ gpg --list-sigs
> 25519
$ gpg --output public.key --armor --export fpr
> public.key
$ gpg --armor --export you at example.com
> public.asc

key is also a certificate if i understood well what i read.
it looks like :
	- gnupg uses public.key for being exported on a server_internal operation.
	- gnupg uses public.asc for being exported on an
e-mail/mailing-list_external
operation.
	- gnupg uses cert for server/vpn = multiple keys
	- key = gpg = cert ?
	- cert = sign = sig = every keys (subkeys included)
	- cert = gpg = soft/file encrypted
	- cert = asc = sign = sig = gpg = gpg2 ?
--- is it not the same ?

i do not clearly understand the difference between .cert .asc , .gpg ,
.sign , .sig and do not know the official_usage & conventions.
- could i rename the public.* as .sign and what is the difference using
.sig ?
- could i export the public.key on the hkps-server or must i use the
public.asc ?
- could i rename public.asc in public.gpg2 ?
... and the same questions come in my mind about the *SUMS files.
... and the same confusion about user-id , fpr , e-mail :
--- is it not the same ?

if there are strict conventions/rules it should be a better idea to
clarify & compartment the usage no ?
have you a link where all these embarrassing questions are clearly
explained ?

thx.





OFF-TOPIC : could gnupg add a special option in his settings/option :
quantum resistant ?
I mean an embedded version of codecrypt.
*******************************************************
-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEWaYFNxYJKwYBBAHaRw8BAQdAForZDwa2XHzyPK0h9HaX48zG334uB//GIzrk
5uX5pRK0GG1pemV0dCA8bWl6ZXR0QGVsdWRlLmluPoiWBBMWCAA+FiEEkHF8qdYY
xDml5OIMuksBqrkkVUIFAlmmBTcCGwMFCQAJOoAFCwkIBwIGFQgJCgsCBBYCAwEC
HgECF4AACgkQuksBqrkkVUL1MAEAxDli/OwIkKM/V+PI30WZMooZa8i7Pb60NBEP
/dafH4gBAKbJDetYDFV72Re7AyMOZ+WoncRVr+HyLg+9QWdeoRUMuDgEWaYFNxIK
KwYBBAGXVQEFAQEHQCucJY+zC9uNI6EBzZnxmAc7yMkSk5RWyY6qQRPm3/omAwEI
B4h+BBgWCAAmFiEEkHF8qdYYxDml5OIMuksBqrkkVUIFAlmmBTcCGwwFCQAJOoAA
CgkQuksBqrkkVUJPBQEA3u8dDnu7qyAsXQkiGsVS1A4q3h6hXePQ5pN7E6QYvjIB
AOrkfJ3/bhMO3Wu/BbQEwuIkwENyGoCwpTDOA9/hPW0I
=oqqh
-----END PGP PUBLIC KEY BLOCK-----
********************************************************