-
-
Notifications
You must be signed in to change notification settings - Fork 4
ucloud: update ports to match new Arduino CA. #94
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
Conversation
Do we also need to update CA data? |
9e8bed1
to
bd04f84
Compare
yes, thanks. Do you know if it's pem or der encoded? |
DER |
I can't connect with openssl s_client -showcerts -connect iot.arduino.cc:8885 </dev/null | openssl x509 -outform PEM > ca-root.pem
mosquitto_sub --cafile ca-root.pem --cert cert.pem --key key.pem -d -h mqtts-sa.iot.arduino.cc -p 8885 -i ${DEVICE_ID} -v --tls-version tlsv1.2 -q 0 -t "/a/d/${DEVICE_ID}/e/i" I got: OpenSSL Error[0]: error:0A000086:SSL routines::certificate verify failed
Error: Protocol error |
since the CA is changed, to restore the CI we have to produce a new cert.pem signed with the new CA (for each device). Github action secrets are write-only, is there any other way we can retrieve their values? |
Does this mean that all provisioned devices will stop working? That sounds bad. |
Actually my device already stopped working already Feb 24 for no obvious reason and can no longer connect to the MQTT broker. note that I got an email from Arduino "Important Security Update Required for Arduino Cloud Devices" I followed all the steps mid February and my device continued working after my changes (and successfully removed the "requires update" icon in the web UI on cloud.arduino.cc under Devices) until it stopped working Feb 24 without me changing anything. It is Arduino RP2040 connect. @rjtokenring I was even giving Arduino classes recommending the IoT cloud but I will stop doing this. Sorry for hi-jacking this PR with my comments but I hope it finds the right audience this way. |
@Bodobolero I missed that email, but I can't access my devices anyway. @mirkokurt @rjtokenring Can you regenerate a device certificate if I send you the device ID and/or API key? Or should I just try to create a new device? |
Please provide device-id, so we can re-sign it. |
mine is |
@Bodobolero That was for me to provide the device id used for the CI. |
The CI test now passes. |
7367aa7
to
d6a1577
Compare
0a46728
to
1ca1252
Compare
1ca1252
to
4ebcd12
Compare
4ebcd12
to
0d3aadf
Compare
@Bodobolero An automatic migration of all device certificates has been made for security reasons. The migration has been applied leveraging the cloud editor for RP2040. I've checked and the certificate of your device has been re-signed and the library version has been updated so your device should be able to connect. If this is not the case as you said, we can investigate. But this is not the right place. Please post in the forum and we will help you. |
Another user failing arduino-libraries/ArduinoIoTCloud#534 |
Due to the switch at broker level, move certificate based authenticates clients to port 8885