★ wanayoo — archive 1999 https://github.com/nodejs/node/pull/25564Nouvelle recherche | Portail wanayoo
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

test: use stronger curves for keygen #25564

Closed
wants to merge 1 commit into from

Conversation

Projects
None yet
4 participants
@danbev
Copy link
Member

commented Jan 18, 2019

This commit updates the named curves P-192 (prime192v1), and secp192k1
to 256 bit versions.

The motivation for this is that in Red Hat Enterprise Linux (RHEL) all
ECC curves < 224 bits are removed from OpenSSL provided by the system.
I'm not sure if other distributions do this but these 256 bit curves are
availalbe in OpenSSL 1.1.0j (current version on master) and OpenSSL
1.1.1 so as far as I can tell it should be safe change to make.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines
@danbev

This comment has been minimized.

Copy link
Member Author

commented Jan 18, 2019

@sam-github
Copy link
Member

left a comment

I know the commit description says test: , but the message sounded to me like it was making a breaking change. Maybe a description like test: use stronger curves for keygen would be more clear?

test: use stronger curves for keygen
This commit updates the named curves P-192 (prime192v1), and secp192k1
to 256 bit versions.

The motivation for this is that in Red Hat Enterprise Linux (RHEL) all
ECC curves < 224 bits are removed from OpenSSL provided by the system.
I'm not sure if other distributions do this but these 256 bit curves are
availalbe in OpenSSL 1.1.0j (current version on master) and OpenSSL
1.1.1 so as far as I can tell it should be safe change to make.

@danbev danbev force-pushed the danbev:test-crypto-keygen-rhel8 branch from ef558fb to 573f8cf Jan 20, 2019

@danbev

This comment has been minimized.

Copy link
Member Author

commented Jan 20, 2019

Maybe a description like test: use stronger curves for keygen would be more clear?

Yeah, that sounds good. I've updated now. Thanks

@danbev danbev changed the title test: update P-192 and secp192k1 to 256 bit test: use stronger curves for keygen Jan 20, 2019

@lpinca

lpinca approved these changes Jan 20, 2019

@danbev

This comment has been minimized.

Copy link
Member Author

commented Jan 21, 2019

Landed in 8b2e861.

@danbev danbev closed this Jan 21, 2019

@danbev danbev deleted the danbev:test-crypto-keygen-rhel8 branch Jan 21, 2019

danbev added a commit that referenced this pull request Jan 21, 2019

test: use stronger curves for keygen
This commit updates the named curves P-192 (prime192v1), and secp192k1
to 256 bit versions.

The motivation for this is that in Red Hat Enterprise Linux (RHEL) all
ECC curves < 224 bits are removed from OpenSSL provided by the system.
I'm not sure if other distributions do this but these 256 bit curves are
availalbe in OpenSSL 1.1.0j (current version on master) and OpenSSL
1.1.1 so as far as I can tell it should be safe change to make.

PR-URL: #25564
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>

addaleax added a commit that referenced this pull request Jan 23, 2019

test: use stronger curves for keygen
This commit updates the named curves P-192 (prime192v1), and secp192k1
to 256 bit versions.

The motivation for this is that in Red Hat Enterprise Linux (RHEL) all
ECC curves < 224 bits are removed from OpenSSL provided by the system.
I'm not sure if other distributions do this but these 256 bit curves are
availalbe in OpenSSL 1.1.0j (current version on master) and OpenSSL
1.1.1 so as far as I can tell it should be safe change to make.

PR-URL: #25564
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>

@MylesBorins MylesBorins referenced this pull request Jan 24, 2019

Merged

v11.8.0 proposal #25687

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.