Re: [PATCH] X.509: fix printing uninitialized stack memory when OID is empty
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: [PATCH] X.509: fix printing uninitialized stack memory when OID is empty
From
: David Howells <dhowells@xxxxxxxxxx>
Date
: Tue, 28 Nov 2017 11:03:54 +0000
Cc
: dhowells@xxxxxxxxxx, keyrings@xxxxxxxxxxxxxxx, linux-crypto@xxxxxxxxxxxxxxx, Alexander Potapenko <glider@xxxxxxxxxx>, Eric Biggers <ebiggers@xxxxxxxxxx>, Takashi Iwai <tiwai@xxxxxxx>
In-reply-to
: <
20171127071817.25999-1-ebiggers3@gmail.com
>
Organization
: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903
References
: <
20171127071817.25999-1-ebiggers3@gmail.com
>
I wonder if all -EBADMSG returns here should just print "(badoid)" into the buffer. David
Follow-Ups
:
Re: [PATCH] X.509: fix printing uninitialized stack memory when OID is empty
From:
Eric Biggers
References
:
[PATCH] X.509: fix printing uninitialized stack memory when OID is empty
From:
Eric Biggers
Prev by Date:
Re: [PATCH] X.509: fix comparisons of ->pkey_algo
Next by Date:
Re: [PATCH 4/4] staging: most: Remove a attribute group from a kobject
Previous by thread:
[PATCH] X.509: fix printing uninitialized stack memory when OID is empty
Next by thread:
Re: [PATCH] X.509: fix printing uninitialized stack memory when OID is empty
Index(es):
Date
Thread
[Index of Archives]
[Kernel]
[Gnu Classpath]
[Gnu Crypto]
[DM Crypt]
[Netfilter]
[Bugtraq]
