Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

x/crypto/chacha20: new package #6914

Closed
gopherbot opened this issue Dec 7, 2013 · 7 comments
Closed

x/crypto/chacha20: new package #6914

gopherbot opened this issue Dec 7, 2013 · 7 comments
Labels
FrozenDueToAge
Milestone
Unreleased

Comments

@gopherbot
Copy link

by mischief@offblast.org:

it seems only natural to have chacha20, if we have djb's other crypto suites.

http://cr.yp.to/chacha.html

http://tools.ietf.org/html/draft-agl-tls-chacha20poly1305-01

http://undeadly.org/cgi?action=article&;sid=20131204090217
@minux
Copy link
Member

minux commented Dec 8, 2013

Comment 1:

Labels changed: added release-none, repo-crypto.

@ality
Copy link
Member

ality commented Dec 8, 2013

Comment 2:

This will have to be in the main repo if it's going to be used in TLS.

Labels changed: added repo-main, removed repo-crypto.

@minux
Copy link
Member

minux commented Dec 8, 2013

Comment 3:

i believe it happens at all, it must first be landed in the go.crypto sub-repository
before migrating to the main tree.
besides, poly1305 is still in the go.crypto tree.
I think probably opening up crypto/tls to accept external cipher suite
implementations is the correct way to go (similar to the crypto.Hash interface)

@minux
Copy link
Member

minux commented Dec 20, 2013

Comment 4:

Labels changed: added repo-crypto, removed repo-main.

Status changed to Accepted.

@mikioh mikioh changed the title go.crypto: no chacha20 implementation chacha20: new package Jan 7, 2015
@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@rsc rsc changed the title chacha20: new package x/crypto/chacha20: new package Apr 14, 2015
@rsc rsc modified the milestones: Unreleased, Unplanned Apr 14, 2015
@rsc rsc removed the repo-crypto label Apr 14, 2015
@bardiharborow
Copy link

Is this still on the table?

@mark-kubacki mark-kubacki mentioned this issue Apr 30, 2016
Closed
@Thomasdezeeuw Thomasdezeeuw mentioned this issue Jun 24, 2016
Closed
@leonklingele
Copy link
Contributor

I assume this can be closed?

@bradfitz
Copy link
Contributor

@leonklingele, yup, thanks.

This landed in Go 1.8: https://beta.golang.org/doc/go1.8#crypto_tls

And also in: https://godoc.org/golang.org/x/crypto/chacha20poly1305

@josharian josharian mentioned this issue Mar 6, 2017
Closed
@golang golang locked and limited conversation to collaborators Jan 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
7 participants
@bradfitz @rsc @minux @ality @bardiharborow @leonklingele @gopherbot