Project

General

Profile

Feature #26460

Add API to download encryption key

Added by Daisuke Imai almost 2 years ago. Updated over 1 year ago.

Status:
Done
Priority:
Critical
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Estimated time:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

Created an encrypted pool should prompt user to backup key immediately.
Please take the following ticket as an reference.
https://bugs.freenas.org/issues/24727

When user clicks "Download Recovery Key" button, user should be able to download encryption key(for example, geli.key).

Associated revisions

Revision a60d8b0a (diff)
Added by Vladimir Vinogradenko almost 2 years ago

feat(middleware): pool.download_encryption_key Ticket: #26460

Revision 9e729fc2 (diff)
Added by Vladimir Vinogradenko almost 2 years ago

feat(middleware): pool.download_encryption_key Ticket: #26460

History

#1 Updated by William Grzybowski almost 2 years ago

  • Assignee changed from William Grzybowski to Vladimir Vinogradenko
  • Target version changed from 11.1-RC1 to 11.2-BETA1

Vladimir, could you take a look at this, please?

#2 Updated by Vladimir Vinogradenko almost 2 years ago

  • Status changed from Unscreened to Needs Developer Review
  • Assignee changed from Vladimir Vinogradenko to William Grzybowski

Done(pool.download_encryption_key(oid))

#3 Updated by Vladimir Vinogradenko almost 2 years ago

  • Status changed from Needs Developer Review to Ready For Release
  • Assignee changed from William Grzybowski to Vladimir Vinogradenko

#4 Updated by Dru Lavigne almost 2 years ago

  • Subject changed from An API to download encryption key to Add API to download encryption key

#5 Avatar?id=13649&size=24x24 Updated by Ben Gadd over 1 year ago

  • Status changed from Ready For Release to Done

#6 Updated by Dru Lavigne over 1 year ago

  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#7 Updated by Dru Lavigne over 1 year ago

  • Status changed from Done to Ready for Testing

#8 Updated by Timothy Moore II over 1 year ago

  • Status changed from Ready for Testing to Passed Testing
  • Severity set to New

#9 Updated by Dru Lavigne over 1 year ago

  • Status changed from Passed Testing to Done
  • Needs QA changed from Yes to No

Also available in: Atom PDF