96 lines
3.3 KiB
HTML
96 lines
3.3 KiB
HTML
|
<!DOCTYPE html>
|
||
|
<html>
|
||
|
<head>
|
||
|
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
|
||
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||
|
<link rel="stylesheet" type="text/css" href="/css/navbar.css">
|
||
|
<link rel="stylesheet" type="text/css" href="/css/main.css">
|
||
|
<script src="/js/navbar.js"></script>
|
||
|
<title>PGP - About</title>
|
||
|
</head>
|
||
|
<body>
|
||
|
|
||
|
<!-- BEGIN NAVBAR -->
|
||
|
<div class="navbar" id="navbar">
|
||
|
<a class="logo" href="/index.html"><img src="/static-objects/navbar/home.svg" alt="Home" width="26" height="26"></a>
|
||
|
<div class="mobile">
|
||
|
<a href="/index.html">Home</a>
|
||
|
</div>
|
||
|
<div class="dropdown">
|
||
|
<button class="dropbutton">Identity ⤵</button>
|
||
|
<div class="droplist">
|
||
|
<a href="/identity">⤷ Key Downloads</a>
|
||
|
<a href="/identity/about.html">⤷ About PGP</a>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="dropdown">
|
||
|
<button class="dropbutton">FDS ⤵</button>
|
||
|
<div class="droplist">
|
||
|
<a href="/fds">⤷ About FDS</a>
|
||
|
<a href="/fds/ultrasonic">⤷ Ultrasonic</a>
|
||
|
</div>
|
||
|
</div>
|
||
|
<a href="/projects">Projects</a>
|
||
|
<a href="/about.html">About</a>
|
||
|
<i>Fred Boniface</i>
|
||
|
<a href="javascript:void(0);" class="icon" onclick="hamburger()">☰</a>
|
||
|
</div>
|
||
|
<!-- END NAVBAR -->
|
||
|
|
||
|
<h1>About PGP</h1>
|
||
|
<ul title="Quick Links"><br>
|
||
|
<li><a href="#trust">Should I trust your key?</a></li>
|
||
|
<li><a href="#integrity">How do you keep your keys secure?</a></li>
|
||
|
<li><a href="#create">How can I create my own keys?</a></li>
|
||
|
</ul>
|
||
|
|
||
|
<h2 id="trust">How do I know I can trust your key?</h2>
|
||
|
<p> There are a few ways to confirm where an email came from but checking
|
||
|
the sender address isn't a reliable way to check. Signing emails with a
|
||
|
PGP key can be a good way to verify an emails source but it isn't as
|
||
|
simple as receiving a signed email. </p>
|
||
|
|
||
|
<p> Once you have verified that the key used to sign the email belongs to
|
||
|
me, you can trust that any message signed with the key originated from me.
|
||
|
</p>
|
||
|
|
||
|
<p> You can check if the key is mine in several ways. </p>
|
||
|
|
||
|
<ul>
|
||
|
<li>If you trust this website, you can trust the key provided here.</li>
|
||
|
<br>
|
||
|
<li>If you know my contact details, you can confirm the keys fingerprint
|
||
|
with me.</li>
|
||
|
<br>
|
||
|
<li>If you do not know me and still need to verify the key, you could
|
||
|
video call me and verify the fingerprint and some photo ID.</li>
|
||
|
</ul>
|
||
|
|
||
|
<p> Once you've established that you can trust the key you can sign it with
|
||
|
your key. </p>
|
||
|
|
||
|
<p> View my key history and download my current PGP key <a href="index.html">here</a>.
|
||
|
</p>
|
||
|
|
||
|
<h2 id="integrity">
|
||
|
What do you do to keep your key secure?
|
||
|
</h2>
|
||
|
<p>
|
||
|
I'm going to provide instructions, showing how I create and manage my keys and showing how you can do the same
|
||
|
if you wish.
|
||
|
</p>
|
||
|
<h2 id="create">Creation</h2>
|
||
|
<p>
|
||
|
To create your key run the following commands.
|
||
|
<br>
|
||
|
<br>
|
||
|
<code>
|
||
|
gpg --generate-key<br>
|
||
|
</code>
|
||
|
</p>
|
||
|
<br>
|
||
|
<footer>----<br>This website is under contruction and is being written by hand. I'm
|
||
|
focussing on the content first before adding styling.</footer>
|
||
|
</body>
|
||
|
</html>
|