Originally posted by Amit Agarwal:
Good news guys,
I have checked the usage of trusted applets with Java(TM) Plug-in: Version 1.3.0rc1-T using JRE version 1.3.0rc1 Java HotSpot(TM) Client VM. It seems sun has solved the problem of not looking at the IE repository. Now, you can simply give a link to the certificate on your web page, and ask the user to install it in their browser. Once the certificate is installed your applet's signature will be verified against the IE repository and the user will be asked if he would like to grant the applet privileges.
You no longer need to manually import the certificate in the cacerts file. Although, it may be required for some users who might be using some particular sub version java plugin 1.3, but they can simply upgrade to a newer version.
Amit
Java Rawks
Originally posted by Amit Agarwal:
Good news guys,
I have checked the usage of trusted applets with Java(TM) Plug-in: Version 1.3.0rc1-T using JRE version 1.3.0rc1 Java HotSpot(TM) Client VM. It seems sun has solved the problem of not looking at the IE repository. Now, you can simply give a link to the certificate on your web page, and ask the user to install it in their browser. Once the certificate is installed your applet's signature will be verified against the IE repository and the user will be asked if he would like to grant the applet privileges.
You no longer need to manually import the certificate in the cacerts file. Although, it may be required for some users who might be using some particular sub version java plugin 1.3, but they can simply upgrade to a newer version.
Amit
Originally posted by a hui:
By using this certificate, is this another way of dealing with the security? because I just solved the problem by editing the policy file.
Originally posted by Amit Agarwal:
the user needs to go thru two steps. first is to install the certificate, this is required just once for every machine. this is achieved by clicking on the link to the certificate and pressing the install button and follow the instructions (2-3 confirmations). once this is done, the scertificate of the signed applet can be authenticated against the installed applet.
the second step is to grant rights to the applet. when you access the applet, IE checks the certificate of the applet jar, authenticates it against the installed certificate and pops up a dialogbox where the user can grant access to the applet for a session or forever or even deny it. so according to the users choice the applet runs in a trusted environment. if the user chooses to grant rights to the applet for a session, he wil be prompted with the same dialog box when he accesses the applet the next time.
She's out of the country right now, toppling an unauthorized dictatorship. Please leave a message with this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|