This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [doc patch] auto-load: Make more set auto-load safe-path references [Re: [patch#3 5/8] set auto-load safe-path]
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org, Eli Zaretskii <eliz at gnu dot org>
- Date: Wed, 9 May 2012 12:58:22 -0700
- Subject: Re: [doc patch] auto-load: Make more set auto-load safe-path references [Re: [patch#3 5/8] set auto-load safe-path]
- References: <20120403185058.GE14189@host2.jankratochvil.net> <20120509042129.GA24867@adacore.com> <20120509182555.GA16482@host2.jankratochvil.net>
> attached.
Thanks!
> > And lastly, it would have been nice if, after reading the documentation,
> > the user could have had a sense of what policy GDB implements by default.
> > For instance, GDB's default policy is to enable auto-loading of all
> > files, but only from trusted directories specified via the "auto-load
> > safe-path" setting.
>
> There is already that paragraph (in Node: Auto-loading safe path):
>
> Setting this variable to `/' disables this security protection,
> corresponding GDB configuration option is
> `--without-auto-load-safe-path'. This variable is supposed to be set
> to the system directories writable by the system superuser only. Users
> can add their source directories in init files in their home
> directories (*note Home Directory Init File::). See also deprecated
> init file in the current directory (*note Init File in the Current
> Directory during Startup::).
>
> Do you find it insufficient?
I just find it more logical to have it at the beginning, rather than
the end. The way I see it, "set auto-load safe-path" is the first
barrier involved in determining whether to auto-load a file or not.
But I'm fine either way. I think your patch is already a good
improvement as it is.
Thanks, Jan.
--
Joel