From 81adeb818204cf487eac3c0ad938518cfd5b5115 Mon Sep 17 00:00:00 2001 From: Tyeth Gundry Date: Tue, 7 Jan 2025 16:14:26 +0000 Subject: [PATCH] Update adafruitio_secure_esp8266.ino - mention expiry date --- .../adafruitio_secure_esp8266/adafruitio_secure_esp8266.ino | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/adafruitio_secure_esp8266/adafruitio_secure_esp8266.ino b/examples/adafruitio_secure_esp8266/adafruitio_secure_esp8266.ino index f62ad7a..f386138 100644 --- a/examples/adafruitio_secure_esp8266/adafruitio_secure_esp8266.ino +++ b/examples/adafruitio_secure_esp8266/adafruitio_secure_esp8266.ino @@ -44,7 +44,7 @@ WiFiClientSecure client; Adafruit_MQTT_Client mqtt(&client, AIO_SERVER, AIO_SERVERPORT, AIO_USERNAME, AIO_KEY); // io.adafruit.com SHA1 fingerprint -/* WARNING - This value was last updated on 07/02/24 and may not be up-to-date! +/* WARNING - This value was last updated on 07/02/24 (expires Aug2025) and may not be up-to-date! * If security is a concern for your project, we strongly recommend users impacted by this moving * to ESP32 which has certificate verification by storing root certs and having a * chain-of-trust rather than doing individual certificate fingerprints.