Re: Re (5): Configuring Iceweasel security policies.

2011-06-17 Thread Scott Ferguson
On 17/06/11 04:45, peasth...@shaw.ca wrote: > From: Scott Ferguson > Date: Thu, 16 Jun 2011 19:52:12 +1000 > > In chromium-browser, about:config doesn't work. Does it need to? On my computer with Chrome open Ctrl+O to open the file open dialog choose /home/scott/Category2.html (has various

Re (6): Configuring Iceweasel security policies.

2011-06-16 Thread peasthope
From: Camaleon Date: Thu, 16 Jun 2011 18:25:47 + (UTC) > Err... Peter, have you considered using the suggestedA1 extension? > https://addons.mozilla.org/firefox/addon/281 I had foolishly assumed it wouldn't work for Iceweasel; but it does, in Iceweasel 3.5.16 in Squeeze. Thanks! > ...

Re: Re (5): Configuring Iceweasel security policies.

2011-06-16 Thread Camaleón
On Thu, 16 Jun 2011 10:45:01 -0800, peasthope wrote: > From: Scott Ferguson Date: Thu, 16 Jun > 2011 19:52:12 +1000 (...) >> You *did* change the restrictions in Iceweasel (about:config) didn't >> you? > > That's where I started about 5 days ago. In about:config, > security.checkloaduri a

Re (5): Configuring Iceweasel security policies.

2011-06-16 Thread peasthope
From: Scott Ferguson Date: Thu, 16 Jun 2011 19:52:12 +1000 > ... lynx doesn't support xhtml by default ... w3m only support xhtml 1.0 > > Try not using an xhtml file - I suspect you are complicating your tests. Oops; thanks. The result is the same for C*.html. When lynx and w3m are given

Re: Re (4): Configuring Iceweasel security policies.

2011-06-16 Thread Scott Ferguson
On 16/06/11 12:29, peasth...@shaw.ca wrote: > From: Scott Ferguson > Date: Wed, 15 Jun 2011 23:12:59 +1000 > >> Does it work with Lynx - Konqueror, Opera, Chrome, or any other web >> browser?? > > Dalton's address is 142.103.107.137. In these tests, file:///Category2.xhtml > and file://142.10

Re (4): Configuring Iceweasel security policies.

2011-06-15 Thread peasthope
From: Scott Ferguson Date: Wed, 15 Jun 2011 23:12:59 +1000 > And your problem is that Iceweasel is stopping you from loading a file > that the user running Iceweasel has permission to read and is on the > same machine?? Yes, that happens when the file URI originates from the remote server. No

Re: Re (3): Configuring Iceweasel security policies.

2011-06-15 Thread Scott Ferguson
On 15/06/11 13:12, peasth...@shaw.ca wrote: > From: Scott Ferguson > Date: Mon, 13 Jun 2011 15:30:27 +1000 >> To clarify - is it only you that needs to be able to use this file link?? > > Yes, only me. The objective is to simplify my testing procedure. > Of course, the time I've spent to under

Re (3): Configuring Iceweasel security policies.

2011-06-14 Thread peasthope
From: Scott Ferguson Date: Mon, 13 Jun 2011 15:30:27 +1000 > To clarify - is it only you that needs to be able to use this file link?? Yes, only me. The objective is to simplify my testing procedure. Of course, the time I've spent to understand it probably outweighs the time that will be

Re: Re (2): Configuring Iceweasel security policies.

2011-06-12 Thread Scott Ferguson
On 13/06/11 09:14, peasth...@shaw.ca wrote: > From: Scott Ferguson > Date: Sun, 12 Jun 2011 20:20:17 +1000 >> Stepping through what you've described above... >> >> You saved the page to "storage of Dalton" presumably "storage" is >> somewhere below /home/peter >> >> eg.:- >> home/peter/"P

Re (2): Configuring Iceweasel security policies.

2011-06-12 Thread peasthope
From: Scott Ferguson Date: Sun, 12 Jun 2011 20:20:17 +1000 > Stepping through what you've described above... > > You are on a Dalton console. By console I mean the SVGA monitor, keyboard and mouse. It supports X11 in addition to plain CLI. > If you are *not* running as root (and why would

Re: Configuring Iceweasel security policies.

2011-06-12 Thread Scott Ferguson
On 12/06/11 12:05, peasth...@shaw.ca wrote: > * From: Scott Ferguson > * Date: Sat, 11 Jun 2011 23:23:30 +1000 > Here is my explanation again, step by step. > * I sit in front of the console of dalton. > * Using Iceweasel in Squeeze, open this. > "http://members.shaw.ca/peasthope/#Links"

Re(2): Configuring Iceweasel security policies.

2011-06-11 Thread peasthope
* From: Scott Ferguson * Date: Sat, 11 Jun 2011 23:23:30 +1000 > Now that's confusing me too! I've never had to modify anything to get a > web browser to load local files or to load links from local files > either to local links or online links. Again, we're at crossed purposes.

Re: Configuring Iceweasel security policies.

2011-06-11 Thread Scott Ferguson
On 11/06/11 06:38, peasth...@shaw.ca wrote: > From: peasth...@shaw.ca > Date: Fri, 10 Jun 2011 12:24:32 -0800 >> Appears that the instructions for the Mozilla security policies are for the >> case >> where both the file URI link comes from the same machine as the browser runs >> on. > > That wa

Re: Configuring Iceweasel security policies.

2011-06-11 Thread Scott Ferguson
On 11/06/11 06:24, peasth...@shaw.ca wrote: > After reading http://kb.mozillazine.org/Security_Policies > add these four lines to dalton:/etc/iceweasel/pref/iceweasel.js . > > // Allow my file URI to be opened. > user_pref("capability.policy.policynames", "localfilelinks"); > user_pref("capability

Re: Configuring Iceweasel security policies.

2011-06-11 Thread Camaleón
On Fri, 10 Jun 2011 12:24:32 -0800, peasthope wrote: > After reading http://kb.mozillazine.org/Security_Policies add these four > lines to dalton:/etc/iceweasel/pref/iceweasel.js . (...) > This message comes to the Iceweasel error console. Security Error: > Content at http://members.shaw.ca/peas

Re: Configuring Iceweasel security policies.

2011-06-10 Thread peasthope
From: peasth...@shaw.ca Date: Fri, 10 Jun 2011 12:24:32 -0800 > Appears that the instructions for the Mozilla security policies are for the > case > where both the file URI link comes from the same machine as the browser runs > on. That was garbled. This might make more sense. Are the ins

Configuring Iceweasel security policies.

2011-06-10 Thread peasthope
After reading http://kb.mozillazine.org/Security_Policies add these four lines to dalton:/etc/iceweasel/pref/iceweasel.js . // Allow my file URI to be opened. user_pref("capability.policy.policynames", "localfilelinks"); user_pref("capability.policy.localfilelinks.checkloaduri.enabled", "allAccess