Alexander Mueller wrote:
> However HTTPS does not prevent that the Administrator of the
> destination server is acquiring the actual plain text data.
So the .value of this input would already be hashed? Otherwise, this argument
fails: the page can just grab the value and do whatever it wants wi
If you change the "security.fileuri.origin_policy" pref to a traditional
value does it start working again?
http://bonsai.mozilla.org/cvsblame.cgi?file=/mozilla/modules/libpref/src/init/all.js&rev=3.717&mark=477-478#477
Try '3' first, and if that's still not working try '4'.
Is there a way to dow
Sorry, if I might have chosen the wrong group, but as my issue is also
security related I thought this group is still the best to choose. If
there is a better, please let me know. Thank you.
I sent this message already to a W3.org mailing list, but consider it as
important to have it discussed
Hi Armin,
On 1/9/08, Armin Mueller <[EMAIL PROTECTED]> wrote:
> First i want to say that i am new in this group and that i am not very
> versed in security questions.
> And, my english not very good, sorry.
>
> Now my problem.
> We have several applications which show interactive SVG maps
> (http:
First i want to say that i am new in this group and that i am not very
versed in security questions.
And, my english not very good, sorry.
Now my problem.
We have several applications which show interactive SVG maps
(http://www.mapviewsvg.com/examples/index.html). These applications should
be r
