'sudo sbctl verify' Returning 'panic: bytes.Buffer: truncation out of range'

I’ve been updating my system the last few days with the standard ‘sudo pacman -Syu’ and it runs fine, but whenever something changes that wants sbctl to sign anything new then it returns an error and ignores any other signing jobs. I ran

sudo sbctl verify

And I get this long-winded repsonse

panic: bytes.Buffer: truncation out of range

goroutine 1 [running]:
bytes.(*Buffer).Truncate(...)
        bytes/buffer.go:98
github.com/foxboron/go-uefi/authenticode.Parse({0x584b24c73aa0, 0xc00006a1a0})
        github.com/foxboron/go-uefi@v0.0.0-20240722190620-5d4f760099bd/authenticode/checksum.go:201 +0xe1b
github.com/foxboron/sbctl/backend.(*KeyHierarchy).VerifyFile(0xc000090400, 0xa0?, {0x584b24c73aa0, 0xc00006a1a0})
        github.com/foxboron/sbctl/backend/backend.go:160 +0x245
github.com/foxboron/sbctl.VerifyFile(0x584b24c731d8?, 0xc000090400, 0x3, {0xc0001482a0?, 0x1?})
        github.com/foxboron/sbctl/keys.go:29 +0xdc
main.VerifyOneFile(0xc0001180c0, {0xc0001482a0, 0x24})
        github.com/foxboron/sbctl/cmd/sbctl/verify.go:51 +0x2d9
main.RunVerify.func1(0xc00011e2a0)
        github.com/foxboron/sbctl/cmd/sbctl/verify.go:99 +0x45
github.com/foxboron/sbctl.SigningEntryIter(0xc0001180c0, 0xc000031b30)
        github.com/foxboron/sbctl/database.go:58 +0x150
main.RunVerify(0xc00012a500?, {0x584b24f8e8a0, 0x0, 0x584b24af2407?})
        github.com/foxboron/sbctl/cmd/sbctl/verify.go:97 +0x33b
github.com/spf13/cobra.(*Command).execute(0x584b24ef2000, {0x584b24f8e8a0, 0x0, 0x0})
        github.com/spf13/cobra@v1.8.1/command.go:985 +0xaca
github.com/spf13/cobra.(*Command).ExecuteC(0x584b24ef0620)
        github.com/spf13/cobra@v1.8.1/command.go:1117 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
        github.com/spf13/cobra@v1.8.1/command.go:1041
github.com/spf13/cobra.(*Command).ExecuteContext(...)
        github.com/spf13/cobra@v1.8.1/command.go:1034
main.main()
        github.com/foxboron/sbctl/cmd/sbctl/main.go:166 +0x5a7

Anybody that can assist me in fixing this issue? I’m still new around this type of stuff.

You should probably report it upstream

1 Like

Will do. I appreciate the response.