Liquidsoap
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
Comparison · DevOps
Libreswan vs pgBackRest
A side-by-side editorial comparison of Libreswan and pgBackRest — release velocity, themes, recent moves, and the top alternatives to consider.
Libreswan vs pgBackRest: at a glance
What is Libreswan?
Libreswan puts post-quantum key exchange into IKEv2 — ML-KEM 768 ships in v5.4.
Libreswan spent the last two releases on security patches, including a CVE found when the project ran an AI audit over its own codebase. v5.4 breaks that pattern: it implements RFC 9370's multiple-key-exchange machinery end to end — IKE_INTERMEDIATE, IKE_ADDITIONAL_KE and IKE_FOLLOWUP_KE — and uses it to carry ML_KEM_768 in IKE_SA_INIT and IKE_INTERMEDIATE. The rest of the release is a wide maintenance sweep across kernel integration on the BSDs, config parsing and logging.
What is pgBackRest?
pgBackRest tracks PostgreSQL 19 beta by beta, patching the hangs it finds along the way.
pgBackRest is in the tail of the 2.59 cycle, which brought PostgreSQL 19 support and restricted every command except restore from running as root. The 2.59.1 patch keeps step with PostgreSQL 19beta3 and clears three defects, including a hang that occurred whenever the chunk buffer was smaller than the input buffer. Release cadence remains a few feature releases a year with patches slotted between them.
Libreswan vs pgBackRest: editorial side-by-side
Libreswan
6.3DEVOPS
Libreswan puts post-quantum key exchange into IKEv2 — ML-KEM 768 ships in v5.4.
◆ Current state
Libreswan spent the last two releases on security patches, including a CVE found when the project ran an AI audit over its own codebase. v5.4 breaks that pattern: it implements RFC 9370's multiple-key-exchange machinery end to end — IKE_INTERMEDIATE, IKE_ADDITIONAL_KE and IKE_FOLLOWUP_KE — and uses it to carry ML_KEM_768 in IKE_SA_INIT and IKE_INTERMEDIATE. The rest of the release is a wide maintenance sweep across kernel integration on the BSDs, config parsing and logging.
◆ Where it's heading
The post-quantum work is the spine of this release and it is not experimental framing — it is standards-track RFC 9370 plus a hard dependency on NSS 3.118.1, meaning distributions have to move their crypto library before users can turn it on. Around it, the project keeps grinding on operator experience: better proposal parsing, more specific error messages, traffic selectors and DIGSIG algorithms in logs, and rate-limited logging. Experimental flags for subnet leasing and updown-config suggest the next capability additions are already staged.
◆ Prediction
Expect ML-KEM to move from supported to recommended in default proposals once NSS 3.118.1 is widely packaged, and the experimental leftaddresspool subnet leasing and per-connection debug options to stabilize in a following release.
pgBackRest
5.0DEVOPS
pgBackRest tracks PostgreSQL 19 beta by beta, patching the hangs it finds along the way.
◆ Current state
pgBackRest is in the tail of the 2.59 cycle, which brought PostgreSQL 19 support and restricted every command except restore from running as root. The 2.59.1 patch keeps step with PostgreSQL 19beta3 and clears three defects, including a hang that occurred whenever the chunk buffer was smaller than the input buffer. Release cadence remains a few feature releases a year with patches slotted between them.
◆ Where it's heading
Two currents continue. Support for the next PostgreSQL major arrives experimentally a full release before it is needed — 18 in 2.55.0, 19 in 2.59.0, and now tracking 19's betas point by point — so the backup tool is ready before the database ships. The second is a move away from ambient privilege and toward cloud-native identity: managed identities and pod identity in place of stored keys, and the root restriction narrowing what a compromised invocation can reach. The 2.59.1 fixes are the ordinary cost of that pace, including a packaging fault in the GitHub source archives.
◆ Prediction
Expect the beta-tracking patches to continue through PostgreSQL 19's release cycle, with the next feature release arriving after 19 goes final rather than before it.
Alternatives to Libreswan and pgBackRest
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Libreswan or pgBackRest.
Appwrite
Appwrite keeps reworking its own plumbing — Go CLI, SquashFS mounts, and an MCP layer that refreshes itself
FusionAuth
FusionAuth's feed publishes version numbers; whether they carry news is a coin flip.
Sanity
Sanity ships across every package at once, and the agent-facing surface moves fastest.
ESP-IDF
The 6.1 candidate arrives carrying the same notes the beta already shipped in June.
Auth0
Auth0 hands tenants a throttle on their own noisy apps
See all Libreswan alternatives → · See all pgBackRest alternatives →
Recent activity from Libreswan and pgBackRest
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agopgBackRestv2.59.1: PostgreSQL 19beta3 Support
- 5d agoLibreswan5.4: ML-KEM 768 and RFC 9370 multiple key exchanges for IKEv2 ⚡
- 1mo agopgBackRestv2.59.0: PostgreSQL 19 Support
- 1mo agoLibreswan5.3.2: FIPS-mode daemon crash from malformed X.509 certificates
- 1mo agoLibreswan5.3.1: three CVEs and a newer-GCC compile fix
- 7mo agopgBackRestv2.58.0: Object Storage Improvements
- 10mo agopgBackRestv2.57.0: Suppress Repository Symlinks
- 1y agopgBackRestv2.55.1: Bug Fixes
- 1y agopgBackRestv2.56.0: Progress Info Improvements
- 2y agoLibreswanIKEv1 cryptosuite defaults tightened; systemd libxz dependency dropped
- 2y agoLibreswanCompile error fix carried over from 4.13
Frequently asked questions
What is the difference between Libreswan and pgBackRest?
They serve adjacent needs but don't currently overlap on shipped themes. Libreswan is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Libreswan better than pgBackRest?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Libreswan is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
What are the best alternatives to Libreswan?
Top Libreswan alternatives in DevOps are ranked by recent ship velocity. Browse the "Libreswan alternatives" section above for the current picks, or visit /alternatives/libreswan for the full list with editorial commentary on each.
What are the best alternatives to pgBackRest?
Top pgBackRest alternatives in DevOps are ranked by recent ship velocity. Browse the "pgBackRest alternatives" section above for the current picks, or visit /alternatives/pgbackrest for the full list with editorial commentary on each.