Messages in this thread |  | | | Date | Mon, 16 Feb 2004 21:10:33 +0000 | | From | viro@parcelfa ... | | Subject | Re: UTF-8 practically vs. theoretically in the VFS API |
| |
On Mon, Feb 16, 2004 at 09:16:10PM +0100, Marc Lehmann wrote: > The point is, however, that this is highly undesirable, and it would be > nice to have a kernel that would (optionally) fully support a UTF-8 > environment in where applications can feed UTF-8 and _expect_ UTF-8 in > return, which _is_ a security issue. > > It's very desirable to have a kernel that actively supports this. IT is > clearly not _required_, of course. But then again, process abstraction > is also not required...
Mind taking the demagogy elsewhere? Note that the same handwaving applies to e.g. file contents. Care to explain what makes read() and write() different in that respect? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |