Mikaela/mikaela.github.io
1
0
Fork 0
mirror of https://github.com/mikaela/mikaela.github.io/ synced 2025-02-23 17:00:40 +01:00
Code Issues Projects Releases Wiki Activity

Merge branch 'master' of github.com:Mkaysi/mkaysi.github.com

Browse Source
This commit is contained in:
Mikaela Suomalainen 2012-08-02 11:08:11 +03:00
commit 37a6ad5aeb
2 changed files with 46 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
articles/guides/GPG/GPG.html
View File

@ -73,6 +73,16 @@ sub 4096R/A4271AC5 2012-03-27</code></pre>
<blockquote> <blockquote>
<p>y</p> <p>y</p>
</blockquote> </blockquote>
<h6 id="setting-preferred-keyserver-of-the-key.">Setting preferred keyserver of the key.</h6>
<p>Preferred keyserver is where the key is refreshed when someone runs &quot;gpg2 --refresh-keys&quot;.</p>
<p>To set it run</p>
<blockquote>
<p>gpg2 --edit-key KEYID</p>
</blockquote>
<blockquote>
<p>keyserver</p>
</blockquote>
<p>and enter the keyserver address, for example hkp://pool.sks-keyservers.net (I recommend this keyserver).</p>
<h4 id="step-1-importing-old-key">Step 1: Importing old key</h4> <h4 id="step-1-importing-old-key">Step 1: Importing old key</h4>
<p>You can import your old private key same way as you import public keys. This means:</p> <p>You can import your old private key same way as you import public keys. This means:</p>
<blockquote> <blockquote>
@ -92,7 +102,7 @@ sub 4096R/A4271AC5 2012-03-27</code></pre>
<h3 id="step-3-configuring-gpg2">Step 3: Configuring gpg(2)</h3> <h3 id="step-3-configuring-gpg2">Step 3: Configuring gpg(2)</h3>
<p>The configuring of gpg happens in gpg configuration directory. In Linux and Mac this is ~/.gnupg/gpg.conf.</p> <p>The configuring of gpg happens in gpg configuration directory. In Linux and Mac this is ~/.gnupg/gpg.conf.</p>
<p>I recommend you to add following lines to it. I'll try to explain them with my best ability.</p> <p>I recommend you to add following lines to it. I'll try to explain them with my best ability.</p>
<p><code># Options for GnuPG # Copyright 1998, 1999, 2000, 2001, 2002, 2003, # 2010 Free Software Foundation, Inc. # # This file is free software; as a special exception the author gives # unlimited permission to copy and/or distribute it, with or without # modifications, as long as this notice is preserved. # # This file is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY, to the extent permitted by law; without even the # implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</code> License information so I won't break license of the default config file, which I have appended.</p> <p><code># Options for GnuPG # Copyright 1998, 1999, 2000, 2001, 2002, 2003, # 2012— Mika Suomalainen (Mkaysi) https://raw.github.com/Mkaysi/shell-things/master/gnupg/gpg.conf # 2010 Free Software Foundation, Inc. # # This file is free software; as a special exception the author gives # unlimited permission to copy and/or distribute it, with or without # modifications, as long as this notice is preserved. # # This file is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY, to the extent permitted by law; without even the # implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</code> License information so I won't break license of the default config file, which I have appended.</p>
<blockquote> <blockquote>
<p>default-key KEYID</p> <p>default-key KEYID</p>
</blockquote> </blockquote>
@ -101,34 +111,36 @@ sub 4096R/A4271AC5 2012-03-27</code></pre>
encrypt-to KEYID</code></pre> encrypt-to KEYID</code></pre>
<p>So everything what you encrypt is also encrypted to you.</p> <p>So everything what you encrypt is also encrypted to you.</p>
<blockquote> <blockquote>
<p>keyid-format 0xLONG</p>
</blockquote>
<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>
<p>charset UTF-8</p> <p>charset UTF-8</p>
</blockquote> </blockquote>
<p>So UTF-8 is used as default character set and most of characters can be used.</p> <p>So UTF-8 is used as default character set and most of characters can be used.</p>
<pre><code>keyserver hkp://pool.sks-keyservers.net <pre><code>keyserver hkp://pool.sks-keyservers.net
keyserver-options auto-key-retrieve no-include-revoked verbose</code></pre> keyserver-options auto-key-retrieve no-include-revoked verbose import-clean</code></pre>
<p>So default keyserver is specified and unknown keys are always received when something what requires missing key is procressses and revoked keys aren't included in search results and verbose output is used.</p> <p>So default keyserver is specified and unknown keys are always received when something what requires missing key is procressses and revoked keys aren't included in search results and verbose output is used and signatures by unknown keys are automatically removed.</p>
<p>By the way, you can find my gpg.conf <a href="https://raw.github.com/Mkaysi/shell-things/master/gnupg/gpg.conf">here</a>.</p> <p>By the way, you can find my gpg.conf <a href="https://raw.github.com/Mkaysi/shell-things/master/gnupg/gpg.conf">here</a>.</p>
<h4 id="group-lines">Group lines</h4> <h4 id="group-lines">Group lines</h4>
<p>Group lines are a way to write email to one recepient and have it encrypted to multiple keys automatically.</p> <p>Group lines are a way to write email to one recepient and have it encrypted to multiple keys automatically.</p>
<p>Example group line:</p> <p>Example group line:</p>
<blockquote>
<p>group <script type="text/javascript"> <p>group <script type="text/javascript">
<!-- <!--
h='&#x67;&#x6f;&#x6f;&#x67;&#108;&#x65;&#x67;&#114;&#x6f;&#x75;&#112;&#x73;&#46;&#x63;&#x6f;&#x6d;';a='&#64;';n='&#116;&#x6f;&#x75;&#x63;&#104;&#108;&#x61;&#x79;&#x2d;&#x73;&#x65;&#114;&#118;&#x65;&#114;';e=n+a+h; h='&#x67;&#x6f;&#x6f;&#x67;&#108;&#x65;&#x67;&#114;&#x6f;&#x75;&#112;&#x73;&#46;&#x63;&#x6f;&#x6d;';a='&#64;';n='&#116;&#x6f;&#x75;&#x63;&#104;&#108;&#x61;&#x79;&#x2d;&#x73;&#x65;&#114;&#118;&#x65;&#114;';e=n+a+h;
document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'">'+'<code>'+e+'</code>'+'<\/'+'a'+'>'); document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'">'+'<code>'+e+'</code>'+'<\/'+'a'+'>');
// --> // -->
</script><noscript>&#116;&#x6f;&#x75;&#x63;&#104;&#108;&#x61;&#x79;&#x2d;&#x73;&#x65;&#114;&#118;&#x65;&#114;&#32;&#x61;&#116;&#32;&#x67;&#x6f;&#x6f;&#x67;&#108;&#x65;&#x67;&#114;&#x6f;&#x75;&#112;&#x73;&#32;&#100;&#x6f;&#116;&#32;&#x63;&#x6f;&#x6d;</noscript>=82A46728 8449A12B 666CC0DD 4EC00206</p> </script><noscript>&#116;&#x6f;&#x75;&#x63;&#104;&#108;&#x61;&#x79;&#x2d;&#x73;&#x65;&#114;&#118;&#x65;&#114;&#32;&#x61;&#116;&#32;&#x67;&#x6f;&#x6f;&#x67;&#108;&#x65;&#x67;&#114;&#x6f;&#x75;&#112;&#x73;&#32;&#100;&#x6f;&#116;&#32;&#x63;&#x6f;&#x6d;</noscript>=0x4DB53CFE82A46728 0x0BD622288449A12B 0x729DF464666CC0DD 0xCACC5B094EC00206</p>
</blockquote>
<p>With that line, when recepient is touchlay-server@googlegroups.com, then emails are encrypted to those 4 keys.</p> <p>With that line, when recepient is touchlay-server@googlegroups.com, then emails are encrypted to those 4 keys.</p>
<p>NOTE: I think that group lines require email addresses to be in format</p> <p>NOTE: I think that group lines require email addresses to be in format</p>
<blockquote> <p>NOTE: KEYIDs in group line should be in format 0xLONG. If you don't use that format by default, use &quot;gpg2 --keyid-format 0xLONG --list-keys&quot;. &gt; <script type="text/javascript">
<p><script type="text/javascript">
<!-- <!--
h='&#116;&#104;&#x69;&#46;&#110;&#x67;';a='&#64;';n='&#x73;&#x6f;&#x6d;&#x65;';e=n+a+h; h='&#116;&#104;&#x69;&#46;&#110;&#x67;';a='&#64;';n='&#x73;&#x6f;&#x6d;&#x65;';e=n+a+h;
document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'">'+'<code>'+e+'</code>'+'<\/'+'a'+'>'); document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'">'+'<code>'+e+'</code>'+'<\/'+'a'+'>');
// --> // -->
</script><noscript>&#x73;&#x6f;&#x6d;&#x65;&#32;&#x61;&#116;&#32;&#116;&#104;&#x69;&#32;&#100;&#x6f;&#116;&#32;&#110;&#x67;</noscript></p> </script><noscript>&#x73;&#x6f;&#x6d;&#x65;&#32;&#x61;&#116;&#32;&#116;&#104;&#x69;&#32;&#100;&#x6f;&#116;&#32;&#110;&#x67;</noscript></p>
</blockquote>
<p>See also my <a href="Enigmail.html">Enigmail</a> instructions about group lines.</p> <p>See also my <a href="Enigmail.html">Enigmail</a> instructions about group lines.</p>
<h3 id="comments">Comments</h3> <h3 id="comments">Comments</h3>
<p>GPG can automatically add comments to signed and encrypted content. They are usually hidden by email clients, which support GPG.</p> <p>GPG can automatically add comments to signed and encrypted content. They are usually hidden by email clients, which support GPG.</p>

28
articles/guides/GPG/GPG.html.md
View File

@ -107,6 +107,18 @@ and confirm to save changes with
> y > y
###### Setting preferred keyserver of the key.
Preferred keyserver is where the key is refreshed when someone runs "gpg2 --refresh-keys".
To set it run
> gpg2 --edit-key KEYID
> keyserver
and enter the keyserver address, for example hkp://pool.sks-keyservers.net (I recommend this keyserver).
#### Step 1: Importing old key #### Step 1: Importing old key
You can import your old private key same way as you import public keys. This means: You can import your old private key same way as you import public keys. This means:
@ -136,6 +148,7 @@ I recommend you to add following lines to it. I'll try to explain them with my b
``` ```
# Options for GnuPG # Options for GnuPG
# Copyright 1998, 1999, 2000, 2001, 2002, 2003, # Copyright 1998, 1999, 2000, 2001, 2002, 2003,
# 2012— Mika Suomalainen (Mkaysi) https://raw.github.com/Mkaysi/shell-things/master/gnupg/gpg.conf
# 2010 Free Software Foundation, Inc. # 2010 Free Software Foundation, Inc.
# #
# This file is free software; as a special exception the author gives # This file is free software; as a special exception the author gives
@ -159,16 +172,24 @@ encrypt-to KEYID
So everything what you encrypt is also encrypted to you. So everything what you encrypt is also encrypted to you.
> keyid-format 0xLONG
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.
``` ```
keyserver hkp://pool.sks-keyservers.net keyserver hkp://pool.sks-keyservers.net
keyserver-options auto-key-retrieve no-include-revoked verbose keyserver-options auto-key-retrieve no-include-revoked verbose import-clean
``` ```
So default keyserver is specified and unknown keys are always received when something what requires missing key is procressses and revoked keys aren't included in search results and verbose output is used. So default keyserver is specified and unknown keys are always received when something what requires missing key is procressses and revoked keys aren't included in search results and verbose output is used and signatures by unknown keys are automatically removed.
By the way, you can find my gpg.conf [here]. By the way, you can find my gpg.conf [here].
@ -180,12 +201,13 @@ Group lines are a way to write email to one recepient and have it encrypted to m
Example group line: Example group line:
> group <touchlay-server@googlegroups.com>=82A46728 8449A12B 666CC0DD 4EC00206 group <touchlay-server@googlegroups.com>=0x4DB53CFE82A46728 0x0BD622288449A12B 0x729DF464666CC0DD 0xCACC5B094EC00206
With that line, when recepient is touchlay-server@googlegroups.com, then emails are encrypted to those 4 keys. With that line, when recepient is touchlay-server@googlegroups.com, then emails are encrypted to those 4 keys.
NOTE: I think that group lines require email addresses to be in format NOTE: I think that group lines require email addresses to be in format
NOTE: KEYIDs in group line should be in format 0xLONG. If you don't use that format by default, use "gpg2 --keyid-format 0xLONG --list-keys".
> <some@thi.ng> > <some@thi.ng>
See also my [Enigmail] instructions about group lines. See also my [Enigmail] instructions about group lines.