[rfc][icedtea-web] conditional disabling of manifes tattributes

[Jiri Vanek]

On 04/10/2014 04:44 PM, Andrew Azores wrote:
> On 04/10/2014 08:43 AM, Jiri Vanek wrote:
>> Hi!
>>
>> This patch can disable the check for new manifest attributes.
>> sevral motivations
>>   -  I hate this feature
>>   - the remembering of this actions may take time to implement
>>   - and the most important  - the testsuite...
>
> Most important indeed.
>
>>
>> will go both head and 1.5.
>>
>> I'm hesitating whether to make this property public via itw-settings... Well if so, then as
>> another changeset. Any opinion about publish it in itw-settings?
>>
>> J
>
> Ok to push, so that we can clean up some of the noise in the test suite.
>
> RE putting it in itweb-settings - I think the cleanest way to do this, if it's to be done at all, is
> probably to add another security level. 'Minimal' or something perhaps? Because I don't think it
> makes sense to add it in as a checkbox, for example, and have it possible to set security to High,
> but disable manifest checks. I'm not sure if we really want to allow this, though. I can imagine
> most users leaving the security level at Minimal once they discover that this gives them the least
> amount of clicking to do before getting their applets to run :)


Oh yes, that can be correct thing to do. But looking to the issue from this perspective, it is NO-GO 
  argument for it as it is done. Well all correct applications should be updated to support new 
attributes.. but the legaxy, and still used ones?

So I have another idea here - really extend ExtendedAppletsSecurity, and to allow "do not check 
manifest attributes" on the application/codebase  - So all those dialogs will be moreover based on 
your abstraction of Extended Applets security. Also remember alaca checkbox issue will be solved  by 
this.

Bu the extension of ExtendedAppletsSecurity will needed to be done really carefully - and prepared 
before implementation.

What do you think?