On 14102 March 1977, Laura Arjona Reina wrote: >> The main point that makes it entirely unusable is its usage of a >> new subdomain for serving the javascript FOR EVERY NEW REQUEST. >> This is beyond stupid and disallows any kind of javascript blocker >> in your browser, unless you allow it to trust the whole debian.net >> domain, which is way too far fetched. > I understand. Would adding storm.debian.net to the white list do the > trick? > I've done it in my Iceweasel with NoScript and it seems to work but > I'm not totally sure.
Only if JS gets served from there. The two anti-js things i tested for chromium either want to trust all of debian.net for full domain, or just the host, ie they dont want to allow "everything below this subdomain". :/ In any sensible setup there isnt the need for it. :/ -- bye, Joerg _______________________________________________ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
