You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
49 lines
3.1 KiB
49 lines
3.1 KiB
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<title>Alex's crypto keys</title>
|
|
</head>
|
|
<body>
|
|
<p>This page hosts up-to-date information on my crypto keys.</p>
|
|
|
|
<h2>OpenPGP</h2>
|
|
<p>I use PGP-signed emails. All my keys expire 2 years after creation, though I may publish the revocation certificate before the expiration date. I recommend checking periodically with the Ubuntu keyserver (keyserver.ubuntu.com) and the key's page at the PGP archive in case I revoked the key.</p>
|
|
<p>See also the <a href="pgp-archive/index.html">PGP key archive</a></p>
|
|
<table>
|
|
<tr>
|
|
<th>KeyID</th>
|
|
<th>Created</th>
|
|
<th>Expiration date</th>
|
|
<th>Expired/revoked</th>
|
|
</tr>
|
|
<tr>
|
|
<td><a href="pgp-archive/11ADE4393600C1BDFFCBC0A598DE15942B08CA00/key.pub">11ADE4393600C1BDFFCBC0A598DE15942B08CA00</a></td>
|
|
<td>2023-01-13</td>
|
|
<td>2025-01-12</td>
|
|
<td>No</td>
|
|
</tr>
|
|
</table>
|
|
<p>The latest key is also available via <a href="https://wiki.gnupg.org/WKD">Web Key directory</a>.</p>
|
|
<h2>Git</h2>
|
|
<p>I use SSH keys at git. This key is only used at git. I'm not much of a fan of OpenPGP, I actually prefer the simpler SSH keys. You can also go to <a href="https://codeberg.org/YellowComet.keys">YellowComet.keys at Codeberg</a> and <a href="https://github.com/redbluegreenhat.keys">redbluegreenhat.keys at GitHub</a> to check my latest key.</p>
|
|
<table>
|
|
<tr>
|
|
<th>Public key</th>
|
|
<th>Fingerprint</th>
|
|
<th>Still used</th>
|
|
</tr>
|
|
<tr>
|
|
<td>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAINbnd8D+WQJVrNep2/UWRwErwbQxyGhQgKRvvnD7qWkX</td>
|
|
<td>SHA256:R9JgcFwobmbm954dT287awvY7wUsd8OMi4asFJwkmMY</td>
|
|
<td>Yes</td>
|
|
</tr>
|
|
</table>
|
|
<h2>How to know that a new OpenPGP/SSH key is from me</h2>
|
|
<p>This site is hosted on a <a href="https://codeberg.org/YellowComet/pages">Git repository at Codeberg</a>. As I sign all my commits there, using the SSH key indicated above, you can use that signature as a way to know that a new key is from me. Look for the "Signed by: YellowComet" line at the commit on the web interface, or clone the repository, put my SSH key in your <a href="https://man.openbsd.org/ssh-keygen.1#ALLOWED_SIGNERS">allowed_signers</a> file, and use the Git CLI to verify the signature on your machine.</p>
|
|
<p>This is straightforward enough for OpenPGP keys. In the case of SSH keys, I'll first generate it, make a commit including the new public key at this website's Git repository using the old key, and only then sign new commits using my new key.</p>
|
|
<p>Of course, to be 100% sure it is me (as this scheme falls apart if my private SSH key is compromised), you should verify these keys with me in person.</p>
|
|
<p>Copyright 2023 Alex <<a href="mailto:alex@blueselene.com">alex@blueselene.com</a>>. This website is hosted at Codeberg: <a href="https://codeberg.org/YellowComet/pages">YellowComet/pages</a>.</p>
|
|
<p>This webpage is licensed under the Creative Commons Attribution-ShareAlike 4.0 International license, see <a href="https://codeberg.org/YellowComet/pages/src/branch/main/LICENSE">here</a> for the license, and Creative Commons for a <a href="https://creativecommons.org/licenses/by-sa/4.0/">summary</a> of the license.</p>
|
|
</body>
|
|
</html>
|