Building full path before executing a GNOME binary.

[Hema Seetharamaiah <hema seetharamaiah wipro com>]

There are instances in GNOME code where a command/binary is executed
without specifying the absolute path.

GNOME ( e.g. : nautilus, gnome-login-check ) commands are being executed
in the code via calls like system(), g_spawn_command_line_sync(), etc.

Since there is a dependency on the PATH variable to locate the binary,
it can be a security concern. 

Is there a way to work around this?

Could we perhaps have a global place ( variable/xml file ) where the
GNOME install paths are available from which the command, complete with
full path, can be constructed and executed?

Regards,
Hema.


Regards,
Hema.

**************************Disclaimer**************************************************    
 
 Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' 
and 'confidential' and intended for use only by the individual or entity to which it is 
addressed. You are notified that any use, copying or dissemination of the information 
contained in the E-MAIL in any manner whatsoever is strictly prohibited.

****************************************************************************************