[GH-ISSUE #757] Password protected certificate .p12 files #501

New issue

Closed

opened 2026-02-27 15:50:39 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 15:50:39 +03:00

Owner

Originally created by @H4xl0r on GitHub (Feb 23, 2019).
Original GitHub issue: https://github.com/quasar/Quasar/issues/757

Would be nice to import own .p12 certs.

It would work , but he prompts with some PW wrong errors.
(generating randoms at moment)

So when importing , asking for PW.... Or print out PW when generating one.
Help would be nice thanks

Originally created by @H4xl0r on GitHub (Feb 23, 2019). Original GitHub issue: https://github.com/quasar/Quasar/issues/757 Would be nice to import own .p12 certs. It would work , but he prompts with some PW wrong errors. (generating randoms at moment) So when importing , asking for PW.... Or print out PW when generating one. Help would be nice thanks

kerem

2026-02-27 15:50:39 +03:00

closed this issue
added the
improvement
label

kerem commented

2026-02-27 15:50:40 +03:00

Author

Owner

@ndragon798 commented on GitHub (Dec 3, 2019):

Fixed in pull request #789

@ndragon798 commented on GitHub (Dec 3, 2019): Fixed in pull request #789

kerem commented

2026-02-27 15:50:40 +03:00

Author

Owner

@H4xl0r commented on GitHub (Dec 6, 2019):

good job !

@H4xl0r commented on GitHub (Dec 6, 2019): good job !

kerem commented

2026-02-27 15:50:40 +03:00

Author

Owner

@MaxXor commented on GitHub (Mar 12, 2023):

If you have the permissions restrictive enough on the private key (e.g. only letting Quasar user read it) this would probably be good enough. Quasar will have to keep the private key loaded in memory anyway; this might be harder for an attacker to recover, but if they have root access to the box you should consider the key compromised regardless.

I'd recommend locking down permissions on the certificate file and not having a password on it.

@MaxXor commented on GitHub (Mar 12, 2023): If you have the permissions restrictive enough on the private key (e.g. only letting Quasar user read it) this would probably be good enough. Quasar will have to keep the private key loaded in memory anyway; this might be harder for an attacker to recover, but if they have root access to the box you should consider the key compromised regardless. I'd recommend locking down permissions on the certificate file and not having a password on it.