We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description
When running cosign generate-key-pair in a directory where it cannot write to, it results in a panic:
cosign generate-key-pair
$ docker run -it --rm -e COSIGN_PASSWORD= -u1000:1000 gcr.io/projectsigstore/cosign:v1.10.1 generate-key-pair panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xd7bd7c] goroutine 1 [running]: github.com/sigstore/cosign/pkg/cosign.FileExists({0x27668bd?, 0x0?}) github.com/sigstore/cosign/pkg/cosign/common.go:35 +0x5c github.com/sigstore/cosign/cmd/cosign/cli/generate.GenerateKeyPairCmd({0x2b8bd80, 0xc0001ac000}, {0x0?, 0x0?}, {0x3f38378?, 0x0?, 0x0?}) github.com/sigstore/cosign/cmd/cosign/cli/generate/generate_key_pair.go:88 +0x22a github.com/sigstore/cosign/cmd/cosign/cli.GenerateKeyPair.func1(0xc0006be000?, {0x3f38378?, 0x0?, 0x0?}) github.com/sigstore/cosign/cmd/cosign/cli/generate_key_pair.go:66 +0x4c github.com/spf13/cobra.(*Command).execute(0xc0006be000, {0x3f38378, 0x0, 0x0}) github.com/spf13/cobra@v1.5.0/command.go:872 +0x694 github.com/spf13/cobra.(*Command).ExecuteC(0xc00017a000) github.com/spf13/cobra@v1.5.0/command.go:990 +0x3b4 github.com/spf13/cobra.(*Command).Execute(...) github.com/spf13/cobra@v1.5.0/command.go:918 main.main() github.com/sigstore/cosign/cmd/cosign/main.go:61 +0x4c
Version
1.10.1
The text was updated successfully, but these errors were encountered:
This is closed by #2162 right?
Sorry, something went wrong.
Closing as fixed by #2162.
No branches or pull requests
Description
When running
cosign generate-key-pair
in a directory where it cannot write to, it results in a panic:Version
1.10.1
The text was updated successfully, but these errors were encountered: