-
Notifications
You must be signed in to change notification settings - Fork 699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cert export (.p12) corrupted #7251
Comments
not likely corrupted, format has changed due to openssl changing to version 3 (
|
You're right, it was in the release notes - I hadn't thought about it. I have now tried to convert the certificate into a .pem file. But this does not work either. I see that the problem is not on the OPNsense side, so you can close the issue. I have to do my research. |
I'm not 100% sure, but expect something like:
|
Thank you, this looked very promising. I now had a .p12 file that could also be opened via the GUI. However, the Wlan authentication still does not work. Maybe it is also related to Linux Mint. Previously I only had Fedora, popOS and Android clients. So it could also be related to Linux Mint. I will try again on another client when I get the chance. I always have the following errors in the FreeRADIUS log:
|
Ok, it looks like it's a Linux Mint problem. I have no problems on another Linux OS with the same certificate. also without converting the certificate - so directly the .p12 file from the OPNsense. Many thanks for your help. |
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
The certificates issued by a CA on the OPNsense can no longer be exported in .p12 format. The files are corrupt after the download and cannot be opened or imported.
This was definitely functioning with version 23.7
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A working .p12 File that i can use.
Describe alternatives you considered
export user cert and key file separately
Environment
OPNsense 24.1.1 (amd64).
DEC840
The text was updated successfully, but these errors were encountered: