Project

General

Profile

Actions

Feature #8490

closed

pfSense-pkg-acme: acme_certificates_edit.php - Add ability to specify (vs generate) private key

Added by Scott Smith almost 6 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
ACME
Target version:
-
Start date:
04/28/2018
Due date:
% Done:

0%

Estimated time:
24.00 h
Plus Target Version:

Description

I was unable to find a bug/issue/etc on this specific topic, so I'm submitting it as a Feature request.

When a user adds a certificate definition on the Services>Acme>Certificates page, the Key Size drop-down offers five options for generating a private key. I already have a private key, and I'd like to use it to configure pfSense to manage my certificate via letsencrypt.org

UI:

  • Modify the UI on the acme_certificates_edit.php page, adding a Custom... option to the end of the Key Size list.
  • Selecting Custom... would show a (previously hidden) Private Key edit field beneath the drop-down.
  • Selecting any other Key Size would hide the Private Key edit field again.
  • If visible, Private Key would be a required field.

Implementation:

  • Like other user-entered data, the user-entered Private Key text would be stored in the configuration.
  • The private-key-generation logic in acme.sh will be skipped if a private key was provided (specific details on this are TBD).
Actions #1

Updated by Michael M almost 6 years ago

Scott Smith wrote:

  • Like other user-entered data, the user-entered Private Key text would be stored in the configuration.
  • The private-key-generation logic in acme.sh will be skipped if a private key was provided (specific details on this are TBD).

Hey, that's a feature I would really love to see, I recently switched to LE and have a huge issue with this because I use HPKP on other websites on the same domain as my pfsense and I want a static private key to add it to the HPKP header. If I can generate it in pfsense that would be nice, but is not necessary.

Actions #3

Updated by Jim Pingle almost 6 years ago

  • Target version deleted (2.4.4)
Actions #4

Updated by Jim Pingle over 5 years ago

  • Status changed from New to Feedback

PR was merged back in May

Actions #5

Updated by Jim Pingle almost 5 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF