Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267087AbTGKWaa (ORCPT ); Fri, 11 Jul 2003 18:30:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267089AbTGKWaa (ORCPT ); Fri, 11 Jul 2003 18:30:30 -0400 Received: from air-2.osdl.org ([65.172.181.6]:7141 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S267087AbTGKWaZ (ORCPT ); Fri, 11 Jul 2003 18:30:25 -0400 Date: Fri, 11 Jul 2003 15:44:58 -0700 (PDT) From: Linus Torvalds To: Alan Cox cc: Mikulas Patocka , Linux Kernel Mailing List Subject: Re: SECURITY - data leakage due to incorrect strncpy implementation In-Reply-To: <1057959932.20637.51.camel@dhcp22.swansea.linux.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 617 Lines: 19 On 11 Jul 2003, Alan Cox wrote: > > Lots of kernel drivers rely on the libc definition of strncpy. But that's ok. We _do_ do the padding. I hated it when I wrote it, but as far as I know, the kernel strncpy() has done padding pretty much since day one. Yes, strlcpy() conversion users need to be careful, but I think we mostly _were_ careful. Knock wood. Linus - 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/