| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 751da2c (posts: Update posts to reflect usage of cgit's signature
mechanism, 2021-05-06) updated the project pages as well as "Verifying
snapshots with signify" with information regarding the new cgit
signature mechanism, but neglected to mention that signatures can be
obtained directly through git.oriole.systems as well (the project pages
merely deeplink to that).
Furthermore, with commit 28c2473 (posts: Add a new post: "Hosting
signify signatures on cgit", 2021-05-16) we now have an explanatory
piece which we can link if people are interested in the underlying
infrastructure.
|
| |
|
|
| |
Let's hope that bug is fixed in the next 10 years!
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
cgit can host detached signatures using git-notes(1). Since we want to
make use of that going forward and have finally gotten around to setting
it up fully, we need to make some small changes to
verify-with-signify.md and the weltschmerz project page.
Specifically, we no longer host both the signature and the checksum
(since this would be too cumbersome to maintain with cgit), rendering
the choice explained in the post moot. Since the detached signature has
always contained the checksum, however, we can just fall back to a
slightly different invocation for verifying it.
|
| |
|
|
|
| |
In light of the addition of the author metadata tag to <head>, we
decided to use our full name in the post tags.
|
| | |
|
| | |
|
| |
|
