-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
API: Exposed for WebRTC without any access control #2684
Copy link
Copy link
Closed
Labels
BugIt might be a bug.It might be a bug.EnglishNativeThis issue is conveyed exclusively in English.This issue is conveyed exclusively in English.WebRTCWebRTC, RTC2RTMP or RTMP2RTC.WebRTC, RTC2RTMP or RTMP2RTC.
Milestone
Description
With WebRTC we need to expose http_api to public.
Why there isn't any access control for http_api?
User can send HTTP to /rtc/v1/play/ - which is OK.
But... there is also /api/v1/streams/ /api/v1/clients/ accessible for everyone in internet...
We need to setup reverse-proxy between client and SRS server?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BugIt might be a bug.It might be a bug.EnglishNativeThis issue is conveyed exclusively in English.This issue is conveyed exclusively in English.WebRTCWebRTC, RTC2RTMP or RTMP2RTC.WebRTC, RTC2RTMP or RTMP2RTC.