Skip to content

Instantly share code, notes, and snippets.

View neo1908's full-sized avatar

neo1908

View GitHub Profile
@neo1908
neo1908 / proof.md
Created April 9, 2025 23:52

$argon2id$v=19$m=512,t=256,p=1$jNt8BQuiMsPdwbIpgIO8HQ$4Eo0dq5cEblgX6415IgpAObFPfHLw5uz6NDU0yuXQW8

@neo1908
neo1908 / doomsday-recovery.md
Created January 18, 2022 18:43

Doomsday Recovery

This page serves as a dumping ground for ideas on preserving access to online ( and offline ) accounts in the event of disaster

General Principles

  • All passwords are stored in a password safe ( KeePass )
  • Password safe lives on the NAS and is backed up once per day to a spare nas
  • primary NAS is backed up once per week to B2 Storage
@neo1908
neo1908 / lets-encypt-internal.md
Last active December 2, 2021 15:50
Let's Encrypt On Internal Infratructure

Internal Let's Encrypt Certificates

Here are some thoughts and ideas on how I have lets encrypt certificates deployed to home infrastructure ...

At a high level , my setup assigns a hostname based subdomain for each internal host.

E.G. If my registered domain is example.com and my host is host1 then I will generate a cert for host1.example.com.

Let's encrypt supports wildcards, you could use a wildcard if you wanted to. I didn't like the idea of every internal host using the same keypair.

@neo1908
neo1908 / keys.pub.txt
Last active December 25, 2021 17:04
BEGIN MESSAGE.
RqU8I9DzFfGl3Bd 8G8rwJqZCf7Dzv8 kRgQzc37c21ENZF zfXbJz9N7XvyoqH
ETRSa4fAY5E3ix3 Kz52Fw2Twl4TCKq 6Xr2MZHgg77QYZH gzRA51LPJOs86yr
RLBTVnfaHOX7RgS a7yCyo4AwozpWeL RiUBamOUb1W6AH8 ZJyYxIIOIPums52
XOSENEUBffENckJ TeIAlR1mHNIxSwz oeF9u2IP.
END MESSAGE.
@neo1908
neo1908 / keybase.md
Last active November 29, 2016 22:37

Keybase proof

I hereby claim:

  • I am neo1908 on github.
  • I am neo1911 (https://keybase.io/neo1911) on keybase.
  • I have a public key whose fingerprint is 4266 38DB 7952 1C61 2EE2 68B7 AD95 0A08 7310 D01C