Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: simon.marchi@ericsson.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Make sure GDB uses a valid shell when starting the inferior and to perform the "shell" command
Date: Fri, 24 Jul 2015 19:17:00 -0000	[thread overview]
Message-ID: <838ua52wmp.fsf@gnu.org> (raw)
In-Reply-To: <87k2tp5q3g.fsf@redhat.com>

> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: GDB Patches <gdb-patches@sourceware.org>
> Date: Fri, 24 Jul 2015 15:10:27 -0400
> 
> > Note that on my Ubuntu 14.04:
> >
> > $ which nologin
> > /usr/sbin/nologin
> 
> /sbin/nologin is probably a symlink to this file, isn't it?  But yeah,
> the check could include /usr/sbin/nologin as well.
> 
> > I think that /bin/false is also commonly specified as the default shell
> > for system users (at least according to my /etc/passwd).
> 
> Indeed.  I will include /bin/false as well.

Since the number of valid shells is much smaller than the number of
non-shell programs, isn't it better to have a database of known shells
than to have a database of non-shells people could be expected to set
SHELL to?


  reply	other threads:[~2015-07-24 19:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 18:20 Sergio Durigan Junior
2015-07-24 18:34 ` Simon Marchi
2015-07-24 19:10   ` Sergio Durigan Junior
2015-07-24 19:17     ` Eli Zaretskii [this message]
2015-07-24 19:29       ` Sergio Durigan Junior
2015-07-24 19:53         ` Eli Zaretskii
2015-07-24 20:09           ` Simon Marchi
2015-07-24 20:20             ` Sergio Durigan Junior
2015-07-25  7:10             ` Eli Zaretskii
2015-07-25 16:30               ` Sergio Durigan Junior
2015-07-25 16:41                 ` Eli Zaretskii
2015-07-25 17:03                   ` Sergio Durigan Junior
2015-07-25 17:30                     ` Eli Zaretskii
2015-07-25 23:46                       ` Sergio Durigan Junior
2015-07-24 20:29           ` Paul_Koning
2015-07-24 20:38             ` Simon Marchi
2015-07-24 20:51               ` Paul_Koning
2015-07-24 21:36                 ` Matt Rice
2015-07-25  7:20                   ` Eli Zaretskii
     [not found]             ` <87y4i547lk.fsf@redhat.com>
2015-07-25  7:16               ` Eli Zaretskii
2015-07-24 20:18       ` Andreas Schwab
2015-07-25  7:11         ` Eli Zaretskii
2015-07-25  7:54           ` Andreas Schwab
2015-07-25  8:09             ` Eli Zaretskii
2015-07-24 19:54     ` Simon Marchi
2015-07-24 18:43 ` Luis Machado
2015-07-24 19:08   ` Sergio Durigan Junior
2015-07-24 19:15 ` Eli Zaretskii
2015-07-24 20:38 ` [PATCH v2] " Sergio Durigan Junior
2015-07-26  0:14 ` [PATCH v3] " Sergio Durigan Junior
2015-07-26  8:05   ` Doug Evans
2015-07-26 17:03     ` Doug Evans
2015-07-26 19:26     ` Sergio Durigan Junior
2015-07-26 20:48       ` Doug Evans
2015-07-28 23:11         ` Pedro Alves
2015-07-29 19:21           ` Sergio Durigan Junior
2015-07-26 15:04   ` Eli Zaretskii
2015-07-28 19:58 ` [PATCH] Warn the user when $SHELL is invalid Sergio Durigan Junior
2015-07-28 23:12   ` Pedro Alves
2015-07-29 19:22     ` Sergio Durigan Junior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838ua52wmp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.com \
    --cc=simon.marchi@ericsson.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox