GPG guide: add example keyid with 0xLONG format.

This commit is contained in:
Mikaela Suomalainen 2012-07-31 10:05:59 +03:00
parent 6a3770a4f4
commit 1ec2933434
2 changed files with 6 additions and 0 deletions

View File

@ -114,6 +114,8 @@ encrypt-to KEYID</code></pre>
<p>keyid-format 0xLONG</p> <p>keyid-format 0xLONG</p>
</blockquote> </blockquote>
<p>So keyids are shown in the longest format, including 0x prefix, which marks them as hexadecimanls.</p> <p>So keyids are shown in the longest format, including 0x prefix, which marks them as hexadecimanls.</p>
<p>Example outputs from --list-keys and gpg --fingerprint after setting 0xLONG as keyid format.</p>
<p>After you set 0xLONG as keyid-format, keys appear like 0x4DB53CFE82A46728 instead of 82A46728.</p>
<blockquote> <blockquote>
<p>charset UTF-8</p> <p>charset UTF-8</p>
</blockquote> </blockquote>

View File

@ -176,6 +176,10 @@ So everything what you encrypt is also encrypted to you.
So keyids are shown in the longest format, including 0x prefix, which marks them as hexadecimanls. So keyids are shown in the longest format, including 0x prefix, which marks them as hexadecimanls.
Example outputs from --list-keys and gpg --fingerprint after setting 0xLONG as keyid format.
After you set 0xLONG as keyid-format, keys appear like 0x4DB53CFE82A46728 instead of 82A46728.
> charset UTF-8 > charset UTF-8
So UTF-8 is used as default character set and most of characters can be used. So UTF-8 is used as default character set and most of characters can be used.