From owner-freebsd-stable Fri Aug 25 11:35: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E91E137B423 for ; Fri, 25 Aug 2000 11:35:05 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA76376; Fri, 25 Aug 2000 12:35:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18552; Fri, 25 Aug 2000 12:34:59 -0600 (MDT) Message-Id: <200008251834.MAA18552@harmony.village.org> To: Vivek Khera Subject: Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons) Cc: FreeBSD Stable List In-reply-to: Your message of "Fri, 25 Aug 2000 11:36:30 EDT." <14758.37502.989465.176825@onceler.kciLink.com> References: <14758.37502.989465.176825@onceler.kciLink.com> <20000824110414.C12752@winternet.com> <200008241201.IAA32736@sanson.reyes.somos.net> <20000824080419.B51628@dazed.slacker.com> <14757.15655.515615.780499@onceler.kciLink.com> <20000824162123.A80150@irrelevant.org> <14757.16490.269381.416596@onceler.kciLink.com> <20000824163533.B80150@irrelevant.org> <14757.17729.113055.693358@onceler.kciLink.com> <200008250322.VAA31765@billy-club.village.org> Date: Fri, 25 Aug 2000 12:34:59 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14758.37502.989465.176825@onceler.kciLink.com> Vivek Khera writes: : Much more slick! I like the idea of making rcmd(3) be ssh-aware, with : fallback to rsh for compatibility. It seems the only change I'll need : to make to my backup process is to do it as a user of group operator : rather than as root. Not a big issue. I have changes in my tree that ports the dump changes that OpenBSD did a while ago to make dump/restore not setgid anymore. But it requires that I port changes to wall to support -g. Alternatively, I need to add group support to syslogd, which would be much more generic (thanks to bde, I think, for this idea). Now, all I need is a good syntax for groups. Right now you have / -> log to file * -> all users @h -> log to host h | -> log to program u1,u2 -> log to users u1 and u2 and I'm thinking that : might be a good idea: :g -> log to all members of group g logged into the machine. I'm not sure which way to go at this point. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message