Boris Zbarsky a écrit :
Marine wrote:
The webpage have to be able to expose some values/parameters to the
extension.
So I tried to add properties to button, to document or to window
objects, in my webpage.
The problem is that reading those from chrome would be exploitable (by
the
Boris Zbarsky a écrit :
> Marine wrote:
>
>> The webpage have to be able to expose some values/parameters to the
>> extension.
>> So I tried to add properties to button, to document or to window
>> objects, in my webpage.
>>
>
> The problem
Marine a écrit :
> Jonas Sicking a écrit :
>> Marine wrote:
>>
>>> Boris Zbarsky a écrit :
>>>
>>>> Marine wrote:
>>>>
>>>>> However, I don't see how to put all the code in a signed j
Jonas Sicking a écrit :
> Marine wrote:
>
>> Boris Zbarsky a écrit :
>>
>>> Marine wrote:
>>>
>>>
>>>> However, I don't see how to put all the code in a signed jar, as JSP
>>>> will generate HTML cod
Boris Zbarsky a écrit :
Marine wrote:
However, I don't see how to put all the code in a signed jar, as JSP
will generate HTML code dynamically for each client request.
Is it possible to dynamically generate the signed jar? Or move the
logic from server to c
but I
would like to avoid this if possible.
Boris Zbarsky a écrit :
Marine wrote:
...
I wonder if this could be due to vulnerability correction in Firefox
2.0.0.15 : http://www.mozilla.org/security/announce/2008/mfsa2008-23.html
Yes. What you were
Hi,
A few months ago, I posted this message :
http://groups.google.com/group/mozilla.dev.security/browse_thread/thread/d95d4d9d82959739/da0875e5639698c2?lnk=gst&q=signed+jar#da0875e5639698c2
I wanted to call JavaScript methods that require special Firefox
privileges from a JSP page
I finally su
