linux-kernel - Re: [PATCH] Smackv10: Smack rules grammar + their stateful parser

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071107150811.517e4c9a@the-village.bc.nu>
Date:	Wed, 7 Nov 2007 15:08:11 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Ahmed S. Darwish" <darwish.07@...il.com>,
	Pavel Machek <pavel@....cz>,
	Casey Schaufler <casey@...aufler-ca.com>,
	akpm@...ux-foundation.org, linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org, Al Viro <viro@....linux.org.uk>
Subject: Re: [PATCH] Smackv10: Smack rules grammar + their stateful parser

> Users are used to work on characters, not on bytes.

Absolutely true - but completely missing the point.

When I open a UTF-8 file name as displayed by nautilus the kernel does
byte comparisons. The kernel doesn't care what character set is in use.

> > So you either implement "match one byte", or you go crazy. It's that 
> > simple.
> 
> Sure, you can limit what is possible and what not.

If your regexps are reasonably complete you just have to turn the unicode
match into a byte match. That is a user interface problem - in user space.

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/