Kind of a doomsday, I'm afraid.
One of the aspects of this (if I have it right, and I think I do) is that *all
Java developers who which to build any applet and run it on their local
installations will have to have trusted signed certificates.*
As far as I can tell, this is pretty much the end
This is building up on my previous feeling:
while trying to protect themselves from responsibility on what
malicious Java applets might do, Oracle is just killing their own
Java business -- everyone will run away and move to another platform.
Do they realize?
Sure they realize. I think we're lucky Java still exists at all, actually.
I'm guessing Oracle is running fastest.
On Wed, Nov 6, 2013 at 7:36 AM, Angel Herráez angel.herr...@uah.es wrote:
This is building up on my previous feeling:
while trying to protect themselves from responsibility on
Hi Bob,
Hard constraints are indeed being added to Java for applets and JNLP :-(
I think it will still be possible to use self signed applets locally for
development by circumventing this mechanism : a trusted certificate is
nothing more than a certificate issued by a root certificate authority
nope. Read the blog carefully.
https://blogs.oracle.com/java-platform-group/entry/code_signing_understanding_who_and
*Developers* must sign any browser applet or Web Start application that
they produce. Signatures on other application types (such as back-end
server applications) are optional.
You misunderstood me.
You will need to sign Jmol applet even to test it locally, I agree, this is
a new requirement.
But locally, you can add your own self-signed certificate (or the own
currently in Jmol SVN) in your repository of trusted certificate
authorities : your self-signed certificate
That would be good. I'll believe it when I see it. That's not one of
options they mention in the blog. Seems to me that would have been the
obvious solution.
On Wed, Nov 6, 2013 at 8:30 AM, Nicolas Vervelle nverve...@gmail.comwrote:
You misunderstood me.
You will need to sign Jmol applet
I think it's just something like what is described in here
http://stackoverflow.com/questions/11617210/how-to-properly-import-a-selfsigned-certificate-into-java-keystore-that-is-avail
Nico
On Wed, Nov 6, 2013 at 6:29 PM, Robert Hanson hans...@stolaf.edu wrote:
That would be good. I'll believe
On 11/06/2013 06:29 PM, Robert Hanson wrote:
That would be good. I'll believe it when I see it. That's not one of
options they mention in the blog. Seems to me that would have been the
obvious solution.
On Wed, Nov 6, 2013 at 8:30 AM, Nicolas Vervelle nverve...@gmail.comwrote:
You
Hi,
I've produced jars for Jmol signet applet that are signed with my own
trusted certificate.
The jars are also time-stamped.
You can try them by downloading at
http://site4145.mutu.sivit.org/Temporary/JmolAppletSigned.zip
Nico
Nico, a quick test and it works
I opened a page in local webserver (otherwise I am having trouble in general
with JSmol from local disk)
A Java dialog asked to trust you, I accepted for ever.
Then it asked --a different dialog, from the browser maybe or the browser
plugin-- if I wanted to allow
Hi,
For many years I have used local web pages on my laptop instead of using ppt
for lectures.
This has enabled me to have Jmol and JSpecView at hand and for 2-way
interaction between them.
(Originally I used MDL CHIME)
I was horrified to discover that having set an assignment in our computer
On 6 Nov 2013, at 20:21, LANCASHIRE,Robert J robert.lancash...@uwimona.edu.jm
wrote:
Hi,
For many years I have used local web pages on my laptop instead of using ppt
for lectures.
This has enabled me to have Jmol and JSpecView at hand and for 2-way
interaction between them.
13 matches
Mail list logo
