Skip to content

Conversation

@dcousens
Copy link
Contributor

In preparation of #394.

@dcousens dcousens added this to the 2.0.0 milestone Jun 23, 2015
@jprichardson
Copy link
Member

It's not clear to me why we would want to do this at this point? Shouldn't we get #394 resolved first and then do this?

@dcousens
Copy link
Contributor Author

@jprichardson the idea is that we can iterate on #394 without worrying about interrupting the public API.

@weilu
Copy link
Contributor

weilu commented Jul 5, 2015

LGTM. Please add deprecation warning on 1.x branch though.

dcousens added a commit that referenced this pull request Jul 7, 2015
@dcousens dcousens merged commit 5ba0c3d into master Jul 7, 2015
@dcousens dcousens deleted the ecdsabreak branch July 7, 2015 00:35
@dcousens
Copy link
Contributor Author

dcousens commented Jul 7, 2015

@jprichardson if you have further concerns with this, please bring them up ASAP.

@dcousens dcousens mentioned this pull request Jul 7, 2015
Closed
@jprichardson
Copy link
Member

The problem is that ECDSA shouldn't have exposed the ECC primitives. (I guess a case could be made for performance) But given that's what we have now, I understand the reasoning behind this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants