blakeblackshear / blakeblackshear/frigate
Ability to disable unauthenticated port when running in host mode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 3.6k
- Avg merge
- 8h 57m
- Merged PRs (30d)
- 118
Description
Using go2rtc with HomeKit cameras requires host networking, but the frigate docs recommend using a docker network since port 5000 is unauthenticated and shouldn't be exposed.
Since I have a HomeKit camera I'd like to use, I think I have two options:
- Use an external instance of go2rtc that is on the host network, but forgo "enhanced live view (full frame rate and audio), two-way talk, and other streaming features".
- Change frigate to the host network, but leave the unauthenticated port 5000 exposed externally.
It sounds like there are no plans to fully support external instances of go2rtc, so that leaves me with exposing port 5000 if I want all the features.
Instead, I would like to be able to disable access via port 5000.
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 by tracing Frigate's handling of the unauthenticated port 5000 when host networking is enabled, using the configuration and server entry points related to port exposure. Determine how access can be disabled without losing the requested host-networked streaming features, and add or update tests showing that port 5000 is inaccessible when disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure, networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100