From: Martin Orr <martin@martinorr.name>
To: SELinux List <selinux@tycho.nsa.gov>
Cc: Stephen Smalley <sds@tycho.nsa.gov>
Subject: restorecon and symbolic links
Date: Sat, 29 Aug 2009 18:10:30 +0100 [thread overview]
Message-ID: <4A996106.4060604@martinorr.name> (raw)
With policycoreutils 2.0.71, "restorecon /dev/stdin" fails if stdin is a pipe:
martin@caligula:~$ echo hi | sudo restorecon /dev/stdin
realpath(/dev/stdin) failed No such file or directory
Why would you want to do this?
The Debian udev init script does
ln -s /proc/self/fd/0 /dev/stdin
restorecon /dev/stdin
I am not sure why stdin is a pipe here but it is some consequence of the
boot process.
The intention here (and what happened with policycoreutils 2.0.69) is to
relabel the symbolic link. But the recent realpath patch changed this, and
I don't think there is a way now to ask restorecon to relabel an individual
symlink.
--
Martin Orr
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2009-08-29 17:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 17:10 Martin Orr [this message]
2009-08-29 23:19 ` restorecon and symbolic links Manoj Srivastava
2009-08-31 12:17 ` Stephen Smalley
2009-08-31 12:20 ` Stephen Smalley
2009-08-31 13:24 ` Martin Orr
2009-08-31 13:21 ` Martin Orr
2009-08-31 20:27 ` Stephen Smalley
2009-09-01 13:43 ` Martin Orr
2009-09-01 14:34 ` Martin Orr
2009-09-01 14:46 ` Stephen Smalley
2009-09-02 12:24 ` Martin Orr
2009-09-02 12:52 ` Stephen Smalley
2009-09-03 9:47 ` Martin Orr
2009-09-03 15:25 ` Stephen Smalley
2009-09-03 20:17 ` SELinux and SSH Timers ? Hasan Rezaul-CHR010
2009-09-03 20:32 ` Stephen Smalley
2009-09-04 11:49 ` Stephen Smalley
2009-09-04 14:45 ` Hasan Rezaul-CHR010
2009-09-04 14:56 ` Stephen Smalley
2009-09-04 14:55 ` Hasan Rezaul-CHR010
2009-09-04 15:17 ` Hasan Rezaul-CHR010
2009-09-04 16:06 ` Stephen Smalley
2009-09-04 16:15 ` Hasan Rezaul-CHR010
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=4A996106.4060604@martinorr.name \
--to=martin@martinorr.name \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.