Back to matrix

E03-HP: Pending

Rationale

The December 2025 Linkoping project report supersedes treating the 2024 ECDSA failure as the latest candidate evidence. Section 4.1 reports PyHIP using ECDSA/SHA-384 with AES-256-GCM. Section 4.2 separately reports OpenHIP/OpenSSL provider integration and algorithm tests, and asserts base-exchange/ESP support. These are different implementation tracks; their results cannot be combined into one demonstrated profile.

Assessment method

Newer primary developer report, implementation-track and selected-suite comparison; no execution

Source context

Rosengren, Amin, Kanefall and Sohail, Improving the Open Source HIPv2 Implementation, 17 December 2025, sections 4.1 and 4.2

Outstanding qualification

Pending: bind a public code revision and license/dependency inventory to ECDSA P-256, ECDH P-256, HIT suite 2, ESP transform 8 and RFC 8046 mobility together. The report does not supply that exact complete binding. Its OpenSSL algorithm/provider results alone do not establish the selected HIP composition; its PyHIP GCM witness does not establish the selected CBC transform. The old failure is historical, not evidence that current ECDSA support is absent.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.