← Back to home
Comparison · DevOps

Libreswan vs r311

A side-by-side editorial comparison of Libreswan and r311 — release velocity, themes, recent moves, and the top alternatives to consider.

Libreswan vs r311: at a glance

FeatureLibreswanr311
SectorDevOpsDevOps
Velocity score6.30.0
Sparks · 30d10
Top themesipsec, post-quantum crypto, ikev2, rfc 9370open311, civic data, api client, endpoint curation
Last editorial update16h ago1h ago
WebsiteVisit →Visit →

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.

Read the full Libreswan trajectory →

What is r311?

r311 curates a catalogue of Open311 endpoints and now marks the dead ones explicitly.

r311 wraps Open311 civic-issue APIs behind one R interface, with a bundled list of municipal endpoints. Recent releases are dominated by keeping that list current — Helsinki added in 0.4.4, Espoo and Oulu in 0.4.3, with Ottawa, Siegburg, Northfield and Annaberg-Buchholz deprecated. Version 0.4.3 added the machinery to record that decay: questioned and deprecated keys that make o311_api() warn or abort.

Read the full r311 trajectory →

Libreswan vs r311: editorial side-by-side

L
Libreswan
DEVOPS
6.3

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.

R
r311
DEVOPS
0.0

r311 curates a catalogue of Open311 endpoints and now marks the dead ones explicitly.

◆ Current state

r311 wraps Open311 civic-issue APIs behind one R interface, with a bundled list of municipal endpoints. Recent releases are dominated by keeping that list current — Helsinki added in 0.4.4, Espoo and Oulu in 0.4.3, with Ottawa, Siegburg, Northfield and Annaberg-Buchholz deprecated. Version 0.4.3 added the machinery to record that decay: questioned and deprecated keys that make o311_api() warn or abort.

◆ Where it's heading

The package's real work is curation, and it has started treating endpoint rot as a first-class state rather than letting requests fail silently. Error handling and condition objects were hardened in the same release, which fits a client whose dominant failure mode is a city's server going away. Releases are small and roughly annual.

◆ Prediction

Expect the next release to be another catalogue pass — a city or two added, more moved to questioned or deprecated — rather than new API surface.

Alternatives to Libreswan and r311

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 r311.

See all Libreswan alternatives → · See all r311 alternatives →

Recent activity from Libreswan and r311

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoLibreswan5.4: ML-KEM 768 and RFC 9370 multiple key exchanges for IKEv2
  2. 29d agoLibreswan5.3.2: FIPS-mode daemon crash from malformed X.509 certificates
  3. 1mo agoLibreswan5.3.1: three CVEs and a newer-GCC compile fix
  4. 6mo agor311Adds Helsinki to the endpoint catalogue
  5. 1y agor311Deprecation system for dead Open311 endpoints
  6. 2y agoLibreswanIKEv1 cryptosuite defaults tightened; systemd libxz dependency dropped
  7. 2y agoLibreswanCompile error fix carried over from 4.13

Frequently asked questions

What is the difference between Libreswan and r311?

They serve adjacent needs but don't currently overlap on shipped themes. Libreswan is currently shipping more aggressively (velocity 6.3 vs 0.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 r311?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Libreswan is currently shipping more aggressively (velocity 6.3 vs 0.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 r311?

Top r311 alternatives in DevOps are ranked by recent ship velocity. Browse the "r311 alternatives" section above for the current picks, or visit /alternatives/r311 for the full list with editorial commentary on each.