We've run into an interesting - apparently new? - behavior of the openssl ca 
command: 


I believe we've used the following command in the past (pre 1.0.0). (Don't know 
why we were still using the -infiles option with a single input file - 
something vestigial, no doubt; Nonetheless, I think it's worked: 



../bin/openssl ca \ 
-days 1095 \ 
-infiles YOUR.csr \ 
-out YOUR.crt \ 
-config ../openssl.cnf 


Now, using OpenSSL v1.0.0, this command results in an error, as if the -infiles 
option is trying to read the -out option as a filename! (Yes, many of our 
commands are formatted with the backslash for readability): 



-out: No such file or directory 
4274892676:error:02001002:system library:fopen:No such file or 
directory:bss_file.c:355:fopen('-out','r') 
4274892676:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:357: 


Don't know if this is a new 'fastidiousness' of the ca command, or if we simply 
never hit it before, but it may merit attention. 



For example, we haven't tested all the permutations, such as what would happen 
if the -infiles option were the last option in the command string, and had only 
one file as an input? 


Lou 

Reply via email to