[Ovmsdev] UserTrust/AddTrust/Comodo root CA expiration
shamziman at gmail.com
Tue Jun 2 01:58:40 HKT 2020
I finally got my module in these Covid times (took 2 shipments and almost 3 months) and got it set up for the first time and after I got logged in via ssh, I also got the new certificate installed after a few minutes of orienting myself with the file system commands. It might be worth mentioning that the “trustedca” directory doesn’t actually exist by default. So basically, you need to do:
OVMS# vfs mkdir /store/trustedca
and then from a laptop terminal prompt:
scp -c aes128-cbc usertrust.crt omvs at 192.168.4.1:/store/trustedca/usertrust.crt
I’m not sure if the cipher needs to be specified and the module seemed to need a reboot to read the certificate, but I then finally did get a connection.
There was still some noise from mongoose about SSL, but it didn’t seem to affect the v2 server connection.
Overall, it was pretty easy to setup and much more transparent than my old V2 module. I guess I should start looking at the Volt/Ampere code to see if this pre-heat option is real and app accessible.
(via the iPad thingamajigg)
> On 31 May 2020, at 02:45, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
> The AddTrust root CA certificate that our api.openvehicles.com is signed by has expired (last night). This will impact TLS connections to api.openvehicles.com. Our certificate itself is fine (and doesn’t expire until Feb 2022), but the root cert is was signed by (via intermediaries) has expired.
> Pretty irresponsible for AddTrust/UserTrust/Comodo to sign a certificate with a later expiration date than their own CA, imho. Also irresponsible for them not to inform the customers. Everybody can be expected to monitor their own certificate expiration date, but not that of their certificate authority.
> I’ve been up most of the night dealing with fallout from this (in other work and customer related systems), so not happy.
> Anyway, I’ve updated the trusted root certificate in edge now, and released that. AddTrust has become UserTrust.
> To connect via tls to api.openvehicles.com now, you will either need to firmware update, or manually add the trusted ca to /store/trustedca/usertrust.crt (I have attached it here, for convenience).
> I have also taken this opportunity to change the server v2 and v3 backoff retry times to 60 seconds (was 20 or 30).
> Regards, Mark.
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev