public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arjun.is at lostca dot se" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nss/26233] New: matchpathcon and security_context_t are deprecated by libselinux API
Date: Mon, 13 Jul 2020 13:09:57 +0000 [thread overview]
Message-ID: <bug-26233-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26233
Bug ID: 26233
Summary: matchpathcon and security_context_t are deprecated by
libselinux API
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nss
Assignee: unassigned at sourceware dot org
Reporter: arjun.is at lostca dot se
Target Milestone: ---
Found this while building master into a Fedora Rawhide package:
matchpathcon was deprecated:
https://github.com/SELinuxProject/selinux/commit/c7020954caea
security_context_t was removed from usage:
https://github.com/SELinuxProject/selinux/commit/9eb9c9327563
then deprecated:
https://github.com/SELinuxProject/selinux/commit/7a124ca27581
These are used in nss and nscd and the uses now need to be replaced.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-07-13 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 13:09 arjun.is at lostca dot se [this message]
2020-07-13 13:10 ` [Bug nss/26233] " arjun.is at lostca dot se
2020-07-16 15:25 ` jsegitz at suse dot de
2020-07-21 11:20 ` fweimer at redhat dot com
2020-07-21 11:43 ` glaubitz at physik dot fu-berlin.de
2020-07-21 11:48 ` glaubitz at physik dot fu-berlin.de
2020-07-21 11:52 ` schwab@linux-m68k.org
2020-07-22 21:18 ` arjun.is at lostca dot se
2020-07-23 10:39 ` arjun.is at lostca dot se
2022-09-12 22:28 ` cvs-commit at gcc dot gnu.org
2022-09-12 22:30 ` carlos at redhat dot com
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=bug-26233-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).