|
[Feature Request] Option for overrding presentationUrl in UPNP Device Service XML
|
|
18-07-2023, 09:56
Post: #8
|
|||
|
|||
|
RE: [Feature Request] Option for overrding presentationUrl in UPNP Device Service XML
I think you have misunderstood what presentationURL does. It does nothing except appear in the device.xml document. It doesn't make any difference to how files are served.
Also, there are many ways to change MinimServer properties in addition to using the web UI. They can be changed from MinimWatch, by using the web API (see this section) or by using the mscript command (see this section). My suggestion of having separate ports for serving resources and the web API will not prevent properties from being changed in these ways. What is your deployment scenario for MinimServer? Is it on a network that untrusted users can access? Do you want these untrusted users to be able to access MinimServer for streaming music but not able to change configuration properties? Or are these untrusted users doing other things on the network that don't involve MinimServer? UPnP is by its nature an insecure protocol. When I have been asked about this previously, I have suggested using a separate VLAN or subnet for MinimServer. I think this is the only way to make MinimServer secure from untrusted users on the network. Would this be a possible solution in your situation? |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



