You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ Support requests in an issue-format will be closed immediately. For support, go to Swarm's Discord.
Context
Bee Version: latest
Summary
The isCompressedKey parameter in pkg/crypto/signer.go appears to be unused in SignCompact, which could lead to unexpected behavior.
Is this intentional behaviour?
Expected behavior
The isCompressedKey parameter should influence the btcecdsa.SignCompact call directly to ensure the correct signing format is applied, as the isCompressedKey variable is intended to define the key compression type.
Actual behavior
The isCompressedKey parameter is defined but is not passed to btcecdsa.SignCompacthere. Instead, it is set but not used in the signing process, potentially resulting in signing with the wrong format.
Steps to reproduce
Examine the isCompressedKey variable in the d.sign(hash, true) method, where isCompressedKey is set to true.
Notice that isCompressedKey is not forwarded to the btcecdsa.SignCompact function here.
Possible solution
Update SignCompact to forward isCompressedKey to btcecdsa.SignCompact, ensuring the function call respects the compressed key setting.
The text was updated successfully, but these errors were encountered:
gacevicljubisa
changed the title
isCompressedKey Not Forwarded to SignCompact in signer.go
isCompressedKey not forwarded to SignCompact in signer.go
Oct 31, 2024
gacevicljubisa
changed the title
isCompressedKey not forwarded to SignCompact in signer.goisCompressedKey not forwarded to SignCompact in signer.go
Oct 31, 2024
gacevicljubisa
changed the title
isCompressedKey not forwarded to SignCompact in signer.go
isCompressedKey not forwarded to SignCompact in signer.go
Oct 31, 2024
gacevicljubisa
changed the title
isCompressedKey not forwarded to SignCompact in signer.go
isCompressedKey not forwarded to SignCompact – Intentional or Bug?
Nov 4, 2024
Context
latest
Summary
The
isCompressedKey
parameter inpkg/crypto/signer.go
appears to be unused inSignCompact
, which could lead to unexpected behavior.Is this intentional behaviour?
Expected behavior
The
isCompressedKey
parameter should influence thebtcecdsa.SignCompact
call directly to ensure the correct signing format is applied, as theisCompressedKey
variable is intended to define the key compression type.Actual behavior
The
isCompressedKey
parameter is defined but is not passed tobtcecdsa.SignCompact
here. Instead, it is set but not used in the signing process, potentially resulting in signing with the wrong format.Steps to reproduce
isCompressedKey
variable in the d.sign(hash, true) method, whereisCompressedKey
is set to true.isCompressedKey
is not forwarded to thebtcecdsa.SignCompact
function here.Possible solution
Update SignCompact to forward
isCompressedKey
tobtcecdsa.SignCompact
, ensuring the function call respects the compressed key setting.The text was updated successfully, but these errors were encountered: