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

Default key wrap algorithm for archive_encrypted_data() #1719

Closed
pki-bot opened this issue Oct 3, 2020 · 3 comments
Closed

Default key wrap algorithm for archive_encrypted_data() #1719

pki-bot opened this issue Oct 3, 2020 · 3 comments
Milestone

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #1156. Originally filed by edewata (@edewata) on 2014-09-11 20:22:24:


Currently the archive_encrypted_data() method in KeyClient requires the caller to specify the key wrapping algorithm:

nonce_iv = generate_nonce_iv()
algorithm_oid = KeyClient.DES_EDE3_CBC_OID
symkey_params = base64.encodestring(nonce_iv)

key_id = key_client.archive_encrypted_data(
    client_key_id,
    data_type,
    wrapped_private_data,
    wrapped_session_key,
    algorithm_oid,
    symkey_params,
    key_algorithm,
    key_size)

To simplify the API, there should be a default algorithm (e.g. KeyClient.DES_EDE3_CBC_OID) so the caller doesn't have to figure out which algorithm to use unless necessary.

@pki-bot pki-bot added this to the 10.2.1 milestone Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2014-09-24 20:55:51

Per Dogtag 10.2.3 Triage meeting of 09/24/2014 - proposed Milestone: 10.2.1

NOTE: edewata and vakwetu to discuss

@pki-bot pki-bot closed this as completed Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from edewata (@edewata) at 2014-11-25 21:39:55

master: cfeb77b

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from edewata (@edewata) at 2017-02-27 14:01:56

Metadata Update from @edewata:

  • Issue assigned to edewata
  • Issue set to the milestone: 10.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant