https://blog.lazy-evaluation.net/deContents © 2025 <a href="mailto:dzu@member.fsf.org">Detlev Zundel</a> Wed, 10 Dec 2025 16:11:13 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://blog.lazy-evaluation.net/de/posts/gpg-secure-mail.html?pk_campaign=feedDetlev Zundel<div><div class="imageblock" id="org57855a5"> <div id="org5d86394" class="figure"> <p><img src="https://blog.lazy-evaluation.net/de/images/logo-gnupg-light-purple-bg.png" alt="logo-gnupg-light-purple-bg.png" title="GnuPG logo" align="middle" width="200"> </p> </div> </div> <p> As the medium E-Mail has to be considered an open channel, once you want to send sensitive content by e-mail, you should really use a secure encryption method with it. </p> <p> Having setup this with my local machines, this report propably can be interpreted as a short guide on how to get things going. </p> <p> For me the basic requirement was to enable one e-mail account with encryption capabilities and this account is accessed from a desktop system and a mobile (Android) system. </p> <p> So what we need is something like the following: </p> <ol class="org-ol"> <li>Generate secret key</li> <li>Publish public key</li> <li>Verify published key by e-mail</li> <li>Install additional required software</li> <li>Use/Import secret key</li> <li>Import public keys from the web</li> </ol> <p> <a href="https://emailselfdefense.fsf.org/en/">Email Self-Defense</a> </p> <p><a href="https://blog.lazy-evaluation.net/de/posts/gpg-secure-mail.html?pk_campaign=feed">Weiterlesen…</a> (2 min verbleiben zum Lesen)</p></div>https://blog.lazy-evaluation.net/de/posts/gpg-secure-mail.htmlTue, 01 Apr 2025 18:25:39 GMT