Andrej Shadura

@andrew_shadura
336 Followers
217 Following
4.4K Posts
I need reasons?😬
#ArtemisII My latest cartoon for @[email protected]
I may be old but I still have cat like reflexes, I've knocked three different things off the counter already today.

Here we see a cat dividing by mitosis and share the same chromosomal jeans

#caturday #caturdayeveryday

Prague railway station has a LEGO model of Prague railway station.

ICYMI 👉 Apertis v2026 is now available! Based on Debian 13 (Trixie), this latest release delivers updated system libraries, development tools, compilers, and core services, alongside a new default Wayland compositor, a reworked SDK, and smarter packaging pipelines.

Read more: https://www.collabora.com/news-and-blog/news-and-events/apertis-v2026-modern-foundation-industrial-embedded-development.html

#Apertis #EmbeddedLinux #Debian #Trixie #OpenSource

Apertis v2026: A modern foundation for industrial embedded development

Apertis v2026 blazes new trails as the first release based on Debian 13 Trixie plus a range of new features!

Collabora | Open Source Consulting

GnuPG exists for one sole reason:
The original PGP crew in the 1990s decided that open standards, collaboration and multiple implementations are cool.

So they published their - at the time groundbreaking - formats, and standardized them at the IETF.

GnuPG has benefited massively from this, while at the same time being a software that no one I know has ever truly enjoyed. I certainly have not.

This project is now attempting to do a standardization rug pull. It's ridiculous and enraging.

Also see https://chaos.social/@dvzrv/116460347482223544

It would appear that GnuPG upstream is trying to use its influence to create facts on the ground (by proliferation of its proprietary non-OpenPGP formats).

Regular PSA reminder:

While GnuPG 2.5.x implements hybrid PQC encryption based on ML-KEM, just like https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/, GnuPG's implementation is entirely incompatible with the IETF-specified format, which all other libraries are implementing.
Both serialization and the KEM combiners differ.

The bottom line is that anyone who wants to use vendor-agnostic PQC with OpenPGP should *avoid GnuPG's PQC key formats*.

This is all exceedingly unfortunate and weird, and frankly, a total disgrace.

Post-Quantum Cryptography in OpenPGP

This document defines a post-quantum public key algorithm extension for the OpenPGP protocol, extending RFC9580. Given the generally assumed threat of a cryptographically relevant quantum computer, this extension provides a basis for long-term secure OpenPGP signatures and ciphertexts. Specifically, it defines composite public key encryption based on ML-KEM (formerly CRYSTALS-Kyber), composite public key signatures based on ML-DSA (formerly CRYSTALS-Dilithium), both in combination with elliptic curve cryptography, and SLH-DSA (formerly SPHINCS+) as a standalone public key signature scheme.

IETF Datatracker

@v_perjorative

Call it Hobbes's Horse.

(Thomas Hobbes raised the (prankish) extension to the Ship of Theseus thought experiment: what is a boat built from the pieces originally replaced on the Ship of Theseus.)