From mboxrd@z Thu Jan 1 00:00:00 1970 From: Miloslav =?UTF-8?Q?Trma=C4=8D?= Subject: Re: [PATCH 1/2] audit: fix NUL handling in untrusted strings Date: Thu, 11 Sep 2008 20:15:11 +0200 Message-ID: <1221156911.17533.17.camel@amilo> References: <1221085418.2705.19.camel@amilo> <1221143113.2992.9.camel@localhost.localdomain> <48C955C8.2000602@redhat.com> <1221156612.17533.14.camel@amilo> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1221156612.17533.14.camel@amilo> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: John Dennis Cc: linux-audit , viro@zeniv.linux.org.uk, linux-kernel List-Id: linux-audit@redhat.com Miloslav Trma=C4=8D p=C3=AD=C5=A1e v =C4=8Ct 11. 09. 2008 v 20:10 +0200: > Yes, that's possible - but then audit_log_n_untrustedstring() would be > more accurately called audit_log_n_ascii_like_binary_data(). ... my original patch (which stops at the first NUL) works the same way the other interfaces with maximum string length (e.g. strnlen() or printf ("%.5s", ...)) do. Mirek