From owner-cvs-all Wed Aug 26 05:35:58 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22344 for cvs-all-outgoing; Wed, 26 Aug 1998 05:35:58 -0700 (PDT) (envelope-from owner-cvs-all) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22322; Wed, 26 Aug 1998 05:35:51 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id OAA06763; Wed, 26 Aug 1998 14:34:55 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA29436; Wed, 26 Aug 1998 14:34:54 +0200 (MET DST) Message-ID: <19980826143454.03686@follo.net> Date: Wed, 26 Aug 1998 14:34:54 +0200 From: Eivind Eklund To: Matt Dillon , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sbin/ping ping.8 ping.c References: <199808260158.SAA07564@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199808260158.SAA07564@freefall.freebsd.org>; from Matt Dillon on Tue, Aug 25, 1998 at 06:58:41PM -0700 Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Aug 25, 1998 at 06:58:41PM -0700, Matt Dillon wrote: > dillon 1998/08/25 18:58:40 PDT > > Modified files: > sbin/ping ping.8 ping.c > Log: > (well tested at BEST): -i option can now take FP values (e.g. -i 0.1), > extremely useful for networking testing. Other options secured from > user-level D.O.S. attacks. -f, -s now root-only. -i wait times < 1.0 > root-only. >>> -c count limited to 100 and defaults to 16 when ping run >>> by non-root user. Eh - does this mean that I have to su to root to be able to run a continious ping? This is IMO a step backwards - we commonly use ping to find out if something (netwise close) is up yet. I can see its use for public shell servers, but for the way we use FreeBSD here, it will be a hinder (employees are the only ones that have access to execute anything; if somebody abuse it, I talk to them - if necessary, loudly :-) Suggestion: Could we create an /etc/security.conf where things like this can be configured? Thus we could have the best of both worlds... Eivind.