Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Add SRTP application-layer filtering into coturn to stop people trying to use it to relay DNS/QUIC/COAP/whatever #2009

Closed
ara4n opened this issue Mar 15, 2017 · 7 comments

Comments

@ara4n
Copy link
Member

ara4n commented Mar 15, 2017

No description provided.

@ara4n
Copy link
Member Author

ara4n commented Mar 15, 2017

would need to also relay DataChannel traffic too...

@ashpieboop
Copy link

Hi, is there any news on this?

@richvdh
Copy link
Member

richvdh commented Apr 27, 2020

wouldn't this be a coturn feature?

@richvdh richvdh closed this as completed Apr 27, 2020
@richvdh
Copy link
Member

richvdh commented May 19, 2020

wait, coturn doesn't know anything about SRTP or RTP: it's all just TCP or UDP to the turn server. Is this a proposal to try to implement a heuristic to decide what is being transmitted and block the traffic if it doesn't match what is being sent?

@ashpieboop
Copy link

@richvdh I initially thought it was a documentation request to help configure coturn; however given that coturn doesn't do that, I would argue that synapse would benefit from such a feature. Is this possible though?

@richvdh
Copy link
Member

richvdh commented May 19, 2020

the traffic isn't going through synapse, so I don't think so...

@ashpieboop
Copy link

So after all it is coturn "feature request" (would probably need a fork).

For now, I guess admins shouldn't allow calls as guest and probably not as "untrusted" users either. Maybe synapse could have a hardening option that disallows calls for users registered less than X days ago? In my personal case, I'll implement that hardening on my external authentication system.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants