AFAIU, signing using SHA1 will not cause any harm.
@Sameera, Any thoughts on this?..
On Mon, Mar 9, 2015 at 12:56 PM, Rasika Perera wrote:
> Hi Aruna & All,
>
> Eventhough "-digestalg SHA1" solves(or work as a workaround), I am not
> clear about the jarsigner's verification behaviour.
>
>1.
Hi Aruna & All,
Eventhough "-digestalg SHA1" solves(or work as a workaround), I am not
clear about the jarsigner's verification behaviour.
1. Suppose we are signing a JAR with SHA1 then signing SHA256 with the
*same* *key* / alias verification *never fails*.
2. Signing a JAR with SHA1 th
Hi all,
This was resolved by adding the following argument to the jarsigner command.
*-digestalg SHA1*
This was suggested by Rasika, thanks for the suggestion.
Further found that two default jarsigner algorithms for JDK6 and JDK8
differs.
Regards,
Aruna
On Sat, Mar 7, 2015 at 3:34 PM, Aruna K
Hi all,
When security manager enabled for products,(which is build using java 8 and
signed using java8) following exception throws at the server start-up.
JAVA_HOME environment variable is set to
/home/aruna/software/java/jdk1.8.0_20
CARBON_HOME environment variable is set to
/home/aruna/Download
