unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: DJ Delorie <dj@redhat.com>, libc-alpha@sourceware.org
Subject: Re: nsswitch: do not reload if "/" changes
Date: Mon, 18 Jan 2021 10:59:17 -0500	[thread overview]
Message-ID: <25a79acd-f739-83ec-5dcf-ab2bd771f561@redhat.com> (raw)
In-Reply-To: <xnsg71wvbz.fsf@greed.delorie.com>

On 1/15/21 7:59 PM, DJ Delorie via Libc-alpha wrote:
> 
> [Note: I tried putting this functionality in the file_change_detection
> module, but that didn't have enough persistence.]
> 
> [Note: tested by instrumenting test-container.c and observing the
> instrumentation with test containers on the root fs and on a separate
> fs]
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=27077
> 
> Before reloading nsswitch.conf, verify that the root directory
> hasn't changed - if it has, it's likely that we've entered a
> container and should not trust the nsswitch inside the container
> nor load any shared objects therein.

Can we create a non-test-container test for this?

I think you can use support_become_root to unshare and then try
to use support_chroot_create/support_chroot_free and xhcroot to 
change root, and then try to do an NSS call that will fail?

The test can start by calling __nss_lookup_configure to set
a known module to provide the NSS values, and then do an IdM
call, verify you're using a known value, and then try to
become root and chroot.

I'm not sure if this is possible though.

-- 
Cheers,
Carlos.


  parent reply	other threads:[~2021-01-18 15:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16  0:59 nsswitch: do not reload if "/" changes DJ Delorie via Libc-alpha
2021-01-16 10:52 ` Florian Weimer via Libc-alpha
2021-01-18  1:13   ` DJ Delorie via Libc-alpha
2021-01-18 10:47     ` Florian Weimer via Libc-alpha
2021-01-18 18:20       ` DJ Delorie via Libc-alpha
2021-01-19 16:37         ` Florian Weimer via Libc-alpha
2021-01-22 19:10           ` [v2] " DJ Delorie via Libc-alpha
2021-01-26  9:58             ` Florian Weimer via Libc-alpha
2021-01-26 16:19               ` DJ Delorie via Libc-alpha
2021-01-26 16:30                 ` Florian Weimer via Libc-alpha
2021-01-26 16:47                   ` DJ Delorie via Libc-alpha
2021-01-27 17:28                     ` Carlos O'Donell via Libc-alpha
2021-01-27 18:44                       ` DJ Delorie via Libc-alpha
2021-01-28  0:31                         ` Joseph Myers
2021-01-28  0:34                           ` DJ Delorie via Libc-alpha
2021-01-28  0:39                             ` Joseph Myers
2021-01-28  1:15                               ` DJ Delorie via Libc-alpha
2021-01-18 12:42 ` Andreas Schwab
2021-01-18 12:53   ` Florian Weimer via Libc-alpha
2021-01-18 18:27   ` DJ Delorie via Libc-alpha
2021-01-18 15:59 ` Carlos O'Donell via Libc-alpha [this message]
2021-01-18 16:53   ` Florian Weimer via Libc-alpha
2021-01-19 14:30     ` Carlos O'Donell via Libc-alpha
2021-01-19 14:40       ` Florian Weimer via Libc-alpha
2021-01-18 18:35   ` DJ Delorie via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=25a79acd-f739-83ec-5dcf-ab2bd771f561@redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=dj@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).