From owner-freebsd-questions Mon Feb 2 19:01:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09742 for questions-outgoing; Mon, 2 Feb 1998 19:01:54 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from blues.jpj.net (root@blues.jpj.net [204.97.17.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09736 for ; Mon, 2 Feb 1998 19:01:47 -0800 (PST) (envelope-from benh@jpj.net) Received: from [192.168.10.1] (blake.eloquence.net [198.246.0.212]) by blues.jpj.net (backatcha) with ESMTP id WAA08228; Mon, 2 Feb 1998 22:01:41 -0500 (EST) X-Sender: benh@blues.jpj.net Message-Id: In-Reply-To: <34D6586D.875DAAAA@global.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 2 Feb 1998 21:04:03 -0600 To: Gopakumar H Pillai From: Ben Hockenhull Subject: Re: APC Back UPS monitor Cc: freebsd-questions@FreeBSD.ORG Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" >About the second part, I am really interested in knowing what exactly it >does. By the brief description, I am getting ideas to use it to >synchronize the shutting down of all machines in case of power failure. >I was thinking of writing a s/w which would broadcast a packet in the >network and a client listening to it brings down the system. But I am >too naive and have to study a lot to do this. This would be fairly easy to implement, but not quite so easy to implement securely. It is well worth noting that in the absence of some sort of authentication token, there is ample room for a DoS attack against any machines listening for this packet. Ben -- Ben Hockenhull benh@jpj.net "Revenge is a dish best served with pinto beans and muffins."