[konqueror] blacklisting a site

Beginner

Wednesday, July 14th 2004, 1:35pm

Did some one notice that most of the adds on web sites are coming from a different domain.

Since I am almost always browsing the same sites, I d like to make a blacklist in konq for these sites.

Another way to make it work would be to set a firewall rule, but I think it s not the right way to do it fot it would affect all users ....

I tried once M$ win server 2003, and white lists and blacklist are enabled as a default.

PeP

Go to the top of the page

cmbofh

Intermediate

Posts: 539

2

Wednesday, July 14th 2004, 4:31pm

Re: [konqueror] blacklisting a site

Quoted

Original von pep

Did some one notice that most of the adds on web sites are coming from a different domain.

Since I am almost always browsing the same sites, I d like to make a blacklist in konq for these sites.

Another way to make it work would be to set a firewall rule, but I think it s not the right way to do it fot it would affect all users ....

I tried once M$ win server 2003, and white lists and blacklist are enabled as a default.

I'd recommend using a filtering proxy like privoxy (http://www.privoxy.org).
Another easy way is entering the offending hosts to the /etc/hosts file.
For example, putting

127.0.0.1 nuisance.com

there will redirect any requests for nuisance.com to your local system.
So they will fail.

Go to the top of the page

pep

Beginner

Posts: 16

3

Wednesday, July 14th 2004, 4:42pm

using a proxy is not allowed where I work (we do not have access to some ip address)

well using hosts should be fine and as easy as making a new firewall rule, but I would like to do it without having to log as root / sudo.

PeP

Go to the top of the page

anda_skoa

Professional

Posts: 1,273

Location: Graz, Austria

Occupation: Software Developer

4

Wednesday, July 14th 2004, 5:06pm

Quoted

Original von pep

using a proxy is not allowed where I work (we do not have access to some ip address)

You could run a locally installed proxy.
That would have the advantage that it works for all browsers.

Cheers,
_

Qt/KDE Developer
Debian User

Go to the top of the page

pep

Beginner

Posts: 16

5

Wednesday, July 14th 2004, 6:08pm

Well thanks all for these ideas.

I am a little disappointed since it seems to be quite basic and could be done in user space without needing to be root to add/del (ban/unban) a domain.

None of these solution allows different users to have different settings.

And some of them even require to restart the network.

PeP

Go to the top of the page

cmbofh

Intermediate

Posts: 539

6

Wednesday, July 14th 2004, 6:15pm

Quoted

Original von pep

Well thanks all for these ideas.

I am a little disappointed since it seems to be quite basic and could be done in user space without needing to be root to add/del (ban/unban) a domain.

None of these solution allows different users to have different settings.

And some of them even require to restart the network.

AFAIK *none* of the above is true for a local privoxy.
(I'm not saying it's possible without tweaking, and I haven't tried, though)

Go to the top of the page

cmbofh

Intermediate

Posts: 539

7

Wednesday, July 14th 2004, 6:21pm

Quoted

Original von pep

using a proxy is not allowed where I work (we do not have access to some ip address)

A HTTP proxy behind your firewall doesn't give you access to IPs that you wouldn't have access to otherwise. I guess your firewall admins mean tunnelling protocols through open ports is disallowed, no?

Go to the top of the page

pep

Beginner

Posts: 16

8

Wednesday, July 14th 2004, 6:49pm

Quoted

A HTTP proxy behind your firewall doesn't give you access to IPs that you wouldn't have access to otherwise. I guess your firewall admins mean tunnelling protocols through open ports is disallowed, no?

well , we have no access to most of known proxy IP's

PeP

Go to the top of the page

cmbofh

Intermediate

Posts: 539

9

Wednesday, July 14th 2004, 7:00pm

Quoted

Original von pep

Quoted

A HTTP proxy behind your firewall doesn't give you access to IPs that you wouldn't have access to otherwise. I guess your firewall admins mean tunnelling protocols through open ports is disallowed, no?

well , we have no access to most of known proxy IP's

The proxy I'm talking about would have the IP 127.0.0.1 (localhost), for example. I mean a proxy on *your* side of the firewall, not a (for example anonymizing) proxy somewhere in the internet.

Just think of it as an add-on software to your browser, something you install and configure on your local machine...