Use case….store private generated keys for SSL Renewals.

A .key file cannot currently be uploaded.

Maybe but really private keys should never leave the machine they were generated on. This is part of why the whole CSR process is a thing.

Agreed in theory. However, the person who buys the SSL Cert is not always the one installing the Cert. If the cert ever needs to be converted to a different format, the private key is needed.

    • MMTC

      • Post #4
      • Edited

      I just zip whatever file types are not allowed and then upload that. Not as convenient but does the job.

      davesmith87 A .key file is a text file so you could rename to .key.txt. Or compress to a zip file as we have had to do forever. I agree, it would be nice if the file picker wasn't so picky.

      Because the key file is text, you could copy and paste into any one of a number of notes fields, however you are tracking the certificate.

      Best practices is a worthy and lofty goal, but doesn't always take into account what has to happen to get the job done.

        14 days later

        Assume most of us are doing zip archive with all the key and cert file, as related item for cert domain, which i think is the best, cause you can also add a pass to the zip, if you wanna add extra layer of security on it.