esphome / esphome/feature-requests
OTA HMAC support
- Dominant language
- No language data
- Stars
- 450
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the problem you have/What new integration you would like**
HMAC support for HTTP OTA upgrades
**Please describe your use case for this integration and alternatives you've tried:**
I'd like to be able to authenticate the OTA upgrades. Code signing and HTTPS are hard; HMAC is easy enough. Instead of a simple md5 URL, there could be an hmac-md5 URL and the OTA password could be used.
**Additional context**
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the HTTP OTA upgrade implementation and its current MD5 URL handling; the request names no files, tests, or entry points. Clarify the HMAC URL and OTA-password behavior, then establish tests that show authenticated upgrades work and define what happens for invalid credentials.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100