search

rbeckman-nextgen / test-mc4

0 stars 0 forks source link

Fix warnings introduced with Java 7u25 #2863

Closed rbeckman-nextgen closed 4 years ago

rbeckman-nextgen commented 4 years ago

Java 7u25 introduced new security attributes. See http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/no_redeploy.html

Without them the following warnings show up in the consoler for each jar.

Missing Permissions manifest attribute for: http://localhost:8080/webstart/client-lib/mirth-client.jar Missing Codebase manifest attribute for: http://localhost:8080/webstart/client-lib/mirth-client.jar

Imported Issue. Original Details: Jira Issue Key: MIRTH-2963 Reporter: wayneh Created: 2013-10-01T12:15:15.000-0700

rbeckman-nextgen commented 4 years ago

This is also a warning when webstarting on OSX with Java 7 update 45.

Imported Comment. Original Details: Author: jacobb Created: 2013-10-18T13:43:27.000-0700

rbeckman-nextgen commented 4 years ago

This issue will no longer exist if we implement Getdown for MIRTH-3036.

Imported Comment. Original Details: Author: jacobb Created: 2013-10-29T17:58:32.000-0700

rbeckman-nextgen commented 4 years ago

Updated the build to automatically add the following to all client-lib and extension jars: Permissions: all-permissions Codebase: * Application-Name: Mirth Connect

Also unsigned bcprov-jdk16-144.jar and not-yet-commons-ssl-0.3.11.jar since we modify the manifest and the signatures are no longer valid. We re-sign the jar after modifying the manifest during the build process.

Imported Comment. Original Details: Author: jacobb Created: 2013-10-31T14:55:25.000-0700

rbeckman-nextgen commented 4 years ago

Unsigned ws jars since we modify the manifest and the signatures are no longer valid. We re-sign the jars after modifying the manifest during the build process.

Imported Comment. Original Details: Author: jacobb Created: 2013-10-31T15:46:12.000-0700

rbeckman-nextgen commented 4 years ago

Committed an already signed bcprov with a modified manfiest. Exclude bcprov from being signed and having its manifest modified during the build process. bcprov 1.5 will not need to be modified, and could be used instead when it is released.

Imported Comment. Original Details: Author: jacobb Created: 2013-10-31T16:33:04.000-0700

rbeckman-nextgen commented 4 years ago

Updated bcprov to the latest 1.5 beta that already has the manifest changes necessary and is signed by BC.

Imported Comment. Original Details: Author: jacobb Created: 2013-10-31T17:01:14.000-0700

rbeckman-nextgen commented 4 years ago

It looks like we're also getting this warning by launching from the https port because that certificate is self-signed. Launching from the http port is fine. Perhaps we should revert back to requiring that we launch webstart from the http port.

Imported Comment. Original Details: Author: jacobb Created: 2013-11-08T13:30:19.000-0800

rbeckman-nextgen commented 4 years ago

Changed the WebAdmin to launch webstart through the http port by default. Leaving the ability to launch webstart manually through the https port, but there are no longer any links that direct to the url with the https port.

Imported Comment. Original Details: Author: jacobb Created: 2013-11-21T11:57:07.000-0800

rbeckman-nextgen commented 4 years ago

Update bouncy castle one more time before releasing.

Imported Comment. Original Details: Author: jacobb Created: 2013-11-22T13:15:09.000-0800

rbeckman-nextgen commented 4 years ago

Updated the build to automatically add the following to all client-lib and extension jars: Permissions: all-permissions Codebase: * Application-Name: Mirth Connect

Updated bcprov to the latest 1.5 beta taht already has the manifest changes necessary and is signed by BC. Unsigned not-yet-commons-ssl-0.3.11.jar since we modify the manifest and the signatures are no longer valid. We re-sign the jar after modifying the manifest during the build process.

Imported Comment. Original Details: Author: jacobb Created: 2013-11-25T10:33:36.000-0800

rbeckman-nextgen commented 4 years ago

Verified that the permissions / codebase warnings no longer show up in the client console. Also, the warning that occurred when webstarting from the HTTPS port no longer shows up.

Imported Comment. Original Details: Author: narupley Created: 2013-12-03T17:05:11.000-0800

rbeckman-nextgen commented 4 years ago

Updated bcprov again now that 1.50 has been officially released.

Imported Comment. Original Details: Author: wayneh Created: 2013-12-04T17:56:34.000-0800

rbeckman-nextgen commented 4 years ago

Would it be possible to backport this fix to the v2.2 branch? We have production servers running v2.2 and are not yet ready to upgrade to v3.0 due to other issues.

Imported Comment. Original Details: Author: dgtombs Created: 2014-08-13T08:35:08.000-0700