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

stack.yaml: Completely disable RDRAND support in cryptonite #2115

Merged
merged 1 commit into from
Sep 8, 2020

Conversation

rvl
Copy link
Contributor

@rvl rvl commented Sep 7, 2020

Issue Number

Relates to ADP-428.

Overview

Ensures that RDRAND can never be the sole source of RNG entropy.

To generate mnemonics it goes through cryptonite Crypto.Random.Entropy.getEntropy. Disabling the RDRAND backend will leave just the WinCryptoAPI (windows) and DevRandom, DevURandom backends (not windows).

@rvl rvl added the IMPROVEMENT Mark a PR as an improvement, for auto-generated CHANGELOG label Sep 7, 2020
@rvl rvl self-assigned this Sep 7, 2020
@KtorZ
Copy link
Member

KtorZ commented Sep 7, 2020

Ja. Damn AMD CPUs...

@rvl
Copy link
Contributor Author

rvl commented Sep 7, 2020

bors r+

iohk-bors bot added a commit that referenced this pull request Sep 7, 2020
2100: cardano-node: 1.19.0 -> 1.19.1 r=rvl a=rvl

### Issue Number

None

### Overview

- Updates cardano-node to [1.19.1](https://github.com/input-output-hk/cardano-node/releases/tag/1.19.1)
- Back to a URL snapshot - hopefully prevents stack snapshot caching issues.
- Completely disable RDRAND in cryptonite using a cabal flag.

### Comments

- Needs input-output-hk/cardano-haskell#26 merged first.


2115: stack.yaml: Completely disable RDRAND support in cryptonite r=rvl a=rvl

### Issue Number

Relates to ADP-428.

### Overview

Ensures that RDRAND can never be the sole source of RNG entropy.

To generate mnemonics it goes through cryptonite `Crypto.Random.Entropy.getEntropy`. Disabling the RDRAND backend will leave just the WinCryptoAPI (windows) and DevRandom, DevURandom backends (not windows).


Co-authored-by: Rodney Lorrimar <[email protected]>
Co-authored-by: IOHK <[email protected]>
@iohk-bors
Copy link
Contributor

iohk-bors bot commented Sep 8, 2020

This PR was included in a batch that was canceled, it will be automatically retried

@rvl rvl force-pushed the rvl/adp-428/disable-rdrand branch from 989539b to dc160c6 Compare September 8, 2020 00:05
@iohk-bors
Copy link
Contributor

iohk-bors bot commented Sep 8, 2020

Canceled.

@rvl
Copy link
Contributor Author

rvl commented Sep 8, 2020

bors r+

iohk-bors bot added a commit that referenced this pull request Sep 8, 2020
2100: cardano-node: 1.19.0 -> 1.19.1 r=rvl a=rvl

### Issue Number

None

### Overview

- Updates cardano-node to [1.19.1](https://github.com/input-output-hk/cardano-node/releases/tag/1.19.1)
- Back to a URL snapshot - hopefully prevents stack snapshot caching issues.
- Completely disable RDRAND in cryptonite using a cabal flag.

### Comments

- Needs input-output-hk/cardano-haskell#26 merged first.


2115: stack.yaml: Completely disable RDRAND support in cryptonite r=rvl a=rvl

### Issue Number

Relates to ADP-428.

### Overview

Ensures that RDRAND can never be the sole source of RNG entropy.

To generate mnemonics it goes through cryptonite `Crypto.Random.Entropy.getEntropy`. Disabling the RDRAND backend will leave just the WinCryptoAPI (windows) and DevRandom, DevURandom backends (not windows).


Co-authored-by: Rodney Lorrimar <[email protected]>
@iohk-bors
Copy link
Contributor

iohk-bors bot commented Sep 8, 2020

Build failed (retrying...):

@iohk-bors
Copy link
Contributor

iohk-bors bot commented Sep 8, 2020

Build succeeded:

@iohk-bors iohk-bors bot merged commit b83fcc4 into master Sep 8, 2020
@iohk-bors iohk-bors bot deleted the rvl/adp-428/disable-rdrand branch September 8, 2020 03:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IMPROVEMENT Mark a PR as an improvement, for auto-generated CHANGELOG
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants