Re: Alternatives to using a Personal Firewall
- From: zzy <anon@xxxxxxxxxxx>
- Date: Thu, 29 Jun 2006 01:27:51 -0700
B. Nice wrote:
> On Wed, 28 Jun 2006 19:26:47 -0700, zzy <anon@xxxxxxxxxxx> wrote:
> . . .
You just need to disable those services that are in a network
listening state and that You don't need. I would like to be able to
post links to good step-by-step guides but haven't done much googling
for english ones. I have some very good guides that even a novice can
use to harden his/her machine in less than half an hour. But
unfortunately they are in my native language.
How do I tell which ones are in a network listening state?
My main machine is behind a hardware router and is on all day every day. So far, nothing malicious has gotten in. So I'm satisfied with the security the router provides. Like some other folks who've commented here, I like to know what's "phoning home" and often prohibit it -- Windows Media Player, Windows Genuine Advantage Notification (every time I boot), PGP Tray, Real Player, and on and on. Windows (the MS DTC Console) even tries to call home every time I compile a VB program. This is maybe not a security issue, but neither is closing my window shades at night when everybody walking by can look in -- and I do that, too. A number of desktop firewalls give me the ability to stop at least some of this "phoning home".
For me that does'nt make sense. If I don't trust the program vendor to
be serious about my privacy I will not allow it on my machine.
Very noble. But Microsoft, for example, certainly isn't serious about users' privacy considering that the "Genuine Advantage Notification", MS DTC Console, Media Player, and other of their products phone home regularly without permission. I could be pure and stand on principle as you do and not allow any Microsoft software on my machine. (You must not have any on yours.) But I'm not willing to sacrifice my livelihood, which is primarily developing and selling Windows software, in order to be noble.
As PFW's are concerned, I personally would'nt install a big chunk of
code just to be able to control "home phoning".
Again we differ in some basic values. But a question: How do you detect when an application or operating system component "phones home" without your permission, indicating that the vendor isn't serious about your privacy? I assume you don't use a PFW for this purpose, so what method do you use? I'd be happy to try it myself in place of the PFW.
However, if it makes sense to You, that's fine. We are all different.
As long as people don't put it into a security context claiming that
they will prevent malware from doing nasty stuff it's fine with me.
When malware is already run, damage is done. No matter what people claim. The hard but real trick is to prevent it in the first place.
. . .
Thanks again for all the help and good advice.
.
- Follow-Ups:
- Re: Alternatives to using a Personal Firewall
- From: B . Nice
- Re: Alternatives to using a Personal Firewall
- From: B . Nice
- Re: Alternatives to using a Personal Firewall
- From: B . Nice
- Re: Alternatives to using a Personal Firewall
- References:
- Alternatives to using a Personal Firewall
- From: B . Nice
- Re: Alternatives to using a Personal Firewall
- From: zzy
- Re: Alternatives to using a Personal Firewall
- From: B . Nice
- Alternatives to using a Personal Firewall
- Prev by Date: Re: not listening
- Next by Date: What are these vulnerabilities caused by personal firewalls?
- Previous by thread: Re: Alternatives to using a Personal Firewall
- Next by thread: Re: Alternatives to using a Personal Firewall
- Index(es):
Relevant Pages
|