luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-25 23:16:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

Clarify g_spawn_*() behaviour without full path

Browse Source 
Document the previously uncovered case of calling g_spawn_async_with_pipes()
without a full path but no G_SPAWN_SEARCH_PATH. This runs programs from the
current directory, which might be unexpected and even dangerous in some corner
cases.

https://bugzilla.gnome.org/show_bug.cgi?id=656621
This commit is contained in:
Martin Pitt 2011-08-17 08:57:15 +02:00 committed by Matthias Clasen
parent 8ff94df632
commit 1435db48ba
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
glib/gspawn.c
View File

@ -482,6 +482,10 @@ g_spawn_sync (const gchar *working_directory,
* course the name of the program to execute. By default, the name of * course the name of the program to execute. By default, the name of
* the program must be a full path; the <envar>PATH</envar> shell variable * the program must be a full path; the <envar>PATH</envar> shell variable
* will only be searched if you pass the %G_SPAWN_SEARCH_PATH flag. * will only be searched if you pass the %G_SPAWN_SEARCH_PATH flag.
* If the program name is not a full path and %G_SPAWN_SEARCH_PATH flag is not
* used, then the program will be run from the current directory (or
* %working_directory, if specified); this might be unexpected or even
* dangerous in some cases when the current directory is world-writable.
* *
* On Windows, note that all the string or string vector arguments to * On Windows, note that all the string or string vector arguments to
* this function and the other g_spawn*() functions are in UTF-8, the * this function and the other g_spawn*() functions are in UTF-8, the