On Thu, Jun 6, 2013 at 1:48 AM, Andrew Morton wrote:
>> - strncpy(containerpath, optarg, strlen(optarg) + 1);
>> + strlcpy(containerpath, optarg, sizeof(containerpath));
>> break;
>> case 'w':
>>
On Thu, Jun 6, 2013 at 1:48 AM, Andrew Morton a...@linux-foundation.org wrote:
- strncpy(containerpath, optarg, strlen(optarg) + 1);
+ strlcpy(containerpath, optarg, sizeof(containerpath));
break;
case 'w':
On Wed, Jun 5, 2013 at 4:48 PM, Andrew Morton wrote:
> On Fri, 31 May 2013 09:18:07 -0700 Kees Cook wrote:
>
>> Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
>> limits should be about the space available in the destination, not
>> repurposed as a method to either
On Fri, 31 May 2013 09:18:07 -0700 Kees Cook wrote:
> Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
> limits should be about the space available in the destination, not
> repurposed as a method to either always include or always exclude
> a trailing NULL byte. Either
On Fri, 31 May 2013 09:18:07 -0700 Kees Cook keesc...@chromium.org wrote:
Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
limits should be about the space available in the destination, not
repurposed as a method to either always include or always exclude
a trailing
On Wed, Jun 5, 2013 at 4:48 PM, Andrew Morton a...@linux-foundation.org wrote:
On Fri, 31 May 2013 09:18:07 -0700 Kees Cook keesc...@chromium.org wrote:
Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
limits should be about the space available in the destination, not
On Friday, May 31, 2013 09:18:07 AM Kees Cook wrote:
> Fix various weird constructions of strncpy(dst, src, strlen(src)).
> Length
> limits should be about the space available in the destination, not
> repurposed as a method to either always include or always exclude
> a trailing NULL byte. Either
On Friday, May 31, 2013 09:18:07 AM Kees Cook wrote:
Fix various weird constructions of strncpy(dst, src, strlen(src)).
Length
limits should be about the space available in the destination, not
repurposed as a method to either always include or always exclude
a trailing NULL byte. Either the
On Friday, May 31, 2013 09:18:07 AM Kees Cook wrote:
> Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
> limits should be about the space available in the destination, not
> repurposed as a method to either always include or always exclude
> a trailing NULL byte. Either
On Friday, May 31, 2013 09:18:07 AM Kees Cook wrote:
Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
limits should be about the space available in the destination, not
repurposed as a method to either always include or always exclude
a trailing NULL byte. Either the
On Fri, May 31, 2013 at 09:18:07AM -0700, Kees Cook wrote:
> Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
> limits should be about the space available in the destination, not
> repurposed as a method to either always include or always exclude
> a trailing NULL byte.
Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
limits should be about the space available in the destination, not
repurposed as a method to either always include or always exclude
a trailing NULL byte. Either the NULL should always be copied
(using strlcpy), or it should
Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
limits should be about the space available in the destination, not
repurposed as a method to either always include or always exclude
a trailing NULL byte. Either the NULL should always be copied
(using strlcpy), or it should
On Fri, May 31, 2013 at 09:18:07AM -0700, Kees Cook wrote:
Fix various weird constructions of strncpy(dst, src, strlen(src)). Length
limits should be about the space available in the destination, not
repurposed as a method to either always include or always exclude
a trailing NULL byte. Either
14 matches
Mail list logo