PR: ASN.1 Time validation exception because not too much precision

[RobLinux]

Apple has ASN.1 times encoded in this format 20171017112741.65904593Z. If we read it with BC it will throw an exception, because the highest handled precision handled Asn1GeneralizedTime.cs is

case 23: return ParseUtc(s, @"yyyyMMddHHmmss.fffffff\Z");

Solution would be to increase to 24 + 25 with two extra floats.

It's currently a show stopper for my company. Any advice on how to counter it ? (we cannot modify the source data obviously)

[RobLinux]

#410 created a PR for it

[ArnoldCell]

Had the same issue lately