Investigate possible chassis intrusion detection implementation
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
The KGPE-D16 has chassis intrusion headers on the board, as briefly outlined here: https://github.com/lampmerchant/kgpe-d16/blob/main/w83795g-intrusion.md
We should look into how this can be implemented in heads so that when the alarm is triggered the user is informed of such and an attacker could not reset the alarm without the user knowing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked w83795g-intrusion.md document to understand the KGPE-D16 chassis intrusion headers, then locate the relevant heads firmware entry points. Define completion as informing the user when the alarm is triggered and ensuring an attacker cannot reset it without the user knowing.
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