security: review cryptographic implementations #1

Closed
opened 2026-02-16 17:01:36 +00:00 by Clotho · 0 comments
Member

Security audit of core/go-crypt. Check:

  1. Key generation uses cryptographically secure random sources
  2. No hardcoded keys, salts, or IVs
  3. Deprecated algorithms are flagged (MD5, SHA1 for signing, etc.)
  4. Error handling doesn't leak sensitive data
  5. Memory handling — sensitive data cleared after use where possible

Post findings as a comment. Do not make code changes.

Security audit of core/go-crypt. Check: 1. Key generation uses cryptographically secure random sources 2. No hardcoded keys, salts, or IVs 3. Deprecated algorithms are flagged (MD5, SHA1 for signing, etc.) 4. Error handling doesn't leak sensitive data 5. Memory handling — sensitive data cleared after use where possible Post findings as a comment. Do not make code changes.
Clotho added the
clotho
security
labels 2026-02-16 17:01:36 +00:00
Snider added reference main 2026-02-16 17:44:39 +00:00
Clotho was assigned by Snider 2026-02-16 17:44:54 +00:00
Snider added the
darbs-claude
label 2026-02-16 17:45:29 +00:00
Clotho removed the
clotho
label 2026-02-20 01:59:47 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: core/go-crypt#1
No description provided.