profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/zosocanuck/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

zosocanuck/OCR-Tools 1

OCR tests

zosocanuck/acme 0

A simple ACME command line tool without 3rd party deps!

zosocanuck/acme4j 0

Java client for ACME (Let's Encrypt)

zosocanuck/botkit-template 0

Botkit template for Webex Teams

zosocanuck/boulder 0

An ACME-based CA, written in Go.

zosocanuck/cert-manager 0

Automatically provision TLS certificates for Kubernetes

zosocanuck/certbot 0

Certbot, previously the Let's Encrypt Client, is EFF's tool to obtain certs from Let's Encrypt, and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.

zosocanuck/cosign 0

Container Signing

zosocanuck/crypto11 0

Implement crypto.Signer and crypto.Decrypter for HSM-protected keys via PKCS#11

release zosocanuck/crypto11

v1.2.5

released time in 8 days

created tagzosocanuck/crypto11

tagv1.2.5

Implement crypto.Signer and crypto.Decrypter for HSM-protected keys via PKCS#11

created time in 8 days

push eventzosocanuck/sigstore

Ivan Wallis

commit sha 624bbc4ccd2ae4b2bf7de4dc96c19bc37793c74a

Update go.mod

view details

push time in 8 days

release zosocanuck/crypto11

v1.2.4

released time in 8 days

push eventzosocanuck/crypto11

Ivan Wallis

commit sha c89814715ff37303b77e687427a47c78316b5821

Update go.mod

view details

push time in 8 days

push eventzosocanuck/sigstore

Ivan Wallis

commit sha 67fed239c2f8746c98526f00ae3ad6a05b14ee73

Update go.mod

view details

push time in 8 days

push eventzosocanuck/sigstore

Ivan Wallis

commit sha e6f8ef8baf5baa5f75521a31437c204d6c68f4b1

Update go.mod

view details

push time in 8 days

push eventzosocanuck/sigstore

Ivan Wallis

commit sha a2c3c67589f511d8f4ecec49354b4b00d17ec6e7

Update go.mod

view details

push time in 8 days

push eventzosocanuck/sigstore

Ivan Wallis

commit sha 053bd792f5c27bda599fa355d6f27e81657af677

Update go.mod

view details

push time in 8 days

push eventzosocanuck/sigstore

Ivan Wallis

commit sha d5f5090f202e974a58b4caaa8a6e5ffa2d62585a

Update go.mod

view details

push time in 8 days

push eventzosocanuck/sigstore

Ivan Wallis

commit sha ed5dd48ffcaee5e7bd6e602b382019337a351f79

Update kms.go

view details

push time in 8 days

push eventzosocanuck/sigstore

Ivan Wallis

commit sha da6efefb1ed8e7694274cd7d6184beee6af65cd6

Create signer.go

view details

push time in 8 days

push eventzosocanuck/sigstore

Ivan Wallis

commit sha 575b79e0c77249935ed9f2c50a2f00326fc8dda4

Create client.go

view details

push time in 8 days

push eventzosocanuck/crypto11

Ivan Wallis

commit sha 33333ba8fbd9f35c78aef5c82c11492c7499bf94

Venafi P11 compatibility for cosign.

view details

push time in 8 days

fork zosocanuck/crypto11

Implement crypto.Signer and crypto.Decrypter for HSM-protected keys via PKCS#11

fork in 8 days

push eventzosocanuck/cosign

Ivan Wallis

commit sha 95ce5c723435dbef453715cd13a4e61f6b8a4b91

Update keys.go

view details

push time in 8 days

push eventzosocanuck/cosign

Ivan Wallis

commit sha cc3a6509ed1bd3b44e1ee56e8456e92dc1f5ad40

Update util.go

view details

push time in 8 days

push eventzosocanuck/sigstore

Ivan Wallis

commit sha 6168dd8b8c494d1e6234fbb60edfe1fa05114cb3

initial commit

view details

push time in 10 days

fork zosocanuck/sigstore

Common library shared across sigstore services

fork in 10 days

fork zosocanuck/cosign

Container Signing

fork in 11 days

issue closedsigstore/cosign

Signing with 3rd party tool

Hi,

I'm attempting to sign with another tool and using the output of:

cosign generate xxx/yyyto produce the JSON payload.

Shoud I be sending the entire payload for signature?

If so I then attach the signature using:

cosign attach signature -signature xyz xxx/yyy

The end result is when I attempt to verify I get:

error: no matching signatures:
failed to verify signature
 failed to verify signature
 failed to verify signature
 failed to verify signature
 failed to verify signature

cosign version is v1.0.0

closed time in a month

zosocanuck

issue commentsigstore/cosign

Signing with 3rd party tool

Yes, this was helpful. Closing this issue for now as I need to investigate why a 3rd party utility is not producing compatible signatures.

zosocanuck

comment created time in a month

issue commentsigstore/cosign

Signing with 3rd party tool

Yes, I'm using a commercial tool to sign and verify successfully.

zosocanuck

comment created time in a month

issue commentsigstore/cosign

Signing with 3rd party tool

I'm using a REST API to sign payloads, and the backend system is performing EcdsaSha256 for signatures. I assume cosign verify also does EcdsaSha256?

zosocanuck

comment created time in a month

issue openedsigstore/cosign

Description of the issue

Hi,

I'm attempting to sign with another tool and using the output of:

cosign generate xxx/yyyto produce the JSON payload.

Shoud I be sending the entire payload for signature?

If so I then attach the signature using:

cosign attach signature -signature xyz xxx/yyy

The end result is when I attempt to verify I get:

error: no matching signatures:
failed to verify signature
 failed to verify signature
 failed to verify signature
 failed to verify signature
 failed to verify signature

cosign version is v1.0.0

created time in a month

startedVenafi/blueprint-securesoftwarepipeline

started time in 2 months

startedsigstore/cosign

started time in 2 months