I don't like this thread, at all. I don't like the tone used here.
VLC must not be started as root for many reasons, security wise.
VLC hasn't had the same security audits that apache had. Therefore, as we don't want to be blame for those issues, we block the launch of VLC as root.
We are doing the support and this is difficult for us.
If you don't like this policy, then recompile your VLC to match this. If you don't like that this isn't mainline, then help us.
If you have a good reason to start VLC as root, I am all hears.
I have recompiled it and applied the changes. The only issue I have with that now is that VLC is out of my package manager and I won't receive updates, possibly important to security, in a timely fashion unless I manually check.
I'll be honest with you guys. It's a media player. I use it to play video formats that mplayer doesn't support right away and for streaming/dj purposes. I'm not running .m3u's filled with shellcode that'll cause buffer overflows that could potentially leave remote access to my pc even though that wouldn't get past the router firewall, I just want to play a couple of videos.
I appreciate your concern concerning me running my root account. It's a personal machine. I'm not running a server powering the user accounts for hundreds of web hosts, I'm just doing day to day stuff. I happen to dislike using sudo and having to type in my password every 30 minutes or whatever. I make system changes routinely and don't want to get stuck editing a file in the middle of vi only to find out I forgot to sudo it and will have to do that now.
Nobody goes on this machine but me. If a super exploit hits me through VLC, you guys can say I told you so. But so far, two years of running basically any application that I feel like under root has caused me no trouble. I have more than enough backups split across computers in my house to feel safe, and I would keep backing things up regardless if I'm root or a user account.
Would you guys block VLC from working on an administrator account in Windows? That's essentially what I'm doing on my machine. Of course you wouldn't. Basically all of your Window users are on admin accounts, that would be too unpopular. In that situation you could always tell the user to fix the code themselves, but this shouldn't be about only making options known to the knowledgeable. Someone who doesn't understand C code or compiling would be stuck right now in my situation.
At the least, there should be an opt-out for this "feature" short of recompiling the code.