Skip to content

Add a Go envelope package tested against the shared vectors - #30

Merged
GoDeskio merged 1 commit into
mainfrom
cursor/go-envelope-fa6f
Nov 14, 2026
Merged

GoDeskio merged 1 commit into
mainfrom
cursor/go-envelope-fa6f

Conversation

@GoDeskio

Copy link
Copy Markdown
Owner

Summary

bindings/go is a Go package RailYard, Portkyl, and GitGoat can import. It is wire-compatible with the Rust and Python envelope.

  • Default writer is version 3: XChaCha20-Poly1305 plus a 32-byte key commitment.
  • Decrypts version 2 (XChaCha20-Poly1305) and legacy version 1 (AES-256-GCM).
  • HKDF-SHA256 separates keys by kid, purpose, tenant, and algorithm.
  • Argon2id uses the same production parameters as Rust and Python (m = 256 MiB, t = 3, p = 1). Tests use reduced parameters and known answers shared with the Node package.
  • Rewrap decrypts any supported blob and writes version 3 under the current key id.
  • Primitives are golang.org/x/crypto (XChaCha20-Poly1305, HKDF, Argon2id) and the Go standard library for AES-GCM. No other crypto library.

Module path: github.com/GoDeskio/Encryptoglyph/bindings/go.

Local tests

Go 1.22.2 with the toolchain it selected for golang.org/x/crypto v0.31.0, from bindings/go:

go test -count=1 -v
--- PASS: TestSharedVectorsDecrypt
--- PASS: TestV3KnownAnswerReseal
--- PASS: TestBlindIndexVector
--- PASS: TestRoundTripRewrapAndDowngrade
--- PASS: TestTamperWrongContextWrongKey
--- PASS: TestRotation
--- PASS: TestArgon2MatchesNodeAndXCrypto
--- PASS: TestHKDFSeparation
PASS
ok  	github.com/GoDeskio/Encryptoglyph/bindings/go	0.002s

8 tests, 8 passed, 0 failed. go vet ./... exited 0.

The shared-vector test decrypts testvectors/envelope.json v1, v2, and v3, and the known-answer test reseals v3 with the vector nonce. The blind index matches blind_index_hex.

GitHub Actions is budget-blocked. A failure that only says the Actions budget is not a failure of this package.

Open in Web Open in Cursor 

bindings/go seals and opens the shared v1, v2, and v3 vectors with
XChaCha20-Poly1305, HKDF-SHA256, and Argon2id from golang.org/x/crypto.
Rewrap writes a version-3 blob.

Co-authored-by: Admin <GoDeskio@users.noreply.github.com>
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedgolang/​golang.org/​x/​crypto@​v0.31.07325100100100

View full report

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Priority Alert  (click "▶" to expand/collapse) Action
Critical priority
Critical CVE: golang golang.org/x/crypto doesn't drop invoking agent constraints when forwarding keys

CVE: GHSA-f5wc-c3c7-36mc golang.org/x/crypto doesn't drop invoking agent constraints when forwarding keys (CRITICAL)

Affected versions: < 0.52.0

Patched version: 0.52.0

From: bindings/go/go.mod → golang/golang.org/x/crypto@v0.31.0

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/golang.org/x/crypto@v0.31.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: golang golang.org/x/crypto doesn't enforce invoking key constraints

CVE: GHSA-jppx-rxg9-jmrx golang.org/x/crypto doesn't enforce invoking key constraints (CRITICAL)

Affected versions: < 0.52.0

Patched version: 0.52.0

From: bindings/go/go.mod → golang/golang.org/x/crypto@v0.31.0

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/golang.org/x/crypto@v0.31.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: golang golang.org/x/crypto: Invoking VerifiedPublicKeyCallback permissions skip enforcement

CVE: GHSA-x527-x647-q7gg golang.org/x/crypto: Invoking VerifiedPublicKeyCallback permissions skip enforcement (CRITICAL)

Affected versions: < 0.52.0

Patched version: 0.52.0

From: bindings/go/go.mod → golang/golang.org/x/crypto@v0.31.0

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/golang.org/x/crypto@v0.31.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: golang golang.org/x/crypto vulnerable to auth bypass via unenforced @Revoked status

CVE: GHSA-5cgq-3rg8-m6cv golang.org/x/crypto vulnerable to auth bypass via unenforced @revoked status (CRITICAL)

Affected versions: < 0.52.0

Patched version: 0.52.0

From: bindings/go/go.mod → golang/golang.org/x/crypto@v0.31.0

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/golang.org/x/crypto@v0.31.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: golang golang.org/x/crypto vulnerable to infinite loop on large channel writes

CVE: GHSA-rm3j-f69w-wqmq golang.org/x/crypto vulnerable to infinite loop on large channel writes (CRITICAL)

Affected versions: < 0.52.0

Patched version: 0.52.0

From: bindings/go/go.mod → golang/golang.org/x/crypto@v0.31.0

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/golang.org/x/crypto@v0.31.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: golang golang.org/x/crypto: FIDO/U2F security key physical presence check can be bypassed

CVE: GHSA-89gr-r52h-f8rx golang.org/x/crypto: FIDO/U2F security key physical presence check can be bypassed (CRITICAL)

Affected versions: < 0.52.0

Patched version: 0.52.0

From: bindings/go/go.mod → golang/golang.org/x/crypto@v0.31.0

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/golang.org/x/crypto@v0.31.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn
Critical priority
Critical CVE: golang golang.org/x/crypto: Invoking client can cause server deadlock on unexpected responses

CVE: GHSA-vgwf-h737-ff37 golang.org/x/crypto: Invoking client can cause server deadlock on unexpected responses (CRITICAL)

Affected versions: < 0.52.0

Patched version: 0.52.0

From: bindings/go/go.mod → golang/golang.org/x/crypto@v0.31.0

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/golang.org/x/crypto@v0.31.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn

View full report

@GoDeskio
GoDeskio merged commit 3861a70 into main Nov 14, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants