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

add support for SUITE B (Encryption) #1408

Open
pki-bot opened this issue Oct 2, 2020 · 5 comments
Open

add support for SUITE B (Encryption) #1408

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

Comments

@pki-bot
Copy link

pki-bot commented Oct 2, 2020

This issue was migrated from Pagure Issue #841. Originally filed by cfu (@cfu) on 2014-01-27 19:59:28:


Current, some of the symmetric keys (e.g. DRM) on the server are defaulted to DES3 with no option of switching to AES. Need to add such support for SUIT B.

@pki-bot pki-bot added this to the FUTURE milestone Oct 2, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from mharmsen (@mharmsen) at 2014-09-18 04:47:43

Proposed Milestone: 10.2.2 (per CS Meeting of 09/17/2014)

@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from mharmsen (@mharmsen) at 2015-02-24 23:37:51

Per 10.2.2 Triage meeting of 02/24/2015: 10.3

@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from cfu (@cfu) at 2017-02-27 14:04:04

Metadata Update from @cfu:

  • Issue assigned to cfu
  • Issue set to the milestone: 10.4

@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from mharmsen (@mharmsen) at 2017-03-30 15:00:09

Per PKI Bug Council of 03/30/2017: FUTURE

@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from mharmsen (@mharmsen) at 2017-03-30 15:00:11

Metadata Update from @mharmsen:

  • Custom field feature adjusted to ''
  • Custom field proposedmilestone adjusted to ''
  • Custom field proposedpriority adjusted to ''
  • Custom field reviewer adjusted to ''
  • Custom field version adjusted to ''
  • Issue close_status updated to: None
  • Issue set to the milestone: FUTURE (was: 10.4)

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

No branches or pull requests

1 participant