<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi,<div><br></div><div>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:</div><div><br></div><div>OVMS# vfs mkdir /store/trustedca </div><div><br></div><div>and then from a laptop terminal prompt:</div><div>scp -c aes128-cbc usertrust.crt omvs@192.168.4.1:/store/trustedca/usertrust.crt </div><div><br></div><div>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.</div><div><br></div><div>There was still some noise from mongoose about SSL, but it didn’t seem to affect the v2 server connection.</div><div><br></div><div>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.</div><div><br><div dir="ltr">Yada, yada,<div>Shaun</div><div>(via the iPad thingamajigg)</div></div><div dir="ltr"><br><blockquote type="cite">On 31 May 2020, at 02:45, Mark Webb-Johnson <mark@webb-johnson.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div class=""><br class=""></div><div class="">The AddTrust root CA certificate that our <a href="http://api.openvehicles.com" class="">api.openvehicles.com</a> is signed by has expired (last night). This will impact TLS connections to <a href="http://api.openvehicles.com" class="">api.openvehicles.com</a>. Our certificate itself is fine (and doesn’t expire until Feb 2022), but the root cert is was signed by (via intermediaries) has expired.</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">I’ve been up most of the night dealing with fallout from this (in other work and customer related systems), so not happy.</div><div class=""><br class=""></div><div class="">Anyway, I’ve updated the trusted root certificate in edge now, and released that. AddTrust has become UserTrust.</div><div class=""><br class=""></div><div class="">To connect via tls to <a href="http://api.openvehicles.com" class="">api.openvehicles.com</a> 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).</div><div class=""><br class=""></div><div class="">I have also taken this opportunity to change the server v2 and v3 backoff retry times to 60 seconds (was 20 or 30).</div><div class=""><br class=""></div><div class="">Regards, Mark.</div><div class=""><br class=""></div><div class=""></div><div><usertrust.crt></div><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><div class=""></div><span>_______________________________________________</span><br><span>OvmsDev mailing list</span><br><span>OvmsDev@lists.openvehicles.com</span><br><span>http://lists.openvehicles.com/mailman/listinfo/ovmsdev</span><br></div></blockquote></div></body></html>