Recordsgolanggolang.org/x/cryptofailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
FAIL: Handshake SubTypeName mismatch: got <str>, expected <str> · exit status 1
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-03 · Last seen: 2026-09-03
sha256:c3643b16b6fb…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.11.1-0.20230711161743-2e82bdd1719d not measured
- v0.3.0 not measured
- v0.0.0-20220525230936-793ad666bf5e not measured
- v0.0.0-20220331220935-ae2d96664a29 FAIL
- v0.0.0-20210921155107-089bfa567519 not measured
- v0.0.0-20210711020723-a769d52b0f97 not measured
- v0.0.0-20210616213533-5ff15b29337e not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-03 → 2026-09-03
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v0.11.1-0.20230711161743-2e82bdd1719d | v0.3.0 | v0.0.0-20220525230936-793ad666bf5e | v0.0.0-20220331220935-ae2d96664a29 | v0.0.0-20210921155107-089bfa567519 | v0.0.0-20210711020723-a769d52b0f97 | v0.0.0-20210616213533-5ff15b29337e |
|---|---|---|---|---|---|---|---|
| golang.org/x/net | v0.10.0 | v0.2.0 | v0.0.0-20211112202133-69e39bad7dc2 | — | v0.4.0 | v0.0.0-20210226172049-e18ecbb05110 | v0.0.0-20210226172049-e18ecbb05110 |
| golang.org/x/sys | v0.47.0 | v0.2.0 | v0.0.0-20220608164250-635b8c9b7f68 | — | v0.47.0 | v0.0.0-20210615035016-665e8c7367d1 | v0.0.0-20210615035016-665e8c7367d1 |
| golang.org/x/term | v0.10.0 | v0.2.0 | v0.0.0-20201126162022-7de9c90e9dd1 | — | v0.0.0-20210927222741-03fcf44c2211 | v0.0.0-20201126162022-7de9c90e9dd1 | v0.0.0-20201126162022-7de9c90e9dd1 |
Moved: 3 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29: bcrypt.CompareHashAndPassword, bcrypt.Cost, bcrypt.GenerateFromPassword This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbcrypt.CompareHashAndPasswordbcrypt.Costbcrypt.GenerateFromPassword MIT-0 · 2026-08-27