Allow CSR parsing to handle custom extensions #150
Description
Hi,
Currently when using a user defined custom_extensions, this causes the CSR parsing to error out with UnsupportedExtension.
Would it be possible to allow CSR parsing of custom extensions, such as by providing a closure to handle unknown extensions?