All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: Stephen Smalley <stephen.smalley@gmail.com>
Cc: Petr Lautrbach <plautrba@redhat.com>,
	selinux@vger.kernel.org, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [PATCH] libselinux: deprecate security_compute_user(), update man pages
Date: Thu, 27 Feb 2020 17:32:36 +0100	[thread overview]
Message-ID: <pjdlfoo6lej.fsf@redhat.com> (raw)
In-Reply-To: <CAB9W1A2_hSh4j7_KP2Bbi57942yEJO9xy65XxPJxoFdckZRocg@mail.gmail.com>


Stephen Smalley <stephen.smalley@gmail.com> writes:

> On Fri, Feb 21, 2020 at 3:40 AM Petr Lautrbach <plautrba@redhat.com> wrote:
>>
>> From: Stephen Smalley <sds@tycho.nsa.gov>
>>
>> commit 1f89c4e7879fcf6da5d8d1b025dcc03371f30fc9 ("libselinux: Eliminate
>> use of security_compute_user()") eliminated the use of
>> security_compute_user() by get_ordered_context_list().  Deprecate
>> all use of security_compute_user() by updating the headers and man
>> pages and logging a warning message on any calls to it.  Remove
>> the example utility that called the interface. While here, also
>> fix the documentation of correct usage of the user argument to these
>> interfaces.
>>
>> Fixes: https://github.com/SELinuxProject/selinux/issues/70
>> Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
>> Acked-by: Petr Lautrbach <plautrba@redhat.com>
>> ---
>>
>> It looks like the original email didn't get to the mailing list. Therefore
>> I'm resending it for a broader audience.
>
> Can this be merged?

I'm sorry I mis-read
https://lore.kernel.org/selinux/CAFftDdqKkRc5S236+OjXJkfJaHVw8F-1XicHUb2aaxYqZK1QSQ@mail.gmail.com/
and I though that there would be a re-spin, but the mail says that it will
be follow up.

It's merged now. Thanks!


Petr


      reply	other threads:[~2020-02-27 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21  8:38 [PATCH] libselinux: deprecate security_compute_user(), update man pages Petr Lautrbach
     [not found] ` <CAFftDdqzTnhO4ii+r9jweBGMtvwrezi-T1_utoCe-V=v+rfPVA@mail.gmail.com>
     [not found]   ` <2b98a7da-e186-1013-1286-27d751e75536@tycho.nsa.gov>
     [not found]     ` <CAFftDdo_A5KCwj1szdf-JMV5CbCet58sPe2gJ4v9wKCHOd=1KA@mail.gmail.com>
2020-02-24 18:52       ` William Roberts
     [not found]       ` <e5e5f250-8c4e-e80b-f83a-7abe2320adc2@tycho.nsa.gov>
2020-02-24 20:04         ` William Roberts
2020-02-27 16:24 ` Stephen Smalley
2020-02-27 16:32   ` Petr Lautrbach [this message]

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=pjdlfoo6lej.fsf@redhat.com \
    --to=plautrba@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.