+1 from me for this as well. The warning should be there for anyone not realizing that this is dangerous, but having the option to mute that warning for people who know (or think they do) what they're doing makes sense.
My only concern is that if we expect the distribution people to deactivate it, and they don't care, we're are not moving. I'd like to have something that
1) doesn't rely on env variables, cmd line switches, preferences, any other stuff related to the way the software is launched, but works out-of-the-box. It's ok to rely on the package we distribute (Balint's package is not official, but he's a core-, so we're controlling it). If other distributions run "as root" and are based on rpm, we should cover that as well.
2) doesn't bother the users (basically no dialogs).
Surely it has to bother the user in some way, as otherwise there is no point? I'm not advocating the triple chase-the-dialog really, really confirm type of dialog, but I do think it should be front and centre.
--