From: Jim Scott on
I used to use Outpost(Free) on W98se, but when I install it on XPpro SP2 it
just blocks everything even if I tell it to trust email/news/browser etc.
Does it not work with XP?
--
Jim
Tyneside UK
From: Volker Birk on
Jim Scott <mr.jimscott(a)xvirgin.net> wrote:
> I used to use Outpost(Free) on W98se, but when I install it on XPpro SP2 it
> just blocks everything even if I tell it to trust email/news/browser etc.
> Does it not work with XP?

You don't need Outpost. Just use the Windows-Firewall.

Yours,
VB.
--
"Es kann nicht sein, dass die Frustrierten in Rom bestimmen, was in
deutschen Schlafzimmern passiert".
Harald Schmidt zum "Weltjugendtag"
From: Jim Scott on
On 30 Aug 2005 10:58:50 +0200, Volker Birk wrote:

> Jim Scott <mr.jimscott(a)xvirgin.net> wrote:
>> I used to use Outpost(Free) on W98se, but when I install it on XPpro SP2 it
>> just blocks everything even if I tell it to trust email/news/browser etc.
>> Does it not work with XP?
>
> You don't need Outpost. Just use the Windows-Firewall.
>
> Yours,
> VB.

That's what I have been doing, but SOME firewall checkers indicate port not
stealthed. Does that matter. Outpost always indicated all were invisible.
--
Jim
Tyneside UK
From: Duane Arnold on
>
> That's what I have been doing, but SOME firewall checkers indicate
> port not stealthed. Does that matter. Outpost always indicated all
> were invisible.

No, I don't think it matters. What counts is that the port is closed. The
stealth thing is a personal FW term that's hyped up. I myself would much
rather have the port closed and an response sent back that the port is
closed and have a scan move on as opposed stealthed and closed with
nothing sent back, which to me is also and indication that something is
there due to the non response. I don't think stealth buys you anything.
And some clueless hacker may try to lock on and hammer instead of getting
the response back all ports are closed and just moves on.

You want the machine to be stealthed, put the machine behind a packet
filtering FW router -- then it's stealthed as unsolicited inbound traffic
never reaches the machine for it to respond.

The only thing that the XP FW cannot do is stop outbound traffic but you
can stop inbound or outbound by port, protocol or IP with IPsec to
supplement the XP FW.

http://www.petri.co.il/block_ping_traffic_with_ipsec.htm
http://support.microsoft.com/?id=813878
http://www.analogx.com/contents/articles/ipsec.htm

Duane :)




From: Jim Scott on
On Tue, 30 Aug 2005 10:43:33 GMT, Duane Arnold wrote:

>>
>> That's what I have been doing, but SOME firewall checkers indicate
>> port not stealthed. Does that matter. Outpost always indicated all
>> were invisible.
>
> No, I don't think it matters. What counts is that the port is closed. The
> stealth thing is a personal FW term that's hyped up. I myself would much
> rather have the port closed and an response sent back that the port is
> closed and have a scan move on as opposed stealthed and closed with
> nothing sent back, which to me is also and indication that something is
> there due to the non response. I don't think stealth buys you anything.
> And some clueless hacker may try to lock on and hammer instead of getting
> the response back all ports are closed and just moves on.
>
> You want the machine to be stealthed, put the machine behind a packet
> filtering FW router -- then it's stealthed as unsolicited inbound traffic
> never reaches the machine for it to respond.
>
> The only thing that the XP FW cannot do is stop outbound traffic but you
> can stop inbound or outbound by port, protocol or IP with IPsec to
> supplement the XP FW.
>
> http://www.petri.co.il/block_ping_traffic_with_ipsec.htm
> http://support.microsoft.com/?id=813878
> http://www.analogx.com/contents/articles/ipsec.htm
>
> Duane :)

The only thing that bothers me is that http://www.hackerwatch.org/probe/
tells me that port 80 is open and insecure as does a-squared while others
including Shields-Up tell me all is fine.
I am on ADSL broadband if that has any bearing.
--
Jim
Tyneside UK