GPG Sign blog posts #27

Open
opened 2025-11-21 02:42:12 +00:00 by pfych · 1 comment
Owner

Possible to hit a specific endpoint to get if the most recent related commit was signed:

https://git.pfy.ch/api/v1/repos/pfych/static/commits?path=packages/site/posts/thoughts/dream-spaces.md&limit=0

@ commit.verification.verified = true

This can render a badge for if the post was made with a signed commit.

I'd also like to inline a GPG signature in the blog post to allow curl https://pfy.ch/path.html | gpg but requires more research

Possible to hit a specific endpoint to get if the most recent related commit was signed: ``` https://git.pfy.ch/api/v1/repos/pfych/static/commits?path=packages/site/posts/thoughts/dream-spaces.md&limit=0 ``` @ `commit.verification.verified = true` This can render a badge for if the post was made with a signed commit. I'd also like to inline a GPG signature in the blog post to allow `curl https://pfy.ch/path.html | gpg` but requires more research
Author
Owner

I should be able to create a script I can run on my machine to generate a GPG key before pushing to add to the markdown frontmatter and it can render like this:

<html>
  <body>
    <div>Header etc</div>
<!-- BEGIN SIGNED MESSAGE -->
example
<!-- -- BEGIN SIGNATURE --
example
-- END -- -->
    <div>Footer etc</div>
  </body>
</html>

Will need to include the comments in the signature.

Not sure if it'll be easier to sign the whole HTML vs signing just the content. 🤔

I should be able to create a script I can run on my machine to generate a GPG key before pushing to add to the markdown frontmatter and it can render like this: ```html <html> <body> <div>Header etc</div> <!-- BEGIN SIGNED MESSAGE --> example <!-- -- BEGIN SIGNATURE -- example -- END -- --> <div>Footer etc</div> </body> </html> ``` Will need to include the comments in the signature. Not sure if it'll be easier to sign the whole HTML vs signing just the content. 🤔
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pfych/static#27
No description provided.