J
John Corliss
donut said:(clipped)
Actually, as I mentioned, instead of "only selected below" and
Mozilla, I went with "any program".
donut said:(clipped)
»Q« said:This worked without setting up a local IDENT server? I wonder what
your machine is returning as an IDENT response.
That should be fine, IDENT uses only TCP.
It sounds like your ISP is running a lot of old server software. The
only time I have run into the IDENT response delay problem, it has
been with IRC servers. Opening my port 113 to the IRC server made no
difference in the delay unless I also set up an IDENT server to
respond to the incoming requests.
I'm glad you've got it worked out thanks to donut. I just wish I
were not confused about how the solutions works. ;-)
I think it is for more than just newbies. While I cannot use Kerio
2.15 as it crashes my XP box, the rules covered a lot of ad sites,
spyware, gator type stuff as well.
Sponge's lists are good for sparing me gaving to do some work myself,
while teaching me about which ports etc to block
cheers
The concept of closed vs. stealth has been beaten to death in the
security groups, with the consensus being that stealth is used to
market firewalls and it doesn't make a whole lot of difference. Some
go so far as to say that stealth is worse than closed because the
absence of a ping response tells a port scanner that something is
indeed there.
I don't subscribe to that: it seems to me that "invisible" is better
than "I'm here but not letting you in."
All I know is that I have had absolutely no problems of any kind since
learning how to use Kerio properly. That's enough for me.
I will confess that I was dumb enough to go messing around using IE
with install on demand enabled, visited a malicious site, and found
that a virus had been downloaded onto my hard disk, despite Kerio. If
the port to IE is open, anything can come through if you allow it.
donut said:And I disagree with this. All you have to do is create a rule that
allows the traffic from a specific IP.
For example:
Rule Name: Allow port 113 IDENT from POP3 server
Protocol: TCP and UDP
Direction: Incoming
Remote endpoint-
Address Type: Single address
Host address: (enter the IP of the POP3 server)
Rule valid: Always
Action: Permit
This worked without setting up a local IDENT server? I wonder what
your machine is returning as an IDENT response.
Probably deny since nothing is listening on TCP 113.
The idea of the 113 rule is such that the firewall does not do
anything at all to inbound packets addressed to port 113 . But
because no application (ie a real Indent server) is listening ,
the deny request is sent back. This is exactly the same case as if
John was not using a firewall at all. That is Without a firewall
John's machine will show up as closed on 113 anyway hence stopping
the repeat auth requests
Now I'm on stealth mode again, can FTP and get my email faster.
I've just realized why I got so confused. in
<Aaron gives a good
explanation that I think is right, but it would mean your port 113 is
not stealthed at all, just closed. If <https://grc.com/x/portprobe=
113> reports it closed, I can relax.
Well since the rule specifies only his mail server ip's he will
appear stealth to everyone else except his mail server to whom he
will appear closed. Not too bad.