crypto - Go Issues

Go Issues Packages

crypto

Many APIs return errors caused by other errors, without allowing unwrappingNeedsInvestigation

#58365 opened 2 days ago by dcormier

2

add ContextSigner and use in crypto/tlsProposalProposal-AcceptedProposal-Crypto

#56508 opened 3 months ago by rittneje

25

boringcrypto NewGCMTLS no longer accessibleNeedsInvestigation

#56326 opened 3 months ago by wadey

3

boringcrypto cgo pointer failuresNeedsInvestigation

#55318 opened 4 months ago by gopherbot

3

set Data Independent Timing flag on arm64NeedsDecisionSecurityarch-arm64

#49702 opened 1 year ago by FiloSottile

4

provide guidance on how to interchange keysDocumentationNeedsDecision

#45726 opened 2 years ago by AGWA

2

document that the GCM AEADs are safe for concurrent use if the underlying cipher.Block isDocumentationNeedsFix

#41689 opened 2 years ago by cespare

1

import fiat-crypto implementationsProposalProposal-AcceptedProposal-Crypto

#40171 opened 2 years ago by mdempsky

76

add WriteByte, WriteString method to hash implementationsProposalProposal-Accepted

#38776 opened 2 years ago by geraldss

23

apply golang.org/wiki/TargetSpecific policyNeedsFix

#31470 opened 3 years ago by FiloSottile

3

use math.bits rotate functions instead of ad-hoc implementationsNeedsInvestigation

#31456 opened 3 years ago by vitaminniy

17

document which cipher.Block implementations are safe for concurrent useDocumentationNeedsFixhelp wanted

#25882 opened 4 years ago by FiloSottile

7

understand performance differences compared to BoringSSLPerformancehelp wanted

#21525 opened 5 years ago by rsc

7

constant time AES and GCM

#19413 opened 6 years ago by DemiMarie

2

Write power64 versions of assembler routines where applicable

#8913 opened 8 years ago by ianlancetaylor

4

add an easier to use crypto package

#6912 opened 9 years ago by agl

6