does anybody have any idea how to resolve this?
thanks..
kalin m wrote:
hi all...
after setting up a pf rule set on one of newly installed freebsd 7 i
did a scan with nessus 3 on that machine
the result i got was like this one:
http://www.nessus.org/plugins/index.php?view=singleid=11618
kalin m a écrit :
does anybody have any idea how to resolve this?
thanks..
kalin m wrote:
hi all...
after setting up a pf rule set on one of newly installed freebsd 7 i
did a scan with nessus 3 on that machine
the result i got was like this one:
On Aug 7, 2008, at 11:33 AM, kalin m wrote:
does anybody have any idea how to resolve this?
thanks..
kalin m wrote:
hi all...
after setting up a pf rule set on one of newly installed freebsd 7
i did a scan with nessus 3 on that machine
the result i got was like this one:
i have that in i still get that message from nessus... maybe
synproxy or something like S/SAF?!
FreeBSD wrote:
kalin m a écrit :
does anybody have any idea how to resolve this?
thanks..
kalin m wrote:
hi all...
after setting up a pf rule set on one of newly installed freebsd
thanks... or something like it... i'll try...
Chuck Swiger wrote:
On Aug 7, 2008, at 11:33 AM, kalin m wrote:
does anybody have any idea how to resolve this?
thanks..
kalin m wrote:
hi all...
after setting up a pf rule set on one of newly installed freebsd 7 i
did a scan with nessus 3
kalin m wrote:
does anybody have any idea how to resolve this?
[snip]
Not without a lot more information. But I may be able to fathom some wild
guess, generically speaking.
Only allow connections to set up like this:
pass out quick on $ExtIF inet proto tcp all flags S/SA keep state
pass
hi all...
after setting up a pf rule set on one of newly installed freebsd 7 i did
a scan with nessus 3 on that machine
the result i got was like this one:
http://www.nessus.org/plugins/index.php?view=singleid=11618
how do 'fix' it using pf?...
thanks...
