Spacenav interactive configuration GUI
 
 
 
Go to file
John Tsiombikas dfad2e2a90 - added a better comment for serial devices in the generated config file
- added -lX11 to LDFLAGS. aparently it's not linked indirectly through gtk on some systems...


git-svn-id: svn+ssh://svn.code.sf.net/p/spacenav/code/trunk/spnavcfg@114 ef983eb1-d774-4af8-acfd-baaf7b16a646
2011-03-07 03:05:37 +00:00
.gitattributes - added new interactive GUI config program for spacenavd 2008-04-07 08:37:52 +00:00
COPYING forgot to add the GPLv3 license text to spnavcfg 2008-04-09 09:05:24 +00:00
Makefile.in - added a better comment for serial devices in the generated config file 2011-03-07 03:05:37 +00:00
README foo 2009-01-30 03:12:54 +00:00
back.c - added swap-yz and separate translation/rotation sensitivity 2010-02-28 02:13:50 +00:00
cfgfile.c - added a better comment for serial devices in the generated config file 2011-03-07 03:05:37 +00:00
cfgfile.h added the new serial option to the config file 2010-06-07 00:58:50 +00:00
cmd.h compatibility with spacenavd 0.3.1 2009-01-30 03:11:59 +00:00
configure - removed init script installation from spacenavd's install target, added 2008-08-14 02:10:34 +00:00
front_gtk.c - the swap axes label showed the wrong axes 2010-02-28 08:55:14 +00:00
spnavcfg.c compatibility with spacenavd 0.3.1 2009-01-30 03:11:59 +00:00

README

spnavcfg 0.2.1
------------

1. About
Spacenav daemon interactive configuration program.

2. Installation
Requires GTK+ 2 and Xlib headers to be installed.
./configure, make, make install, as usual (make install part as root).

3. Security
The binary is installed setuid root in order to be able to modify /etc/spnavrc
and send signals to the daemon. However, it was designed from start to be as
secure as possible. spnavcfg launches two processes (see front.c and back.c).
The frontend that runs all the GUI code drops priviledges to the original uid,
while the backend that does all the gruntwork keeps effective uid root.
As long as you don't run the program while logged in as root, it should be very
secure.

4. Contact
For bug reports, feature requests, or whatever, contact: nuclear@member.fsf.org