Code signing [Was: JEP draft: Prepare to Restrict The Use of JNI]

[Attila Kelemen]

>
> Why not? It's a simple mechanism, anyone can do it, and anyone can add
> trusted libraries to their blessed list. All that crypto-signing does is
> add another layer of robustness.
>

What I meant is that the signature itself is not that important, what is
important is that you can reliably identify a library. However, you don't
really need all the guarantees a signature gives you for this. It is
enough, if you read some properties from the manifest like vendor, etc. and
trust it. In fact, it might even tells you more, because if not any
manifest entry can be used, then you could tell from the presence of the
manifest entry that people considered that these properties will be used
for access rights (unlike signatures, because all libraries in Maven
central are signed).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jdk-dev/attachments/20230907/971a5ebb/attachment.htm>