From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
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: Sat, 25 Jul 2015 23:46:00 -0000 [thread overview]
Message-ID: <878ua34x89.fsf@redhat.com> (raw)
In-Reply-To: <83380c16wo.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 25 Jul 2015 20:30:47 +0300")
On Saturday, July 25 2015, Eli Zaretskii wrote:
>> From: Sergio Durigan Junior <sergiodj@redhat.com>
>> Cc: simon.marchi@ericsson.com, gdb-patches@sourceware.org
>> Date: Sat, 25 Jul 2015 13:03:12 -0400
>>
>> The new section says:
>>
>> @node Valid Shell
>> @subsection Valid Shell
>>
>> @value{GDBN} considers a @emph{valid shell} a file that:
>>
>> @enumerate
>> @item
>> Exists and can be executed by the user.
>>
>> @item
>> Is not the @file{/sbin/nologin} (or @file{/usr/sbin/nologin}) program.
>>
>> @item
>> Is not the @file{/bin/false} program.
>> @end enumerate
>>
>> If any of those conditions are not met, the specified shell is not
>> used by @value{GDBN}.
>>
>> I do not see any difference from what I said above, but if you think
>> this text can be improved, or that this text is not needed at all, then
>> by all means feel free to ask this.
>
> The use of "valid" seems to imply much broader goals. Your
> description seems to say that "pseudo-shells used to disable logins"
> is a better (though longer) terminology.
>
> Also, I suggest to say "such as the following", so as not to imply
> that this is necessarily an exhaustive list.
OK, I will make these changes and send a v3.
> Finally, is it really OK to lump here the "cannot be executed by the
> user" case? Maybe we should error out in that case.
I don't think we should error out in this case, since we can fallback to
/bin/sh and display a warning (which is what the patch does). Erroring
out seems too much for me.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-07-25 23:46 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
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 [this message]
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=878ua34x89.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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