You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking at the file https://github.com/fonoster/rtpengine/blob/main/.helm/templates/daemonset.yml in the fonoster/rtpengine repo.
I see that the container uses hostNetwork: true. That means it listens on the ports of its host. There is BIND_NG_PORT for the management of the RTPEngine by software like Kamailio. But, as far as I could tell, RTPEngine doesn't use any way to authenticate incoming connections on the NG port. Isn't this a security liability?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm looking at the file
https://github.com/fonoster/rtpengine/blob/main/.helm/templates/daemonset.ymlin thefonoster/rtpenginerepo.I see that the container uses
hostNetwork: true. That means it listens on the ports of its host. There is BIND_NG_PORT for the management of the RTPEngine by software like Kamailio. But, as far as I could tell, RTPEngine doesn't use any way to authenticate incoming connections on the NG port. Isn't this a security liability?Beta Was this translation helpful? Give feedback.
All reactions