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

Additional parameters to use in DEM? #43

Closed
fjarri opened this issue Mar 16, 2021 · 4 comments
Closed

Additional parameters to use in DEM? #43

fjarri opened this issue Mar 16, 2021 · 4 comments
Labels
cryptography Needs attention of someone who knows what they're doing
Milestone

Comments

@fjarri
Copy link
Contributor

fjarri commented Mar 16, 2021

Our implementation of DEM takes additional parameters in several places:

  • HKDF (kdf()) takes salt and info
  • AEAD (DEM) takes aad (additional authenticated data)

We use DEM in two places:

  • to encrypt SecretKey during serialization. We set info there to a predefined tag.
  • to encrypt the plaintext in encrypt() (being added in Interfacing with Python #41). We use the serialized Capsule as aad.

Do we need to use other parameters too in these cases? @cygnusv , @tuxxy

@fjarri fjarri added the cryptography Needs attention of someone who knows what they're doing label Mar 16, 2021
@cygnusv
Copy link
Member

cygnusv commented Apr 7, 2021

Do we need to use other parameters too in these cases?

No, I don't think it's necessary, particularly the salt parameter is not useful for us (we never start with low-entropy input).
I guess you're asking this because of this line?

let key_bytes = kdf(&key_seed, None, None);

I think that's fine.

BTW, a side note:

to encrypt SecretKey during serialization

I think we can/should remove this from Umbral anyway (@tuxxy wdyt?)

@fjarri
Copy link
Contributor Author

fjarri commented Apr 7, 2021

Ok, so no HKDF info for encrypt() either?

I think we can/should remove this from Umbral anyway

It is currently removed (it was in at some point, but I did remove it after our discussion)

@fjarri fjarri added this to the v0.1.0 milestone Apr 7, 2021
@cygnusv
Copy link
Member

cygnusv commented Apr 12, 2021

Ok, so no HKDF info for encrypt() either?
Yeah, no need.

@fjarri
Copy link
Contributor Author

fjarri commented Apr 12, 2021

Great, I guess I can close it then. TODOs to be removed along with other RFCs in #41

@fjarri fjarri closed this as completed Apr 12, 2021
fjarri added a commit to fjarri/rust-umbral that referenced this issue Apr 13, 2021
fjarri added a commit to fjarri/rust-umbral that referenced this issue Apr 22, 2021
fjarri added a commit to fjarri/rust-umbral that referenced this issue Apr 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cryptography Needs attention of someone who knows what they're doing
Projects
None yet
Development

No branches or pull requests

2 participants