Segmentation violation when attempting to load intermediate CA about goca HOT 1 CLOSED

@kairoaraujo Wanted to get your thoughts on the viability of my proposed solution before trying to implement it:

I think the best way to handle this is in CA.SignCSR(), if we set up the paths/storage type right here it seems like the rest of the code should "just work" as intended.

The SignCSR method can take a third boolean indicating if we are signing a regular certificate or another CA.

With a variadic argument signature, we can preserve the existing two-argument signature and it will just default to signing regular certificates by calling the new three-argument form with the appropriate boolean to indicate a regular cert.

On the REST API side, similarly add an optional boolean field in the JSON, if it is there call the three-argument SignCSR passing in the provided setting. Otherwise just call the two-argument SignCSR that defaults to signing regular certs.

from goca.