On 7/26/10 6:54 PM, Antoine Martin wrote: > As someone said, you can bypass the restrictions by downloading other > Xvnc binaries for your platform of choice. (see rpmfind and others) > So the restriction is just an illusion of "security", and I worry that > people may start relying on it. > Not to mention that these "other" binaries might be much worse too. > > If sysadmins really want to secure their system, then they are going to > have to do it properly. Not a bad thing IMO.
Antoine, you're arguing theoreticals. What I'm telling you is that, in a corporate environment, this does not occur. We have people actively and successfully using the security extensions to TurboVNC. Yes, it requires additional administrative policies. The idea is not to make it hack-proof. The idea is to make it so that a user will not be able to casually expose a VNC password. If they've downloaded a custom binary, then they know that they are violating the policy, but honestly, people who have real work to do don't engage in such pursuits. Anyhow, why don't you humor me? If you think the feature is useless, then why do you care if I add it? I am not the only one who uses this method of securing VNC, nor did I invent it. ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
