<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 08/10/2016 11:00 AM, Jakob Bohm wrote:<br>
<blockquote
cite="mid:032bc7ec-61aa-17ad-1eae-34b3bcad903c@wisemo.com"
type="cite">On 08/08/2016 16:51, Benjamin Kaduk wrote:
<br>
<blockquote type="cite">What Rich said, and also note that it's
perfectly valid usage of the PEM routines to read one type from
a BIO and then go on to read another (potentially different)
type from the same BIO, as would happen if they were in the same
file concatenated after each other. So, attempting to peek and
see if there was other stuff after the read PEM object would be
a strange special case.
<br>
<br>
</blockquote>
Maybe there should be a general
<br>
check-no-more-data-in-file(BIO*,bool*bIsPEM)
<br>
routine called from the functions that take a file name as
<br>
argument, open it as a BIO, loads some PEM data and closes
<br>
the BIO, thus giving the caller no opportunity to use (or
<br>
check for) any extra PEM blocks (or DER blocks for DER
<br>
input).
<br>
</blockquote>
<br>
That level of foot-shooting-protection seems overkill to me, though
my opinion doesn't really matter since I'm not on the dev team.<br>
<br>
-Ben<br>
</body>
</html>