1 |
On Thursday 28 May 2015 07:44:23 Meino.Cramer@×××.de wrote: |
2 |
> Mick <michaelkintzios@×××××.com> [15-05-28 07:44]: |
3 |
> > On Thursday 28 May 2015 06:11:08 Meino.Cramer@×××.de wrote: |
4 |
> > > Hi, |
5 |
> > > |
6 |
> > > With wireshark I found, that firefox accesses sites on startup, from |
7 |
> > > which I dont know, for what reason this access is needed or whether |
8 |
> > > the NSA, CIA, FBI, BDN, MOSSAD (fill in what organisation you ever |
9 |
> > > suspect to do such things) has invaded my PC. |
10 |
> > |
11 |
> > It may none of the above, but FF and any addons checking what the latest |
12 |
> > version is of themselves, as well as the Google search on the default |
13 |
> > hope page doing a DNS query or some such. |
14 |
> > |
15 |
> > > I want to block such accesses for two reasons: First is ...hmmm... |
16 |
> > > to block that accesses...second is to find out what will not work |
17 |
> > > than. |
18 |
> > > |
19 |
> > > I dont want to install and configure a complete full blown firewalled |
20 |
> > > SEL-Linux thingy here and I dont want to reboot my Linux box for every |
21 |
> > > new site I added. I am looking for a simple solution, which I can use |
22 |
> > > without studying the history of TCP/IP and others... ;))) |
23 |
> > > |
24 |
> > > What can I use for this purpose? |
25 |
> > |
26 |
> > You could try an application layer filter[1], but I think it won't work |
27 |
> > insofar the connections you observed are probably using ports and |
28 |
> > protocols same as your day to day browsing activity. Therefore you will |
29 |
> > likely need to use iptables to block individual domains or IP addresses |
30 |
> > and then regularly add to the list when the servers your browser wants |
31 |
> > to contact change in that amorphous and reconfiguring cloud out there. |
32 |
> > |
33 |
> > You don't have to reboot your box when you change rules, but you'll need |
34 |
> > to reload iptables. |
35 |
> > |
36 |
> > |
37 |
> > [1] http://l7-filter.sourceforge.net/HOWTO-kernel |
38 |
> |
39 |
> Hi Mick, |
40 |
> |
41 |
> thanks for your help ! :) |
42 |
> |
43 |
> What mechanism is recommended to be used to reinstall/initiate the |
44 |
> iptable rules while booting? Any Gentoo-ish? ;) |
45 |
|
46 |
iptables save any rules in: /var/lib/iptables/rules-save |
47 |
|
48 |
You can edit this and then run '/sbin/iptables-apply -t 90' |
49 |
|
50 |
in case you have something wrong in there and there is a risk of locking |
51 |
yourself out. |
52 |
|
53 |
Or run '/etc/init.d/iptables stop' then change /var/lib/iptables/rules-save to |
54 |
your liking and then '/etc/init.d/iptables start' |
55 |
|
56 |
|
57 |
This is for vanilla iptables (IPv4). There are other scripts available (like |
58 |
arnos-firewall) which have their own configuration files as a front end to |
59 |
iptables. |
60 |
|
61 |
-- |
62 |
Regards, |
63 |
Mick |