crypto - Go Issues

Go Issues Packages

crypto

provide guidance on how to interchange keysDocumentationNeedsDecision

#45726 opened 2 weeks ago by AGWA

0

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

#41689 opened 7 months ago by cespare

1

import fiat-crypto implementationsProposalProposal-AcceptedProposal-Crypto

#40171 opened 10 months ago by mdempsky

51

add WriteByte, WriteString method to hash implementationsProposalProposal-Accepted

#38776 opened 1 year ago by geraldss

22

apply golang.org/wiki/TargetSpecific policyNeedsFix

#31470 opened 2 years ago by FiloSottile

3

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

#31456 opened 2 years ago by vitaminniy

11

add SignContextProposalProposal-Crypto

#28427 opened 2 years ago by x1ddos

3

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

#25882 opened 2 years ago by FiloSottile

7

add facility for key erasureNeedsInvestigationProposal

#21865 opened 3 years ago by zx2c4

100

understand performance differences compared to BoringSSLPerformancehelp wanted

#21525 opened 3 years ago by rsc

4

constant time AES and GCM

#19413 opened 4 years ago by DemiMarie

2

Write power64 versions of assembler routines where applicable

#8913 opened 6 years ago by ianlancetaylor

4

add an easier to use crypto package

#6912 opened 7 years ago by agl

6