SELinux-Refpolicy Archive on
 help / color / Atom feed
* Why is /usr/include matched with /usr/inclu.e?
@ 2019-08-21 19:57 Nicolas Iooss
  2019-08-21 20:02 ` Dominick Grift
  0 siblings, 1 reply; 4+ messages in thread
From: Nicolas Iooss @ 2019-08-21 19:57 UTC (permalink / raw)
  To: selinux-refpolicy

Hi all,

While checking the patterns in refpolicy, I stumbled upon the
following line in

/usr/inclu.e(/.*)? gen_context(system_u:object_r:usr_t,s0)

This pattern matches /usr/include and its content, but why is a dot
used? Which other directories can it match?

The issue there is that a dot can match a slash, so the pattern also
matches /usr/inclu/e/, which seems strange. This pattern has been
introduced in the very early days of refpolicy's git repository,
according to
Does anyone remember why the pattern for /usr/include is so special?


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-21 19:57 Why is /usr/include matched with /usr/inclu.e? Nicolas Iooss
2019-08-21 20:02 ` Dominick Grift
2019-08-21 20:29   ` Nicolas Iooss
2019-08-27  4:06     ` Chris PeBenito

SELinux-Refpolicy Archive on

Archives are clonable:
	git clone --mirror selinux-refpolicy/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 selinux-refpolicy selinux-refpolicy/ \
	public-inbox-index selinux-refpolicy

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox