None. If you'll notice, vglgenkey tries to use 'xauth generate' first, but when it fails, it will simply use 'xauth list' and copy the existing display manager xauth key into /etc/opt/VirtualGL/vgl_xauth_key. The use of 'vglconnect -x', which also relies on 'xauth generate', doesn't generally work at all on recent Linux systems because of the lack of the security extension.
Not sure why X Security was abandoned, but it wouldn't surprise me if the developers felt that it wasn't secure enough. The open source community's approach to security is often that, if Option A is not as secure as Option B, Option A is eliminated so as to encourage users to use Option B. The problem, however, is that this often creates a situation in which users who can't use Option B for whatever reason end up using no security at all. More specifically, 'xauth generate' is not as good as 'ssh -X', but it's better than 'xhost +'. A door lock on your car doesn't prevent someone from smashing the window, but the number of people who would be tempted to steal by smashing a window is much less than the number of people who would be tempted to steal by opening a door. On 10/27/11 5:10 AM, Arthur Huillet wrote: > Hello, > > aside from SELinux-related issues which are documented, I seem not to be able > to use "xauth generate" possibly because of the X security extension is not > enabled on RHEL6. > What solution, if any, did you find to this problem? > > Thanks ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
