github.com/SwuduSusuwu/SusuLib.git (moved from github.com/SwuduSusuwu/SubStack.git) has new certificate. Signature is "SHA256:8MXQK2Ms1FI4X3BSNbLuYAAMO3MXPQ7GsGH4kcXNDiY"

Relevant commits:

• @.ssh/setup.sh, @SECURITY.md#security-policy commit 7aa753d

• @.ssh/id_ed25519.pub; new certificate. commit 4073fc7

• @SECURITY.md#erratafootnotes; date -> hash commit 40bf1ae

As far as know, the previous certificate was not "compromised", but it was used on numerous devices, so it is best practice to switch to new. Used old certificate for signing of new (all commits which follow shall use new).

Is followup to:

Repo move

• @README.md#purposes; /SubStack -> /SusuLib @8617dcdac97d4229f857d9560078990d3f5a8d3c

• Planned repo move to SusuLib; who has comments / responses / suggestions? #58

• The old repo was just called “SubStack” since its original purpose was to mirror the https://swudususuwu.substack.com/ posts. Posts were split into the new repo at https://github.com/SwuduSusuwu/SusuPosts/tree/preview (git clone https://github.com/SwuduSusuwu/SusuPosts.git && git switch preview); SusuLib now focuses on source code.