Dear maintainer,

to prepare the switch of the default golang version in unstable,
I've asked Santiago Vila to rebuild all packages which depend
on golang with Go 1.27. This package failed to build, but it
could be built successfully with Go 1.26.

The full build log is available here:

https://people.debian.org/~toddy/ftbfs-golang-1.27/

I'm filing this bug with severity important for now. Once the
default golang compiler has been switched in unstable, this
bug becomes release-critical. When that happens, I'll upgrade
the severity to serious.

Regards,
Tobias

Could this be a Go 1.27 problem to me, it shouldn't panic?

Did something change in this particular crypto implementation between
1.26 and 1.27?

/Simon

PANIC: jose_test.go:2056: TestSuite.TestEncrypt_ECDH_ES_A192KW_A192CBC_HS384

... Panic: runtime error: invalid memory address or nil pointer dereference (PC=0x491564)

/usr/lib/go-1.27/src/runtime/panic.go:859
  in gopanic
/usr/lib/go-1.27/src/runtime/panic.go:336
  in panicmem
/usr/lib/go-1.27/src/runtime/signal_unix.go:931
  in sigpanic
ecdh.go:138
  in Ecdh.deriveKey
ecdh.go:60
  in Ecdh.WrapNewKey
ecdh_aeskw.go:27
  in EcdhAesKW.WrapNewKey
jose.go:343
  in encrypt
jose.go:260
  in EncryptBytes
jose.go:225
  in Encrypt
jose_test.go:2061
  in TestSuite.TestEncrypt_ECDH_ES_A192KW_A192CBC_HS384
/usr/lib/go-1.27/src/reflect/value.go:369
  in Value.Call
/usr/lib/go-1.27/src/runtime/asm_amd64.s:1264
  in goexit