Hello John,
On Fri, 6 Jan 2012 02:33:37 -0800 (PST) John Doe wrote:
> From: wwp
>
> > On Thu, 5 Jan 2012 08:00:29 -0800 (PST) John Doe wrote:
> >> Try to google "firefox parental control" and click on the first
> > result... ^_^
> > This assertion is not reliable, unless you did it intent
From: wwp
> On Thu, 5 Jan 2012 08:00:29 -0800 (PST) John Doe wrote:
>> Try to google "firefox parental control" and click on the first
> result... ^_^
> This assertion is not reliable, unless you did it intentionally? Results
> brought by googles are not the same here and there..
Yes, it was
On 01/05/2012 05:11 PM, wwp wrote:
> Hello John,
>
>
> On Thu, 5 Jan 2012 08:00:29 -0800 (PST) John Doe wrote:
>
>> From: Marko Vojinovic
>>
>>> Shouldn't there be a firefox plugin, or something similar, that would take
>>> care of all this? I cannot believe that "parental control software" is
>>>
Hello John,
On Thu, 5 Jan 2012 08:00:29 -0800 (PST) John Doe wrote:
> From: Marko Vojinovic
>
> > Shouldn't there be a firefox plugin, or something similar, that would take
> > care of all this? I cannot believe that "parental control software" is
> > something so uncommon... :-)
>
> Try t
It won't help more than /etc/hosts entries, but I've found using OpenDNS
with a free account and a script / client to keep the IP in sync to be very
effective. DNS redirects can be applied categorically or with a per domain
blacklist. The metrics and charts are interesting too, on a nicely basis
o
From: Marko Vojinovic
> Shouldn't there be a firefox plugin, or something similar, that would take
> care of all this? I cannot believe that "parental control software" is
> something so uncommon... :-)
Try to google "firefox parental control" and click on the first result... ^_^
JD
On Thursday 05 January 2012 01:39:49 Ljubomir Ljubojevic wrote:
> On 01/05/2012 12:58 AM, Marko Vojinovic wrote:
> > I am looking at the simplest (implementation-wise) solution to the
> > following problem (on CentOS 6.2):
> >
> > I have a list of web addresses (like http://www.example.com,
> > ht
On Thursday 05 January 2012 11:16:05 Ljubomir Ljubojevic wrote:
> On 01/05/2012 01:21 AM, Marko Vojinovic wrote:
> > On Wednesday 04 January 2012 18:04:43 Frank Cox wrote:
> >> On Wed, 04 Jan 2012 23:58:17 + Marko Vojinovic wrote:
> >>> The point is that I need a simple, easy-to-implement,
> >>
On 01/05/2012 01:21 AM, Marko Vojinovic wrote:
> On Wednesday 04 January 2012 18:04:43 Frank Cox wrote:
>> On Wed, 04 Jan 2012 23:58:17 + Marko Vojinovic wrote:
>>> The point is that I need a simple, easy-to-implement, easy-to-configure
>>> and easy-to-maintain solution for this particular usec
On 01/05/2012 12:58 AM, Marko Vojinovic wrote:
>
> I am looking at the simplest (implementation-wise) solution to the following
> problem (on CentOS 6.2):
>
> I have a list of web addresses (like http://www.example.com, https://1.2.3.4/,
> etc.) that should be "forbidden" to access from a particula
On Wednesday 04 January 2012 18:04:43 Frank Cox wrote:
> On Wed, 04 Jan 2012 23:58:17 + Marko Vojinovic wrote:
> > The point is that I need a simple, easy-to-implement, easy-to-configure
> > and easy-to-maintain solution for this particular usecase.
>
> Put the disallowed addresses into your /
I am looking at the simplest (implementation-wise) solution to the following
problem (on CentOS 6.2):
I have a list of web addresses (like http://www.example.com, https://1.2.3.4/,
etc.) that should be "forbidden" to access from a particular host. On access
attempt, the browser should be redir
12 matches
Mail list logo
