← Back to home
Comparison · DevOps

Libreswan vs Manticore Search

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

Libreswan vs Manticore Search: at a glance

FeatureLibreswanManticore Search
SectorDevOpsDevOps
Velocity score6.36.3
Sparks · 30d11
Top themesipsec, post-quantum crypto, ikev2, rfc 9370search engine, sharding, patch cadence, query correctness
Last editorial update4d ago23h 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 Manticore Search?

Three patch releases in eight hours: Manticore's 29.0 line is being stabilized in public.

Manticore shipped 29.0.3, 29.0.4 and 29.0.5 inside a single day, three days after the 29.0.2 release notes consolidated the sharding work. Two are correctness fixes in query handling — internal sort helper columns leaking into LEFT JOIN output, and NEAR and proximity distances being reset by repeated JSON query fixup. The third hardens the binary API against malformed search counts under a reported advisory.

Read the full Manticore Search trajectory →

Libreswan vs Manticore Search: 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.

M6.3

Three patch releases in eight hours: Manticore's 29.0 line is being stabilized in public.

◆ Current state

Manticore shipped 29.0.3, 29.0.4 and 29.0.5 inside a single day, three days after the 29.0.2 release notes consolidated the sharding work. Two are correctness fixes in query handling — internal sort helper columns leaking into LEFT JOIN output, and NEAR and proximity distances being reset by repeated JSON query fixup. The third hardens the binary API against malformed search counts under a reported advisory.

◆ Where it's heading

The pattern after a major line opens is holding: the commit-level train keeps running at multiple releases a day while the newly exposed surfaces — sharded tables, LEFT JOIN, JSON query parsing — report their edge cases back. The bugs being caught are shaped by what 29.0 changed rather than by new work, and each one arrives with regression coverage attached, which is why they land as separate patch releases rather than accumulating. Search-side work continues to split between classic full-text concerns and the vector and conversational paths.

◆ Prediction

The patch cadence should keep compressing toward the ordinary rhythm as the 29.0 edge cases drain; the next substantive item is more likely to come from the columnar and KNN thread than from sharding, which has just had its release.

Alternatives to Libreswan and Manticore Search

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 Manticore Search.

See all Libreswan alternatives → · See all Manticore Search alternatives →

Recent activity from Libreswan and Manticore Search

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

  1. 1d agoManticore SearchNEAR and proximity distances survive repeated JSON query fixup
  2. 1d agoManticore SearchInternal sort columns no longer leak into LEFT JOIN results
  3. 1d agoManticore SearchBinary API rejects malformed search counts before allocating
  4. 4d agoManticore SearchManticore 29.0 makes sharded tables operable and changes the SHARD_WRITE protocol
  5. 5d agoManticore Search29.0.2 bumps manticore-backup to 1.10.3 and Buddy to 4.4.1
  6. 5d agoLibreswan5.4: ML-KEM 768 and RFC 9370 multiple key exchanges for IKEv2
  7. 6d agoManticore SearchSHOW TABLE SETTINGS now works on sharded tables
  8. 1mo agoLibreswan5.3.2: FIPS-mode daemon crash from malformed X.509 certificates
  9. 1mo agoLibreswan5.3.1: three CVEs and a newer-GCC compile fix
  10. 2y agoLibreswanIKEv1 cryptosuite defaults tightened; systemd libxz dependency dropped
  11. 2y agoLibreswanCompile error fix carried over from 4.13

Frequently asked questions

What is the difference between Libreswan and Manticore Search?

They serve adjacent needs but don't currently overlap on shipped themes. Libreswan and Manticore Search are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Libreswan better than Manticore Search?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Libreswan and Manticore Search are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 Manticore Search?

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