From owner-freebsd-security Fri Jan 21 23:42:11 2000 Delivered-To: freebsd-security@freebsd.org Received: from titan.cc.wwu.edu (titan.cc.wwu.edu [140.160.240.18]) by hub.freebsd.org (Postfix) with ESMTP id 368D914C5A for ; Fri, 21 Jan 2000 23:42:06 -0800 (PST) (envelope-from n8412060@cc.wwu.edu) Received: from localhost by titan.cc.wwu.edu (8.9.1/8.9.1) with ESMTP id XAA04537 for ; Fri, 21 Jan 2000 23:42:04 -0800 (PST) Date: Fri, 21 Jan 2000 23:42:04 -0800 (PST) From: "mr. t" To: security@FreeBSD.ORG Subject: attack notification via email Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Regarding stream, DOS Smurf, trash packet bombing and sybounce... Be nice to have the OS send an email. I realize this is what syslog is for but since this might be a once in awhile sort of a thing and its very important, if you are going to go to the trouble of making the OS smart enough to recognize these - make option to email the sysadmin too with an alert message. That's a little more in-your-face than syslog and might be appropriate for this once in a lifetime event. At least the option would be really great and give alot of piece of mind - no alerts, nothing happened while out to lunch. Not all sysadmins know who to write a utility to scan the logs and email an alert. Besides that's kludgy. Just a thought... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message