From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Restricting Firefox website access
Date: Sat, 17 Jan 2009 09:32:14 -0800 [thread overview]
Message-ID: <49bf44f10901170932v1351ce0bvaaf851a18a06dbc0@mail.gmail.com> (raw)
In-Reply-To: <3BC0E9C7-E397-43C8-96C1-1798ED64EBCB@stellar.eclipse.co.uk>
>> I brought this to the shorewall list for config advice, but I was told:
>>
>> a) NO PACKET FILTERING FIREWALL (which includes Shorewall) has any
>> notion of domains. So filterinG by domain is a non-starter.
>> ...
>>
>> I'd like to restrict the websites one of the computers on my network
>> can access in Firefox. It only needs to access 2 different domain
>> names and I don't want it to be able to access any others.
>
> If it's a case of only 2 domains, then the chances are that dumb filtering
> will work ok.
>
> If you allow packets from computer X with a destination port of 80 only to
> computers with the IP address 12.154.191.10 then users of computer X will be
> able to access mylittlepony.com freely and also any hardcore porn sites also
> hosted on the same webserver (12.154.191.10).
>
> I have to admit this is probably not the way I'd do it, but WHEN YOU WROTE
> IN ALL CAPITALS, I FELT COMPELLED TO REPLY TO YOU.
I was quoting the other thread. Guess I should have used [quote][/quote].
- Grant
> When I asked about content filtering a couple of months ago, everyone said
> Squid was rubbish.
>
> Actually, they ignored me. From now on, I will write all my questions in
> BLOCK CAPITALS in order to maximise my responses.
>
> But I had expected Squid + module to be the answer, and no-one mentioned it.
> A couple of clowns mentioned OpenDNS, and DansGuardian was the only serious
> reply I got, so you might want to look at that, too.
> http://www.gossamer-threads.com/lists/gentoo/user/175114
>
> I really should be implementing this internet filtering this weekend.
>
> Cheers,
>
> Stroller.
next prev parent reply other threads:[~2009-01-17 17:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 21:44 [gentoo-user] Restricting Firefox website access Grant
2009-01-07 21:54 ` Paul Hartman
2009-01-08 20:57 ` Kyle Bader
2009-01-09 18:40 ` Grant
2009-01-09 19:05 ` Alan McKinnon
2009-01-09 19:32 ` Grant
2009-01-09 20:58 ` Kyle Bader
2009-01-09 21:07 ` Nick Cunningham
2009-01-09 21:23 ` Alan McKinnon
2009-01-10 10:14 ` Peter Humphrey
2009-01-10 14:35 ` Matt Causey
2009-01-10 17:50 ` Grant
2009-01-10 19:35 ` Matt Causey
2009-01-10 5:18 ` Mike Kazantsev
2009-01-10 17:48 ` Grant
2009-01-11 2:05 ` Mike Kazantsev
2009-01-11 2:27 ` Grant
2009-01-13 19:33 ` Mick
2009-01-14 1:52 ` Mike Kazantsev
2009-01-17 5:34 ` Grant
2009-01-17 6:30 ` Mike Kazantsev
2009-01-17 9:50 ` Peter Humphrey
2009-01-17 8:47 ` Alan McKinnon
2009-01-17 18:12 ` Grant
2009-01-17 18:21 ` Alan McKinnon
2009-01-17 18:53 ` Matt Harrison
2009-01-17 18:24 ` Grant
2009-01-17 15:43 ` Stroller
2009-01-17 16:32 ` [gentoo-user] " Harry Putnam
2009-01-17 17:40 ` Grant
2009-01-17 19:02 ` Harry Putnam
2009-01-17 17:32 ` Grant [this message]
2009-01-23 11:04 ` [gentoo-user] " Matt Causey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49bf44f10901170932v1351ce0bvaaf851a18a06dbc0@mail.gmail.com \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox