askiiart/askiiart-net
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

new PGP key

Browse source
This commit is contained in:
askiiart 2024-04-01 23:50:14 -05:00
parent 7472397ab1
commit 5e7ff5e5ad
Signed by untrusted user who does not match committer: askiiart
GPG key ID: BC3800E55FB54D67
12 changed files with 330 additions and 170 deletions

6
blog/feed.xml
View file

@ -5,7 +5,7 @@
<title>askiiart.net blog</title>
<description>The feed for askiiart.net but just the blog, I guess</description>
<link>https://askiiart.net/blog/</link>
<lastBuildDate>Wed, 13 Mar 2024 01:44:19 +0000</lastBuildDate>
<lastBuildDate>Tue, 02 Apr 2024 04:49:45 +0000</lastBuildDate>
<item>
<title>300</title>
<link>https://askiiart.net/til/300.html</link>
@ -18,6 +18,10 @@
<title>Marlin Boot Animations</title>
<link>https://askiiart.net/til/marlin-boot-animations.html</link>
</item>
<item>
<title>New PGP key, and new directory</title>
<link>https://askiiart.net/til/new-pgp-key.html</link>
</item>
</channel>
</rss>

50
blog/new-pgp-key.html Normal file
View file

@ -0,0 +1,50 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta content="width=device-width, initial-scale=1" charset="utf-8" />
<link rel="icon" href="/assets/askiiart.gif" type="image/icon">
<title>New PGP key, and new directory</title>
<link href="/style.css" type="text/css" rel="stylesheet" />
<link href="/prism.css" rel="stylesheet" />
</head>
<body class="line-numbers">
<h1 id="new-pgp-key-and-new-directory">New PGP key, and new
directory</h1>
<p>Due to btrfs deciding to corrupt itself, I've lost my master
keys for
<code>02EF A1CE 3C3E 4AAD 7A86 3AB8 ED24 985C A884 CD61</code>.
It has not been compromised (as far as I know, at least), and
everything done with the old key is still valid. Although the
current subkeys are valid for another 6-ish months (until
2024-10-09), I'll be moving to a new key proactively.</p>
<p><strong>My new key is
<code>CFCF 6723 A8ED 791C 5FD2 5CB5 8589 69DC CC2E 792D</code>.</strong></p>
<p>This commit will be signed and pushed with the old key,
<code>0xED24985CA884CD61</code>, then afterwards I will
immediately be switching to the new key,
<code>0x858969DCCC2E792D</code>. The old key will be removed
from my YubiKey and replaced with the new one, and I will be
unable to read anything encrypted to the old key.</p>
<hr />
<p>There's also now a <a href="/data/">/data/</a> directory,
which as of the time of writing, just contains <a
href="/data/old-pubkey-02EFA1CE3C3E4AAD7A863AB8ED24985CA884CD61.asc">my
old key</a>, the public key of <code>0x858969DCCC2E792D</code>'s
<em>master key only</em> signed with my old key, and <a
href="/data/new-pgp-key.asc">a detached signature</a> for the
markdown version of this file signed with
<code>0xED24985CA884CD61</code> saying I'm moving to
<code>0x858969DCCC2E792D</code>.</p>
<p><strong>My current PGP public key will always be at <a
href="/pubkey.asc">/pubkey.asc</a>.</strong></p>
<p><em>Note</em>: Assuming this actually gets done on April 1st,
no, this isn't an April Fools joke. If I were to do an April
Fools joke, it would absolutely have a disclaimer from the
second it goes up that it's an April Fools joke, but that's a
rant for another time.</p>
<script src="/prism.js"></script>
</body>
<footer>
<p><a href="https://git.askiiart.net/askiiart/askiiart-net">code</a> (<a href="https://github.com/askiiart/askiiart.github.io">mirror</a>)&emsp;<a href="/feed.xml">rss</a>&emsp;<a href="/pubkey.asc">pubkey</a></p>
</footer>
</html>

15
blog/new-pgp-key.md Normal file
View file

@ -0,0 +1,15 @@
# New PGP key, and new directory
Due to btrfs deciding to corrupt itself, I've lost my master keys for `02EF A1CE 3C3E 4AAD 7A86 3AB8 ED24 985C A884 CD61`. It has not been compromised (as far as I know, at least), and everything done with the old key is still valid. Although the current subkeys are valid for another 6-ish months (until 2024-10-09), I'll be moving to a new key proactively.
**My new key is `CFCF 6723 A8ED 791C 5FD2 5CB5 8589 69DC CC2E 792D`.**
This commit will be signed and pushed with the old key, `0xED24985CA884CD61`, then afterwards I will immediately be switching to the new key, `0x858969DCCC2E792D`. The old key will be removed from my YubiKey and replaced with the new one, and I will be unable to read anything encrypted to the old key.
---
There's also now a [/data/](/data/) directory, which as of the time of writing, just contains [my old key](/data/old-pubkey-02EFA1CE3C3E4AAD7A863AB8ED24985CA884CD61.asc), the public key of `0x858969DCCC2E792D`'s *master key only* signed with my old key, and [a detached signature](/data/new-pgp-key.asc) for the markdown version of this file signed with `0xED24985CA884CD61` saying I'm moving to `0x858969DCCC2E792D`.
**My current PGP public key will always be at [/pubkey.asc](/pubkey.asc).**
*Note*: Assuming this actually gets done on April 1st, no, this isn't an April Fools joke. If I were to do an April Fools joke, it would absolutely have a disclaimer from the second it goes up that it's an April Fools joke, but that's a rant for another time.