Google Drive backups no longer function

[bucker00]

Since the upgrade all working good, except for Google Drive backup failed when I tried a manual one.
The error was that the p12 key wasn't valid.
I removed and regenerated a new key but get the following response:

The following input errors were detected:

- Invalid P12 key, openssl_pkcs12_read() failed
- Saved settings, but remote backup failed.



Pretty sure this isn't a me problem as all the other settings are unchanged.
Can someone give theirs a go

[Gilad]

Same here  :(

[Roland]

Same here :(

[amichel]

I can confirm the same behavior.

[bucker00]

This has also now been logged as a bug https://github.com/opnsense/core/issues/7184
Thank you for the confirmation folks!

[amichel]

The info in the bugtracker to solve the issue did not work for me, but it pointed me into the right direction:
https://www.practicalnetworking.net/practical-tls/openssl-3-and-legacy-providers/

I modified the /usr/local/openssl/openssl.cnf file

Code Select Expand

[provider_sect]
default = default_sect
legacy = legacy_sect

and

Code Select Expand


[default_sect]
activate = 1
[legacy_sect]
activate = 1

restarted webgui --> Backup worked

[franco]

Since it's patching a template it doesn't work immediately, but a reboot or a reconfiguration of the trust subsystem would do the trick (but I don't know which GUI knob that is from the top of my head).


Cheers,
Franco

[amichel]

Got that franco, thank you for clarification

[Starrbuck]

I modified the /usr/local/openssl/openssl.cnf file

Code Select Expand

[provider_sect]
default = default_sect
legacy = legacy_sect

and

Code Select Expand


[default_sect]
activate = 1
[legacy_sect]
activate = 1

restarted webgui --> Backup worked

This worked for me as well after a reboot.

[bucker00]

Thanks all, muchly appreciated!

[clumsyzombie]

This worked flowless and corrected the issue thank you so much for the information. 

[Melittamann]

Works as described by amichel and Starrbuck. Thank you very much

[adamrc]

Will there be a future patch/update that will be deployed to address this issue for those of us that do not want to manually modify the file referenced above?

[jp0469]

Will there be a future patch/update that will be deployed to address this issue for those of us that do not want to manually modify the file referenced above?

You don't have to manually edit the file. You can just apply the commit from github yourself.

opnsense-patch d8ba131

Or you can wait until the next OPNsense update.

[adamrc]

Will there be a future patch/update that will be deployed to address this issue for those of us that do not want to manually modify the file referenced above?

You don't have to manually edit the file. You can just apply the commit from github yourself.

opnsense-patch d8ba131

Or you can wait until the next OPNsense update.

That worked great! Thanks! I had to reboot for the changes to apply.