On Tuesday 02 January 2001 00:55, you wrote:
On Sun, 31 Dec 2000, Dennis Myers wrote:
Should be in /var/log/messages
You can also take a look at /etc/portsentry.history to see what ended up
being blocked.
Hi again everyone, this has been puzzling me for a while. I have
portsentry
On Sun, 31 Dec 2000, Dennis Myers wrote:
Should be in /var/log/messages
Hi again everyone, this has been puzzling me for a while. I have portsentry
installed and configured on two machines (in conjunction with pmfirewall) and
have not been able to determine where to look for reports on possible
In the standard configuration it sends all reports to /var/log/messages. Unless you
changed the logging facility which it uses during the configuration all your
portsentry reports should be listed there. I understand that there is a way to
redirect it's reports but I have been unable to get it
John Wheat wrote:
I have installed and configured portsentry to my likings but after following
the tutorial at www.linuxnewbie.org/nhf/intel/security/portsentry1.html and
adding the lines /usr/local/psionics/portsentry/portsentry -atcp
/usr/local/psionic/portsentry/portsentry -udp the
ed wrote:
Hi all I was wondering does anyone here use portsentry cause I have it on my
boxx and it works fine except for the wav.file that is supposed to warn me
when someone scans me the ip is blocked and put in the host.deny file but I
never hear the wav.file does anyone here know how I
Mark Weaver wrote:
Definately! I'm all ears...rather I'm all eyes since I can't see with my
ears. My wife would tell you that when I'm sitting in front of this
monitor I can't hear with my ears either! :)
Mine used to say that too but she was always referring to the newpaper
or the
Greg Stewart wrote:
Hell, I'm so blind (and probably deaf, too) my co-workers think the only way
I can see what's on a computer screen is by smelling the damned thing!
--Greg
Sorry to butt in on this thread - Greg, but (sic), that takes "scratch and
sniff" to a whole new level! smile
PS
A good start would be to report them to your ISP.
--
Mark
/* I never worry about the to-jams.
* Once I've stuck my foot in my mouth
* it's already too late...just make sure
* you chew them thoroughly before swallowing!
*/
Registered Linux user #182496
Definately! I'm all ears...rather I'm all eyes since I can't see with my
ears. My wife would tell you that when I'm sitting in front of this
monitor I can't hear with my ears either! :)
--
Mark
/* I never worry about the to-jams.
* Once I've stuck my foot in my mouth
* it's
My wife would tell you that when I'm sitting in front of this
monitor I can't hear with my ears either! :)
Hell, I'm so blind (and probably deaf, too) my co-workers think the only way
I can see what's on a computer screen is by smelling the damned thing!
--Greg
- Original Message -
John; The sound was also used in "Hudson Hawk" with Bruce Willis. I remember
the "Our Man Flint" movies as well ! Anyway the sound was used for the
electronic handcuffs in the show. Maybe That info will help ? Have U tried "
www.freethemes.com " ?? Check out the "Unix Themes" section, dude.
L 8
Portsentry usually adds the offending host IP to the route tables, but this
isn't always the best option anymore. you can change the KILL_ROUTE command
in /usr/local/psionic/portsentry/portsentry.conf to the following and it
will add the host IP to your ipchains rules (if you're using
Dan LaBine wrote:
John; The sound was also used in "Hudson Hawk" with Bruce Willis. I remember
the "Our Man Flint" movies as well ! Anyway the sound was used for the
electronic handcuffs in the show. Maybe That info will help ? Have U tried "
www.freethemes.com " ?? Check out the "Unix
Greg Stewart wrote:
Portsentry usually adds the offending host IP to the route tables, but this
isn't always the best option anymore. you can change the KILL_ROUTE command
in /usr/local/psionic/portsentry/portsentry.conf to the following and it
will add the host IP to your ipchains rules
?? What/why would a socks proxy port port be probed ??
Socks is a network proxy protocol used to provide NAT access for one section
of a network to another. It is possible that the machine from which the
packets came is hitting you or everyone (I haven't seen your packet log
entry, so I can't
John Rye wrote:
Greg Stewart wrote:
Portsentry usually adds the offending host IP to the route tables, but this
isn't always the best option anymore. you can change the KILL_ROUTE command
in /usr/local/psionic/portsentry/portsentry.conf to the following and it
will add the host IP to
Greg Stewart wrote:
?? What/why would a socks proxy port port be probed ??
Socks is a network proxy protocol used to provide NAT access for one section
of a network to another. It is possible that the machine from which the
packets came is hitting you or everyone (I haven't seen your
If you do a whois on the network IP's and can actually resolve some owner of
the network to which these IP's belong, you might drop them a note about
their clients' broadcasting...if they belong to your ISP's subscribers,
contact your technical support.
You won't necessarily get anything done,
Greg Stewart wrote:
If you do a whois on the network IP's and can actually resolve some owner of
the network to which these IP's belong, you might drop them a note about
their clients' broadcasting...if they belong to your ISP's subscribers,
contact your technical support.
You won't
Why, what did you do to the config files that's making portsentry complain?
I've never had a problem editing the config files in portsentry, and it's
never complained about a single thing I've done.
Be more specific about the problem you're experiencing and maybe we can walk
through a
Vic [EMAIL PROTECTED] on 09/13/2000 09:53:42 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL
Vic this is Charley, sorry for using your computer without asking,
I forgot my password and you were
not here when I got back from class.
Dude, its cool man just sit back, and
drink a pop, have a smoke, I looked at
the config files, they look all ok _except_ the
Makefile, and from the looks of
22 matches
Mail list logo
