Skip to content
This repository has been archived by the owner on Nov 16, 2021. It is now read-only.

bip32/nem: IV is copied before encryption #140

Merged
merged 1 commit into from
Apr 3, 2018
Merged

Conversation

tsusanka
Copy link
Contributor

@saleemrashid
Copy link
Contributor

I don't think we'll ever need to encrypt the data in multiple calls, so this is probably fine 👍

@prusnak prusnak merged commit 877998f into master Apr 3, 2018
@prusnak prusnak deleted the tsusanka/nem-encrypt-iv branch April 3, 2018 16:29
tsusanka added a commit to trezor/trezor-mcu that referenced this pull request Apr 4, 2018
The IV copy was moved to trezor-crypto
(trezor/trezor-crypto#140) so it is not needed
anymore in trezor-mcu
tsusanka added a commit to trezor/trezor-mcu that referenced this pull request Apr 4, 2018
The IV copy was moved to trezor-crypto
(trezor/trezor-crypto#140) so it is not needed
in trezor-mcu anymore
tsusanka added a commit to trezor/trezor-mcu that referenced this pull request Apr 4, 2018
The IV copy was moved to trezor-crypto
(trezor/trezor-crypto#140) so it is not needed
in trezor-mcu anymore
prusnak pushed a commit to trezor/trezor-mcu that referenced this pull request Apr 4, 2018
The IV copy was moved to trezor-crypto
(trezor/trezor-crypto#140) so it is not needed
in trezor-mcu anymore
jcrona pushed a commit to archos-safe-t/safe-t-mcu that referenced this pull request Jul 17, 2018
The IV copy was moved to trezor-crypto
(trezor/trezor-crypto#140) so it is not needed
in trezor-mcu anymore
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants