From: Maria Guseva <m.guseva-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: "'Michael Kerrisk (man-pages)'"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: 'Yury Gribov' <y.gribov-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
v.garbuzov-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
'Maria Guseva' <m.guseva-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: RE: [patch] ld.so.8: outline missed cases of secure run
Date: Thu, 29 Oct 2015 12:21:34 +0300 [thread overview]
Message-ID: <"000301d1122b$35737db0$a05a7910$@guseva"@samsung.com> (raw)
In-Reply-To:
Ping.
On 09/22/2015 11:58 AM, Maria Guseva wrote:
Hello Michael, Yury
> What do you think of the alternative patch below?
Thank you, the patch you proposed looks much better.
>>> While at it, could you also mention that /etc/suid-debug enables
>>> LD_DEBUG for suids?
>>
>> Does it? I can't see that in the glibc source. Am I missing something?
>I was looking at process_envvars (in rtld.c): it resets dl_debug_mask for
AT_SECURE binaries unless /etc/suid-debug exists.
So I think it should mentioned in LD_DEBUG environment variable description,
here:
.B LD_DEBUG
-is ignored for set-user-ID/set-group-ID binaries.
+is ignored in secure-execution mode.
+However, if the file
+.IR /etc/suid\-debug
+exists (the content of the file is irrelevant), then .BR LD_DEBUG has
+an effect in secure-execution mode.
.TP
Regards,
Maria
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-29 9:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 16:12 [patch] ld.so.8: outline missed cases of secure run Maria Guseva
2015-09-01 7:18 ` Yury Gribov
[not found] ` <55E55162.5080702-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-09-14 18:42 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjgs9rBz8MvgMW1Xts95nBo433RAvoyOZFKuU6cDFO_zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-15 9:13 ` Yury Gribov
2015-09-14 5:37 ` Michael Kerrisk (man-pages)
[not found] ` <55F65D25.1080708-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-22 8:58 ` Maria Guseva
2015-10-29 9:21 ` Maria Guseva [this message]
2015-11-26 9:43 ` [PING][patch] " Maria Guseva
2015-12-04 21:27 ` Michael Kerrisk (man-pages)
[not found] ` <00f601d1282e$e3e04ef0$aba0ecd0$@guseva@samsung.com>
[not found] ` <00f601d1282e$e3e04ef0$aba0ecd0$@guseva-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-11-26 10:25 ` Silvan Jegen
[not found] ` <CAKvUva-pDmq7Cuvh0=Ne+Z+tbTdxO=s5YX6KVa1dUeB=uw5YPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-11-30 16:49 ` Maria Guseva
[not found] ` <565C7E09.4030209-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-12-05 7:33 ` Michael Kerrisk (man-pages)
2015-12-04 21:28 ` Michael Kerrisk (man-pages)
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='"000301d1122b$35737db0$a05a7910$@guseva"@samsung.com' \
--to=m.guseva-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=v.garbuzov-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=y.gribov-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).