Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #168583 +++ When performing an operation on a signed jar that should not change the hash, ie a repack, or the no-op processing seen in bug 168579, the jar processor can change the hash of the eclipse.inf causing the result to fail verification. This will happen when the jar is signed on a different platform than the one where the later processing occurs. ex: sign on linux, pack on windows. The change comes from the different line endings on the different platforms: \n vs \r\n.
I think this should be fixed in 3.2.2. This is a problem when updating signed & packed jars.
Created attachment 55925 [details] patch against R3_2_maintenance branch
DJ, can you get the required approvals before we release the patch into the maintenance stream?
Just to be clear, since the first comment talks in generalities: The problem is that, on windows, when updating a jar that was packed and signed on linux, the unpack will change the line endings of the META-INF/eclipse.inf file. The result is the jar will fail verification (and potentially cause an NPE (see bug 163421)).
+1 for 3.2.2 assuming the fix is not too risky
Released.