soc.octade.net is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Admin email
social@octade.net

Search results for tag #signatures

[?]Guy [he/him] » 🌐
@phlogiston@mastodon.nz

It's been repeatedly argued that end-to-end email (encryption), particularly using OpenPGP/GPG/PGP is not suitable ... understood.

But I'm still unsure about what people's feeling is for cryptographically *signed* emails. If not using GnuPG, what then? I know there's S/MIME, but that's rather 'top heavy'. For encryption, `age` is a suitable replacement (in the non-email context). For signing, there's Minisign in a similar context.

But ... I'm still thinking that there's *especially* value for signing (fully authenticating) email.

Any positions on how to approach that these days? Or *why not* to do it?

    4 ★ 3 ↺

    [?]OCTADE » 🌐
    @octade@soc.octade.net

    PHP Automatic Cryptographic Signature And Website Generator

    [demo] https://files.octade.net/

    I drafted a prototype for a PHP server application that automatically hashes and signs files and presents visitors with verification archives containing digital signatures for offline verification. The site allows readers to view, download, hash, and verify signatures of files. Since I occasionally like to publish puzzles and bits of cryptology, I just had to make this to scratch the old itch.

    The neat thing about this design is that the current version has zero JavaScript. It uses CSS3 hacks with anchors and URL probing to emulate JavaScript and AJAX functionalities for modal dialogs to present server-side JSON data as HTML text.

    When I upload files or documents to the server, the interface automatically presents them to the user in a grid. So now all I have to do is upload files and documents and the server generates the site.

    The reader can then click buttons to hash, sign, view, verify, and download files.

    GnuPG and OpenSSL Signatures are generated automatically on user demand. The site visitors can download these signatures and the public keys to verify files.

    What should I add / change in the application and its interface?

    What accessibility components might be warranted?

    Should the application parse and present EXIF data, or is that too much?

    @cryptography@soc.octade.net

      5 ★ 3 ↺

      [?]OCTADE » 🌐
      @octade@soc.octade.net

      How to Upgrade GnuPG to Generate Kyber and Goldilocks Keys

      I see some people still using ancient PGP keys. GnuPG offers Linux repositories for updating to the latest versions of GnuPG with new expert features for key generation. Recent versions support both Kyber1024 and Goldilocks448 keys (and more).

      Once installed run: :~$ gpg --full-generate-key --expert

      New GnuPG Repositories for Debian, Ubuntu, and Devuan: Stable and Development Branches Available

      https://www.gnupg.org/blog/20250827-new-repository.html