We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Needs a new CA cert for https://api.iternio.com/
GTS CA 1P5
from this page: https://pki.goog/repository/
The text was updated successfully, but these errors were encountered:
Update README.md for new Google CA certificate
db2b851
As noted in iternio#9 and iternio#10, the https://api.iternio.com/ API requires a new certificate to be deployed to the OVMS box. This PR proposes changes to the `README.md` file to describe the deployment of this certificate. Note that I have also removed the old text describing the deployment of the "Baltimore" certificate, as this is included in the default set of certificates on the OVMS box (ref [OVMS source code](https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/tree/fb0bdde7b420a296bdb7066f1e7eaa12ead71b67/vehicle/OVMS.V3/components/ovms_tls/trustedca)). I've confirmed that connectivity to APRB works if I have the Google cert installed and the Baltimore cert removed.
Closing to #11
Sorry, something went wrong.
No branches or pull requests
Needs a new CA cert for https://api.iternio.com/
GTS CA 1P5
from this page:
https://pki.goog/repository/
The text was updated successfully, but these errors were encountered: