From: Eric M. <em...@mi...> - 2013-12-28 23:28:21
|
When running the unsigned Jmol applet under Java 1.7.0_45, I have seen a red notice that in future, unsigned applets will not be allowed. FirstGlance in Jmol is currently using the unsigned Jmol applet 13.0.15. To avoid having FirstGlance in Jmol stop working in a forthcoming Java update, should I configure it to use only the signed Jmol applet? And would that need to be signed Jmol applet 14.0 in order to be properly signed? Thanks, Eric |
From: Simone S. <sim...@gm...> - 2013-12-29 11:16:24
|
Dear Eric, I did exactly that with my MagresView. I think it's going to be required starting January 2014, so in a few days, but I think Robert will know better on the topic of course. Simone 2013/12/28 Eric Martz <em...@mi...> > When running the unsigned Jmol applet under Java 1.7.0_45, I have > seen a red notice that in future, unsigned applets will not be allowed. > > FirstGlance in Jmol is currently using the unsigned Jmol applet 13.0.15. > > To avoid having FirstGlance in Jmol stop working in a forthcoming > Java update, should I configure it to use only the signed Jmol applet? > > And would that need to be signed Jmol applet 14.0 in order to be > properly signed? > > Thanks, Eric > > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Jmol-users mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-users > -- _______________ Nuovo indirizzo e-mail: sim...@gm... |
From: Robert H. <ha...@st...> - 2013-12-29 20:00:29
|
I'm guessing it will be January 14: https://blogs.oracle.com/java-platform-group/entry/new_security_requirements_for_rias http://www.oracle.com/technetwork/topics/security/alerts-086861.html As I understand it, all applets must be updated. "signed" or not -- all must be signed, and local file reading now requires the JNLP files as well in the directory of the JAR files. (Note that these JNLP files allow the applet to be started outside a browser as well.) In addition, recent versions of JSmol JavaScript libraries are required, and if you are using the older Jmol.js, library that needs to be updated (see http://chemapps.stolaf.edu/jmol/docs/examples-12/Jmol.js). Or you can add this line yourself in the _jmolApplet function: params.permissions = (archivePath.indexOf("Signed") >= 0 ? "all-permissions" : "sandbox"); Feels like Y2K all over again! Bob On Sun, Dec 29, 2013 at 5:16 AM, Simone Sturniolo <sim...@gm... > wrote: > Dear Eric, > > I did exactly that with my MagresView. I think it's going to be required > starting January 2014, so in a few days, but I think Robert will know > better on the topic of course. > > Simone > > > 2013/12/28 Eric Martz <em...@mi...> > >> When running the unsigned Jmol applet under Java 1.7.0_45, I have >> seen a red notice that in future, unsigned applets will not be allowed. >> >> FirstGlance in Jmol is currently using the unsigned Jmol applet 13.0.15. >> >> To avoid having FirstGlance in Jmol stop working in a forthcoming >> Java update, should I configure it to use only the signed Jmol applet? >> >> And would that need to be signed Jmol applet 14.0 in order to be >> properly signed? >> >> Thanks, Eric >> >> >> >> ------------------------------------------------------------------------------ >> Rapidly troubleshoot problems before they affect your business. Most IT >> organizations don't have a clear picture of how application performance >> affects their revenue. With AppDynamics, you get 100% visibility into your >> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics >> Pro! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >> _______________________________________________ >> Jmol-users mailing list >> Jmo...@li... >> https://lists.sourceforge.net/lists/listinfo/jmol-users >> > > > > -- > _______________ > > Nuovo indirizzo e-mail: > sim...@gm... > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Jmol-users mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-users > > -- Robert M. Hanson Larson-Anderson Professor of Chemistry St. Olaf College Northfield, MN http://www.stolaf.edu/people/hansonr If nature does not answer first what we want, it is better to take what answer we get. -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 |
From: Rzepa, H. S <h....@im...> - 2013-12-30 06:21:32
Attachments:
signature.asc
|
On 29 Dec 2013, at 20:00, Robert Hanson <ha...@st...> wrote: > I'm guessing it will be January 14: > > https://blogs.oracle.com/java-platform-group/entry/new_security_requirements_for_rias > http://www.oracle.com/technetwork/topics/security/alerts-086861.html > > As I understand it, all applets must be updated. "signed" or not -- all must be signed, and local file reading now requires the JNLP files as well in the directory of the JAR files. (Note that these JNLP files allow the applet to be started outside a browser as well.) Is there a specific set of instructions for acquiring and installing these “JNLP” files for Jmol? Using this as a search term in Bob’s documentation http://chemapps.stolaf.edu/jmol/docs/?search=JNLP shows no hits. > > In addition, recent versions of JSmol JavaScript libraries are required, and if you are using the older Jmol.js, library that needs to be updated (see http://chemapps.stolaf.edu/jmol/docs/examples-12/Jmol.js). http://chemapps.stolaf.edu/jmol/docs/examples-12/Jmol.js states "THIS LIBRARY IS DEPRECATED STARTING WITH Jmol 13.0.” > Or you can add this line yourself in the _jmolApplet function: > params.permissions = (archivePath.indexOf("Signed") >= 0 ? "all-permissions" : "sandbox"); > > > Feels like Y2K all over again! > |
From: Robert H. <ha...@st...> - 2013-12-30 16:51:34
|
The JNLP files are just in the directory with the JAR files. No "installation" -- just click on one, and the applet should open. On Mon, Dec 30, 2013 at 12:21 AM, Rzepa, Henry S <h....@im...>wrote: > > On 29 Dec 2013, at 20:00, Robert Hanson <ha...@st...> wrote: > > > I'm guessing it will be January 14: > > > > > https://blogs.oracle.com/java-platform-group/entry/new_security_requirements_for_rias > > http://www.oracle.com/technetwork/topics/security/alerts-086861.html > > > > As I understand it, all applets must be updated. "signed" or not -- all > must be signed, and local file reading now requires the JNLP files as well > in the directory of the JAR files. (Note that these JNLP files allow the > applet to be started outside a browser as well.) > > Is there a specific set of instructions for acquiring and installing these > “JNLP” files for Jmol? Using this as a search term in Bob’s > documentation http://chemapps.stolaf.edu/jmol/docs/?search=JNLP shows no > hits. > > > > In addition, recent versions of JSmol JavaScript libraries are required, > and if you are using the older Jmol.js, library that needs to be updated > (see http://chemapps.stolaf.edu/jmol/docs/examples-12/Jmol.js). > > > http://chemapps.stolaf.edu/jmol/docs/examples-12/Jmol.js states "THIS > LIBRARY IS DEPRECATED STARTING WITH Jmol 13.0.” > > > Or you can add this line yourself in the _jmolApplet function: > > params.permissions = (archivePath.indexOf("Signed") >= 0 ? > "all-permissions" : "sandbox"); > > > > > > Feels like Y2K all over again! > > > > > > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Jmol-users mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-users > > -- Robert M. Hanson Larson-Anderson Professor of Chemistry St. Olaf College Northfield, MN http://www.stolaf.edu/people/hansonr If nature does not answer first what we want, it is better to take what answer we get. -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 |
From: Rzepa, H. S <h....@im...> - 2013-12-30 13:25:48
Attachments:
signature.asc
|
On 29 Dec 2013, at 20:00, Robert Hanson <ha...@st...> wrote: > I'm guessing it will be January 14: > > https://blogs.oracle.com/java-platform-group/entry/new_security_requirements_for_rias > http://www.oracle.com/technetwork/topics/security/alerts-086861.html > > As I understand it, all applets must be updated. "signed" or not -- all must be signed, and local file reading now requires the JNLP files as well in the directory of the JAR files. (Note that these JNLP files allow the applet to be started outside a browser as well.) Using Jmol 14.0.2 (14th December) uploaded to a server, I can indeed no longer get the applet to load (OS X Mavericks/Safari or Firefox). "Application blocked by security settings”. It also (falsely) tells me that "the Java security settings have prevented this application from running. You may change this behaviour in the Java control panel”. Well, I could not. This did not happen with eg 13.3.9. There are four JNLP files in this build of Jmol in the Java directory (including eg JmolApplet.jnlp and JmolAppletSigned.jnlp), but their presence has not prevented the above message. Am struggling slightly. Could it be that our Apache server has no MIMEtype defined for JNLP? Or that OS X Mavericks Java is broken in this regard? Or that some other configuration which I have omitted is needed? The relevant page is http://www.ch.ic.ac.uk/rzepa/WEO/ja061400a/?JAVA (which is an ancient page from ~2007 which I thought I might try to rescue). |
From: Philip B. <pb...@sa...> - 2013-12-30 15:23:18
|
Henry: I am using the same OS but downloaded last evening’s release of jmol (14.0.3). I test using my sites local network server on an iMac, which should behave like an outside server. My test was to access test2.htm in the jsmol directory. It runs fine with HTML5 and the signed applet. But does not do so when simply launched as a file. I did have to change permissions on the jmol directory. In my java console (security tab>manage certificates, I see the Integrated Graphics certificate as trusted (That has been true since originally specified several iterations of jmol ago. However, when I try your link, I get the same results as you do. On Dec 30, 2013, at 8:25 AM, Rzepa, Henry S <h....@im...> wrote: > > On 29 Dec 2013, at 20:00, Robert Hanson <ha...@st...> wrote: > >> I'm guessing it will be January 14: >> >> https://blogs.oracle.com/java-platform-group/entry/new_security_requirements_for_rias >> http://www.oracle.com/technetwork/topics/security/alerts-086861.html >> >> As I understand it, all applets must be updated. "signed" or not -- all must be signed, and local file reading now requires the JNLP files as well in the directory of the JAR files. (Note that these JNLP files allow the applet to be started outside a browser as well.) > > Using Jmol 14.0.2 (14th December) uploaded to a server, I can indeed no longer get the applet to load (OS X Mavericks/Safari or Firefox). > > "Application blocked by security settings”. > > It also (falsely) tells me that "the Java security settings have prevented this application from running. You may change this behaviour in the Java control panel”. Well, I could not. This did not happen with eg 13.3.9. > > There are four JNLP files in this build of Jmol in the Java directory (including eg JmolApplet.jnlp and JmolAppletSigned.jnlp), but their presence has not prevented the above message. > > Am struggling slightly. > > Could it be that our Apache server has no MIMEtype defined for JNLP? > Or that OS X Mavericks Java is broken in this regard? > Or that some other configuration which I have omitted is needed? > > The relevant page is http://www.ch.ic.ac.uk/rzepa/WEO/ja061400a/?JAVA (which is an ancient page from ~2007 which I thought I might try to rescue). > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk_______________________________________________ > Jmol-users mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-users Philip Bays Emeritus Professor of Chemistry Saint Mary's College Notre Dame, IN 46556 pb...@sa... |
From: Rzepa, H. S <h....@im...> - 2013-12-31 08:37:37
Attachments:
signature.asc
|
On 30 Dec 2013, at 14:59, Philip Bays <pb...@sa...> wrote: > Henry: > > I am using the same OS but downloaded last evening’s release of jmol (14.0.3). I test using my sites local network server on an iMac, which should behave like an outside server. My test was to access test2.htm in the jsmol directory. It runs fine with HTML5 and the signed applet. But does not do so when simply launched as a file. I did have to change permissions on the jmol directory. > > In my java console (security tab>manage certificates, I see the Integrated Graphics certificate as trusted (That has been true since originally specified several iterations of jmol ago. > > However, when I try your link, I get the same results as you do. > OK, tracked it down. In the info variable; Info = { width: 400, … etc jarFile: "JmolAppletSigned.jar", isSigned: "true", disableJ2SLoadMonitor: false, the original specification omitted the isSigned: "true”, but it now essential. Adding it in now allows the applet to be used. This does reveal an issue, since there must be a vast amount of “legacy” Jmol-Java based stuff, that may well all stop working on January 14th. Depending on how old it is (even Jmol 13 will fail apparently?) the updating may be a great deal of unpredictable manual work. Even a single wrong or missing variable may knock things on their head. I suspect that the easiest recourse might be to give up on Java entirely and just get it working with JSmol? |