Project

General

Profile

Actions

Feature #8645

closed

Upload certificate file instead of pasting

Added by Adam Thompson over 3 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Very Low
Category:
Certificates
Target version:
Start date:
07/13/2018
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:

Description

When importing a new certificate, currently we have to paste in the ASCII Base64 (PEM) representation of the cert & key.
In many scenarios this data is trivial to obtain, but in others quite difficult. (e.g. all I have is a .p12 file, on Windows - now what?)
It is possible to auto-detect file type and extract the components deterministically on the back end using e.g. openssl, for around 4 or 5 common formats IIRC.

This would be a nice-to-have convenience feature, but obviously not critical since I can do the same steps myself with openssl.

(I learned at BSDCan 2018 that certificates can contain arbitrary data, and thus can be code injection vectors themselves, so I'm no longer prepared to even guess how long this feature would take to implement safely. Which, yes, I get means this won't happen... but if I don't ask, I'll never get.)

Actions #2

Updated by Jim Pingle over 2 years ago

  • Target version set to 2.5.0
Actions #3

Updated by Jim Pingle over 2 years ago

  • Status changed from New to Pull Request Review
Actions #5

Updated by Renato Botelho over 1 year ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

PR has been merged. Thanks!

Actions #6

Updated by Steve Beaver about 1 year ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF