Skip to content

Conversation

@stefanmb
Copy link
Contributor

Generating 1024-bit primes on rpi test machines sometimes causes timeouts. We can avoid this situation by using 256-bit primes when not running in FIPS mode.

Resolves#3881.

Generating 1024-bit primes on rpi test machines sometimes causes timeouts. Avoid this situation by using 256-bit primes when not running in FIPS mode.
@mscdexmscdex added test Issues and PRs related to the tests. arm Issues and PRs related to the ARM platform. labels Nov 18, 2015
@cjihrig
Copy link
Contributor

LGTM

@mscdexmscdex added the crypto Issues and PRs related to the crypto subsystem. label Nov 18, 2015
@mscdex
Copy link
Contributor

LGTM

@bnoordhuis
Copy link
Member

@stefanmb
Copy link
ContributorAuthor

I see two unrelated things:
(1) EADDRNOTAVAIL 127.0.0.1:12346 on OS X [1].
(2) test-fs-utimes.js on rpi [2]

@jasnell
Copy link
Member

Landed in da9a89a

@Fishrock123
Copy link
Contributor

Umm, won't this mean the whole CI tests with 256-bit primes now since it doesn't use FIPS?

@stefanmb
Copy link
ContributorAuthor

@Fishrock123 Correct, which is the exact situation we had before my previous commit. Separately, there has been discussion about introducing FIPS builds into CI.

jasnell pushed a commit that referenced this pull request Nov 18, 2015
Generating 1024-bit primes on rpi test machines sometimes causes timeouts. Avoid this situation by using 256-bit primes when not running in FIPS mode. Fixes: #3881 PR-URL: #3902 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Brian White <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
@jasnell
Copy link
Member

Exactly, this reverts the behavior back to where it was before when FIPS is not enabled.

MylesBorins pushed a commit that referenced this pull request Dec 1, 2015
Generating 1024-bit primes on rpi test machines sometimes causes timeouts. Avoid this situation by using 256-bit primes when not running in FIPS mode. PR-URL: #3902 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Brian White <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
rvagg pushed a commit that referenced this pull request Dec 4, 2015
Generating 1024-bit primes on rpi test machines sometimes causes timeouts. Avoid this situation by using 256-bit primes when not running in FIPS mode. PR-URL: #3902 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Brian White <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
rvagg pushed a commit that referenced this pull request Dec 5, 2015
Generating 1024-bit primes on rpi test machines sometimes causes timeouts. Avoid this situation by using 256-bit primes when not running in FIPS mode. Fixes: #3881 PR-URL: #3902 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Brian White <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
@jasnelljasnell mentioned this pull request Dec 17, 2015
jasnell pushed a commit that referenced this pull request Dec 17, 2015
Generating 1024-bit primes on rpi test machines sometimes causes timeouts. Avoid this situation by using 256-bit primes when not running in FIPS mode. PR-URL: #3902 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Brian White <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
jasnell pushed a commit that referenced this pull request Dec 23, 2015
Generating 1024-bit primes on rpi test machines sometimes causes timeouts. Avoid this situation by using 256-bit primes when not running in FIPS mode. PR-URL: #3902 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Brian White <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

armIssues and PRs related to the ARM platform.cryptoIssues and PRs related to the crypto subsystem.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@stefanmb@cjihrig@mscdex@bnoordhuis@jasnell@Fishrock123@MylesBorins