For me, the target file doesn’t exist - even with the build-packages @kz6fittycent listed above.
It also doesn’t exist on my build machine.
For me, the target file doesn’t exist - even with the build-packages @kz6fittycent listed above.
It also doesn’t exist on my build machine.
@frossty Thank you for your workaround.
I don’t think that this is a good solution in the long run, as it pretty sure undermines a security feature of Java.
But as long as the blacklisted.certs isn’t even present in the java-11-openjdk (aka default-jre) package…
Perhaps someone could check, if the current java-11-openjdk version accepts blacklisted certificates 
Anyways, this solution requires no additional build packages (ca-certificates and ca-certificates-java).
ah, that would explain why the snapcraft logic does indeed not work if it is a dangling symlink even outside of the snap context ![]()
It works, thanks @frossty
There are another file named lib/security/blocked.certs. If this file is renamed from blacklist.certs, this bug makes us suffer 
Yes, I think they have renamed the file: https://bugs.openjdk.java.net/browse/JDK-8253866