"David Taylor" <djtaylor@bigfoot.com> wrote in message
news:MPG.1d9fb773cca6de64989e57@news.cable.ntlworl d.com...
>> using. But until now, I was not aware of how powerful of a solution IPsec
>> is
>> and its ability to be used in a FW like manner to stop inbound or
>> outbound
>> traffic by port, protocol or IP and nothing is coming past it *NOTHING*
>> which would make BlackIce react.
>
> It's not new Duane. All you're doing is blocking traffic by port. I'm
> surprised that it's new to you.

MOOT

>
> The main advantage of IPSec is the Sec part, i.e. security. Simply
> creating filters and a filter action like you are doing is the very very
> simplest start. What the original poster wanted was security which to
> do properly requires a PKI implementation. Then you get mutual
> authentication and encryption, none of which you have right now.

Who cares about what the OP is talking about? This goes back to last week
between you and I..

>
>> I am very impressed with IPsec and its ability to supplement in a FW like
>> manner. <g>
>
> Being doing that for ages, it's not new but it does have value, it's
> just not the friendliest interface for noddies to configure and it
> doesn't provide any stateful inspection or application inspection but
> yes, if all you want to do is set up block/allow filters, it's fine.

I been using it for a couple of years and that's after someone made me aware
of it so how can it be new to me? I have made posts about using IPsec as a
supplement for a couple of years so how can it be new to me? Hell, people
who look for solutions in securing machines and that's their job don't know
about using IPsec and it's ability until I inform them about it. I already
know about IPsec statefulness and other short comings. After all, IPsec is
not FW software but can act in limited FW like manner to protect the Windows
NT based O/S like Win 2K and up as a supplemetal solution..

IPsec was not introduced to the Windows NT based O/S until Win 2K so that
someone could use it as a possible solution particularly in the home or on
the road situations. Many, many, many, many users of the WIN 2K and up
O/S(s) are not aware that it's even there. And many users *bitch* about the
XP O/S FW not being able to stop outbound traffic .However, with the use of
IPsec on the machine with the XP FW, IPsec can be used to supplement the XP
FW and stop outbound traffic if need be.
>
>> But just keep in mind I am not a guru like you are, and therefore, you
>> can
>> kiss my *ASS* about IPsec and anything else for that matter with your
>> *tounge* hanging out. <vbg>
>
> No need but keep reading, you'll learn as you go along. It fascinates
> me why you post what you do sometimes.

What? Am I going to learn something from you? LOL I doubt it seriously. <g>

What's the fascination? I have been doing it for years on the Internet for
those I do not *RESPECT*. So guess what I don't have for you? <g> and <EOR>

>
> Just remember, IPSec is an IP only solution, if you have NWLink or
> NetBEUI installed and bound, you might just as well hand your PC over to
> Mr Hacker.

I think I mentioned the word *supplement* several times in my original post
and on the post where you started going to left field.on NWLink and NetBIOS.

Maybe, you need to look up the word *supplement* and the meaning of the
word, since you're such the guru and I might add an
*university/college/boy -- ass-wipe*. <g> and <EOR>

Why would someone need NetBEUI and NWLink on a dialup? However, some ISP(s)
would bind NetBEUI on WIN 2K and down when installing its software like
Netzero a few years back and one knew to unbind it And one uses NWLink in
a LAN situation if needed with something like a router setting there and
possibly IPsec as a *supplemental* solution.

And besides if some end user that does understand how to make filtering
rules on any type of FW such as a PFW solution, then IPsec is a piece of
cake with the use of the AnalogX rules.

Really, I am not posting about IPsec to you in particular but you do need
your ass kicked about it up in my face with your *Bull Shit*. The post was
for others who may be reading this post between you and I and understand
that there is another element on the Win 2K and up O/S that can be used in a
supplemental fashion to protect the machine and it can protect by port,
protocol and IP inbound or outbound and is a powerful supplemental tool
that can be used that has been made easy to use by using the AnalogX SecPol
rules.

Users are not aware of IPsec sitting on the O/S and what it can do in the
protection of the Windows NT based O/S.

I have seen posts about IPsec being used as the only solution to protect the
machine as a FW. <g>
..