Proxy configuration and others parameters (security reasons)

Hi, since 1.0, http-proxy parameter is been deleted for security reasons. Have you a new method to add this parameter?

Others parameters are been deleted and are very important for configuration mms-caching, http-caching, no-drop-late-frames, no-skip-frames.

Thanks

• Maybe the method will be to tag "http-proxy" option as safe.
• Most of *-caching options have been tagged, mms might have been forgotten.
• drop-late-frames, skip-frames: not yet tagged as safe.

I can propose a patch to tag them as safe, but does anyone see a security hole in allowing those options for web-plugins?

Untested patch to tag those options as safe. Apply it only if you think they are safe.

Added attachment:

• 0001-Tag-some-options-as-safe.patch

Thanks for your patch.

I think so, http-proxy would be got by a function directly in Internet Explorer configuration. Or it can be safe.

So, if vout-event can be safe, it will good to allow activating all hotkeys and mouse interactions during fullscreen mode (ActiveX).

I hope this patch will be in the next release.

I think vout-event have been tagged as safe, maybe in 1.1.x branch. Not sure it will fix #2691.

It seems quite inappropriate to change the proxy settings from a web page. They should be fetched from MSIE (see #234 (closed)). If I recall whitelisting caching values was also rejected due to adverse effect on memory and bandwidth consumption, and that VLC tends to behave really badly with too low or too high values.

I don't know about drop-late/skip.

added Status::will not fix label

closed