public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Restricting Firefox website access
Date: Sat, 17 Jan 2009 10:47:04 +0200	[thread overview]
Message-ID: <200901171047.05040.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <49bf44f10901162134o79953e71y393c6a340c398dbe@mail.gmail.com>

On Saturday 17 January 2009 07:34:59 Grant wrote:
> >> That sounds good, how can I do that?
> >
> > iptables module "owner" handles that stuff, just "man iptables" if
> > you'll have any trouble.
> >
> >  iptables -A OUTPUT -m owner --uid-owner someuser -m tcp --dport http -j
> > REJECT
>
> 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.
>
> b) When referring to packet filters, filtering by user id (e.g., root)
> can only be done for connections originating from the firewall. See "man
> shoreall-rules" and read about the USER/GROUP column.
>
> Here was my original request:
>
> 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.  I can
> restrict it at the router if necessary because the router is a Gentoo
> system.
>
> I think this leaves a squid proxy setup as my only option?

Restrict by source AND destination IP

This requires only that the computer in question has a static IP or a 
permanent lease (so you always know what it is), and you know the IP of the 
web sites to be accessed (dig is a very good friend). Allow these, deny 
everything else to destination port 80.


-- 
alan dot mckinnon at gmail dot com



  parent reply	other threads:[~2009-01-17  8:48 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 [this message]
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                 ` [gentoo-user] " Grant
2009-01-23 11:04                 ` 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=200901171047.05040.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@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