Just trying to understand the implications: - This bug was not fixed yet in the package (0.7.5) that is in debian 8, right?- Having this bug means all the certificates I create with a non fixed version will stop working in 2016 (which is in less than 2 months). If that's all true, could you please fix it soon. Thank youJochen
