KT> Kind of the same, but I just write one line, looks like a normal RA
 KT> entry 

as long as it does what you need it to do, it is great! ;)

 KT> Seems like NetFoss puts strangnes in the *R for resolved name some
 KT> times, so I want to address that before I make it available.

if i might speak as a network security admin and specialist for a moment...

do not trust dns resolved hostnames... by that, i mean that IPs can't be faked
not and have the connection work... IPs are the only truth to where the
connection is coming from... the resolved names can easily be faked if one has
control over their DNS...

to elaborate on that, i have systems trying to drop spam off here... some of
them return "localhost" as the resolved name when i do a lookup... their
intention is to confuse me and make me think that my own system is trying to
do the spamming... some others return "." which doesn't say much of
anything... i've seen other stuff, too, which just isn't right and shouldn't
be being done... given some time, i can easily provide examples of IPs which
you can lookup and see what they return ;)

if it is possible to disable netfoss' hostname lookups, i would most likely do
so... mainly to speed up the connection instead of having to wait on the rdns
to complete... but also for the above reason... i learned that lesson not only
from spammers but also others trying to hack into my web server years ago...
they do the same thing and at the time i was recording the FQDN that was
returned... i finally turned that off and started recording only IP numbers
and the real culprits were revealed...

 KT> It's nothing fancy, just something I wanted in my logs. and the 
 KT> IP0n does change to refect the *N  

good deal :)

)\/(ark

 * Origin: North American RemoteAccess Support 919-774-5930 (1:3634/12)