e the problem that you do not get javaws updates starting on
> January (easily) anymore.
>
> JNLP does not allow to overwrite random properties for the started app.
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> ------
> *From:* security-
g java.security properties, you use one
> equals, “=“. To override you use 2, “==‘. So you may want something like:
>
> java-vm-args="-Djava.security.properties==override_file"
>
>
> Tony
>
> On May 21, 2018, at 7:48 PM, Tom Hood wrote:
>
> Hi,
>
> Our
Hi,
Our legacy app will no longer launch with JNLP as of Java 8u171 and 8u172
due to the addition of "3DES_EDE_CBC" to the global java.security file's
"jdk.tls.disabledAlgorithms" property.
Schedule constraints do not allow us to upgrade our application to a
stronger cipher suite at this time and
nning with the JRE. I haven't tried running with the JDK
installation.
-- Tom
On Wed, Sep 20, 2017 at 2:17 PM, Tom Hood wrote:
> In case useful, our jnlp file also contains this:
>
>
>
>
>
> On Wed, Sep 20, 2017 at 2:14 PM, Tom Hood wrote:
>
>> Sean,
>&g
In case useful, our jnlp file also contains this:
On Wed, Sep 20, 2017 at 2:14 PM, Tom Hood wrote:
> Sean,
>
> I'll add those lines to the lib/security/default.policy file as you
> suggested. I left the app running overnight and came in this morning and
> it was s
quot; {
>> permission java.security.AllPermission;
>> };
>>
>> I have a hunch that permissions are not being granted to the jdk.javaws
>> module before it needs them. If that fixes the issue (or you don't see it
>> for a few days), I'll followup and
mains). Also, have you tested this on builds earlier than
> b181?
>
> Thanks,
> Sean
>
> On 9/19/17 2:53 PM, Tom Hood wrote:
>
>> I should add that we have not modified or overridden any policy files.
>> Also, we are not using a custom security manager.
>>
&
