luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-01-26 05:56:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch '2289-setuid-docs' into 'main'

Browse Source 
docs: Document that GIO should not be used in privileged processes

Closes #2289

See merge request GNOME/glib!3413
This commit is contained in:
Patrick Griffis 2023-04-29 03:28:10 +00:00
commit f009d8e368
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/reference/glib/programming.xml
View File

@ -61,7 +61,7 @@ support multithreaded applications.
</refsect2>
<refsect2>
<title>Security</title>
<title>Security and setuid use</title>
<para>
When writing code that runs with elevated privileges, it is important
@ -74,8 +74,17 @@ excellent book on this topic,
When it comes to GLib and its associated libraries, GLib and
GObject are generally fine to use in code that runs with elevated
privileges; they don't load modules (executable code in shared objects)
or run other programs 'behind your back'. GIO has to be used
carefully in privileged programs, see the <ulink url="http://developer.gnome.org/gio/stable/ch02.html">GIO documentation</ulink> for details.
or run other programs ‘behind your back’. GIO, however, is not designed to be
used in privileged programs, either ones which are spawned by a privileged
process, or ones which are run with a setuid bit set.
</para>
<para>
setuid programs should always reset their environment to contain only
known-safe values before calling into non-trivial libraries such as GIO. This
reduces the risk of an attacker-controlled environment variable being used to
get a privileged GIO process to run arbitrary code via loading a GIO module or
similar.
</para>
</refsect2>