Skip to content

fix: treat Dropbear kexguess2 as negotiation marker, not PQ-unsafe KEX - #377

Closed
ranas-mukminov wants to merge 1 commit into
jtesta:masterfrom
ranas-mukminov:fix/kexguess2-not-pq-warn
Closed

ranas-mukminov wants to merge 1 commit into
jtesta:masterfrom
ranas-mukminov:fix/kexguess2-not-pq-warn

Conversation

@ranas-mukminov

Copy link
Copy Markdown

Summary

Fixes #375: kexguess2@matt.ucc.asn.au was listed with WARN_NOT_PQ_SAFE, but it is not a real key-exchange algorithm.

Dropbear defines it as a negotiation / guessing accelerator (data is NULL in common-algo.c); it does not perform a KEX. Marking it post-quantum-unsafe therefore produces a false warning on Dropbear peers.

Changes

  • Add INFO_KEXGUESS2 describing it as a pseudo-algorithm / marker (same pattern as ext-info-* and kex-strict-*).
  • Replace the WARN_NOT_PQ_SAFE entry with an INFO classification.
  • Whitelist it in test_kex_pq_unsafe alongside the other markers.

References

Test plan

  • pytest test/test_ssh2_kexdb.py (2 passed)
  • Audit a Dropbear host offering kexguess2@matt.ucc.asn.au — no PQ-unsafe warning for that name; INFO note present instead.

kexguess2@matt.ucc.asn.au is a Dropbear KEX guessing marker (data field
NULL), not an actual key-exchange algorithm. Flagging it with
WARN_NOT_PQ_SAFE is misleading (jtesta#375). Classify it like ext-info /
kex-strict pseudo-algorithms with an INFO note instead.
@jtesta

jtesta commented Oct 17, 2026

Copy link
Copy Markdown
Owner

Fixed in 68953dd.

@jtesta jtesta closed this Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dropbear kexguess2 "algorithm" flagged as not postquantum-safe

2 participants