Created attachment 364692 [details, diff] force listening on user configured address Not sure if I'm filing this under the right product/component, sorry if I'm wrong. net-misc/minidlna always listens on 0.0.0.0 even if the config/cmdline is set to bind to another address. The listener is also parsing HTTP, so it seems like a pretty easy thing to exploit if you aren't aware that this is an issue and there's any vulnerability. I made a small patch which just forces it to use the first configured listen address. I've been using it locally and it seems to work.
I'd suggest to check what upstream think about.
I'd wager the guess this might break support for multiple interfaces. At any rate, there is no direct link to a security issue, reassigning to maintainer.
Did you talk with upstream about it?
