In reviewing this bug, it appears to be user error .... Reasoning as
follows:
1) pkcs12 in the absence of -export PARSES a PKCS12 input file.
The commandline noted in the report implies the user is trying
to CREATE a PKCS12 file (-out cert.p12); i.e. the user's intent
was to run the command WITH -export included.
2) The code creates the output file before doing much processing, and,
at least for SOME processing errors, does not remove it. So, at least
for some errors, it results in a new zero-byte output file.
I have not tested on v4.0, nor do I have the exact inputs used by the
submitter. However, if either of the files specfied for -in or -inkey
are not valid PKCS12 files, a zero-byte output file results (though,
at least on Squeeze, with error message(s) indicating failure).
3) In all cases I have tried, failure to create the output file due to
exceeding
quota results in:
Error opening output file cert.p12
cert.p12: Disk quota exceeded
Which is consistent with code calling perror() on any failure to
fopen() the
file (code which has been in pkcs12.c since 1999).
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
