--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hello,
Yes we are *ALL* interested in your crap. So please email everyone with
your street address so we can all come to your house and show you our
appreciation!
As for relavency goes it is relavent. Relavent as in how can we block
this crap from the list.
Ed
-Original Message-
Hello,
Yes we are *ALL* interested in your crap. So please email everyone with
your street address so we can all come to your house and show you our
appreciation!
As for relavency goes it is relavent. Relavent as in how can we block
this crap from the list.
Ed
-Original Message-
I have run chkrootkit and get
Anyone have a d/l site for the deb package of this?
Ed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I have run chkrootkit and get
Anyone have a d/l site for the deb package of this?
Ed
Hello,
Last night some interesting logs came to my inbox from a clients firewall
box.
Nov 21 23:20:05 system name sshd[11534]: Disconnecting: crc32 compensation
attack: network attack detected
This went on for a period of time until I went into the box retrieved the ip
address of the person
Message-
From: Alvin Oga [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 22, 2001 10:03 AM
To: Wichert Akkerman
Cc: [EMAIL PROTECTED]
Subject: Re: some interesting attacks
hi ya
Previously Ed Street wrote:
Any input/thoughts on this?
Just that it's always amusing to watch
Hello,
Last night some interesting logs came to my inbox from a clients firewall
box.
Nov 21 23:20:05 system name sshd[11534]: Disconnecting: crc32 compensation
attack: network attack detected
This went on for a period of time until I went into the box retrieved the ip
address of the person and
Message-
From: Alvin Oga [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 22, 2001 10:03 AM
To: Wichert Akkerman
Cc: debian-security@lists.debian.org
Subject: Re: some interesting attacks
hi ya
Previously Ed Street wrote:
Any input/thoughts on this?
Just that it's always amusing
Hey,
Is
there *anything* we can do about all this Spam that's getting on this
list?
Ed
-Original Message-From: HotDeals
[mailto:[EMAIL PROTECTED]]Sent: Friday, November 09, 2001 3:01
AMTo: [EMAIL PROTECTED]Subject: INSURE
GOOD RECEPTION! VITAL EMERGENCY STRATEGY!!!
To: [EMAIL PROTECTED]
Subject: Re: SPAM was RE: INSURE GOOD RECEPTION! VITAL EMERGENCY
STRATEGY!!!
On Friday 09 November 2001 16:43 pm, Sebastiaan wrote:
High,
On Fri, 9 Nov 2001, Ed Street wrote:
Hey,
Is there *anything* we can do about all this Spam that's getting on
this
list
Hey,
Is
there *anything* we can do about all this Spam that's getting on this
list?
Ed
-Original Message-From: HotDeals
[mailto:[EMAIL PROTECTED]Sent: Friday, November 09, 2001 3:01
AMTo: debian-security@lists.debian.orgSubject: INSURE
GOOD RECEPTION! VITAL EMERGENCY
-security@lists.debian.org
Subject: Re: SPAM was RE: INSURE GOOD RECEPTION! VITAL EMERGENCY
STRATEGY!!!
On Friday 09 November 2001 16:43 pm, Sebastiaan wrote:
High,
On Fri, 9 Nov 2001, Ed Street wrote:
Hey,
Is there *anything* we can do about all this Spam that's getting
Hello,
www.freshmeat.net
Or if your running debian do an apt-get install ssh (most recommended)
Ed
-Original Message-
From: Osvaldo Mundim Junior [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 07, 2001 7:47 AM
To: [EMAIL PROTECTED]
Subject: Re: Which ssh should I have?
Hello,
www.freshmeat.net
Or if your running debian do an apt-get install ssh (most recommended)
Ed
-Original Message-
From: Osvaldo Mundim Junior [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 07, 2001 7:47 AM
To: debian-security@lists.debian.org
Subject: Re: Which ssh should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
You are on a public forum called debian security. Please see the
bottom of this email for removal instructions. You was not added
without your permission as you had to reply to the email message, and
fyi it's not considered Spam in this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Already sent mail to the list admin on the bottom of each email.
Ed
- -Original Message-
From: Jakub Jankowski [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2001 11:19 PM
To: debian-security@lists.debian.org
Subject: Layne (was:
?)
Ed Street [EMAIL PROTECTED] said:
Hello,
Already sent mail to the list admin on the bottom of each email.
I just submitted his address in at
http://www.debian.org/MailingLists/unsubscribe to be unsubscribed,
hopefully that will work...
- --paulv
-BEGIN PGP SIGNATURE-
Version
Hello,
#
# LOG level option. NOTE klogd reflects these values for console broadcast
# Simply start klogd with -c 4 to ONLY display errors and above on the
console.
LOG_LEVEL=notice
#define KERN_EMERG 0 /* system is unusable
Hello,
#
# LOG level option. NOTE klogd reflects these values for console broadcast
# Simply start klogd with -c 4 to ONLY display errors and above on the
console.
LOG_LEVEL=notice
#define KERN_EMERG 0 /* system is unusable
Hello,
that's simple ;) If they was stable/non-exploitable then we'd be using rpc
inplace of ssh ;)
Ed
-Original Message-
From: Jacob Meuser [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 8:41 AM
To: [EMAIL PROTECTED]
Subject: Re: strange log entry
On Thu, May 24, 2001 at
Hello,
Make sure you have klogd and syslogd running.
Ed
-Original Message-
From: Paul Dossett [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 12:00 PM
To: [EMAIL PROTECTED]
Subject: Problem with logging firewall packets
Hi guys/gals,
Okay, I'm *really* embarrassed about
Hello,
anyone know why I get this when I post anything to this list?
Fatal Error: \n \nQuota for user [EMAIL PROTECTED] exceeded! \n \nOriginal
message follows: \n \n
it's from their mail delivery subsystem.
Ed
-Original Message-
From: Ed Street [mailto:[EMAIL PROTECTED]]
Sent
Hello,
there's several methods to tell that.
a) use a product like portsentry
b) use iptables/ipchains to reject all forms of portscans
c) don't connect the box to the inet as portscans are a fact of life ;)
portsentry will trashcan any system that attempts to portscan you. If your
using
PROTECTED]]
Sent: Thursday, May 24, 2001 8:11 PM
To: [EMAIL PROTECTED]
Subject: RE: detecting portscanning
Ed == Ed Street [EMAIL PROTECTED] writes:
Ed
Ed iptables has an awsome mechanism for portscans ;) in fact you
Ed can set it up so that all portscans (well most I should say)
Ed
Hello,
Well first off WHY are you running the rpc stuff? (i.e. I can root a redhat
6.x box in under 30 seconds with a rpc exploit from a clean install) Turn
that stuff OFF.
Ed
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 24, 2001 1:08 AM
PROTECTED]
Sent: Thursday, May 24, 2001 4:34 AM
To: debian-security@lists.debian.org
Subject: Re: strange log entry
On Thu, May 24, 2001 at 01:24:50AM -0400, Ed Street wrote:
Hello,
Well first off WHY are you running the rpc stuff? (i.e. I can root a
redhat
6.x box in under 30 seconds with a rpc
Hello,
that's simple ;) If they was stable/non-exploitable then we'd be using rpc
inplace of ssh ;)
Ed
-Original Message-
From: Jacob Meuser [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 24, 2001 8:41 AM
To: debian-security@lists.debian.org
Subject: Re: strange log entry
On Thu, May
Hello,
If memory serves me correctly there's a line in /etc/X11 that you can
add/modify to tell it to NOT lissen.
Ed
-Original Message-
From: Noah L. Meyerhans [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 24, 2001 10:47 AM
To: Debian Security List
Subject: Re: wdm security
On Thu,
Hello,
Make sure you have klogd and syslogd running.
Ed
-Original Message-
From: Paul Dossett [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 24, 2001 12:00 PM
To: debian-security@lists.debian.org
Subject: Problem with logging firewall packets
Hi guys/gals,
Okay, I'm *really*
Hello,
anyone know why I get this when I post anything to this list?
Fatal Error: \n \nQuota for user [EMAIL PROTECTED] exceeded! \n \nOriginal
message follows: \n \n
it's from their mail delivery subsystem.
Ed
-Original Message-
From: Ed Street [mailto:[EMAIL PROTECTED]
Sent
*/
#define KERN_DEBUG 7 /* debug-level messages */
#
Ed
-Original Message-
From: Paul Dossett [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 24, 2001 12:24 PM
To: Ed Street; debian-security
Hello,
there's several methods to tell that.
a) use a product like portsentry
b) use iptables/ipchains to reject all forms of portscans
c) don't connect the box to the inet as portscans are a fact of life ;)
portsentry will trashcan any system that attempts to portscan you. If your
using 2.2.x
PROTECTED]
Sent: Thursday, May 24, 2001 8:11 PM
To: debian-security@lists.debian.org
Subject: RE: detecting portscanning
Ed == Ed Street [EMAIL PROTECTED] writes:
Ed
Ed iptables has an awsome mechanism for portscans ;) in fact you
Ed can set it up so that all portscans (well most I should
34 matches
Mail list logo