From owner-freebsd-security Wed May 10 5: 1: 8 2000 Delivered-To: freebsd-security@freebsd.org Received: from vuurwerk.nl (envy.vuurwerk.nl [194.178.232.112]) by hub.freebsd.org (Postfix) with SMTP id F24B437B613 for ; Wed, 10 May 2000 05:00:57 -0700 (PDT) (envelope-from petervd@vuurwerk.nl) Received: (qmail 15070 invoked from network); 10 May 2000 12:00:53 -0000 Received: from kesteren.vuurwerk.nl (HELO vuurwerk.nl) (194.178.232.59) by envy.vuurwerk.nl with SMTP; 10 May 2000 12:00:53 -0000 Received: (qmail 46331 invoked by uid 11109); 10 May 2000 12:00:53 -0000 Mail-Followup-To: security@FreeBSD.ORG Date: Wed, 10 May 2000 14:00:53 +0200 From: Peter van Dijk To: security@FreeBSD.ORG Subject: Re: envy.vuurwerk.nl daily run output Message-ID: <20000510140053.G46065@vuurwerk.nl> References: <20000509150609.L42267@vuurwerk.nl> <20000509215515.B29766@cc942873-a.ewndsr1.nj.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000509215515.B29766@cc942873-a.ewndsr1.nj.home.com>; from cjc@cc942873-a.ewndsr1.nj.home.com on Tue, May 09, 2000 at 09:55:16PM -0400 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 09, 2000 at 09:55:16PM -0400, Crist J. Clark wrote: > On Tue, May 09, 2000 at 03:06:09PM +0200, Peter van Dijk wrote: > > [snip] > > > > Backup passwd and group files: > > envy.vuurwerk.nl passwd diffs: > > 3c3 > > < root:(password):0:0::0:0:Charlie &:/root:/usr/local/bin/bash > > --- > > > root:(password):0:0::0:0:Charlie &:/root:/usr/local/bin/bash > > [snip] > > > > This line needed some thinking from me until I realized that it was trying > > to tell me the rootpassword changed (which I already knew, ofcourse). Could > > this be made more obvious, something like (password1) in the top one and > > (password2) in the bottom one? > > Can you think of a clean way to do it? You do not want to show > 'password1' and 'password2' if the password _didn't_ change, right? Correct. > Now, for the case above, it is easy enough, but you need to handle > the possibity of multiple changes. > > Sure, it's quite possible to do with awk(1) or perl(1), but IMHO, I'll > take the simple solution in 200.backup-passwd over something that > would need to be fairly complicated. Personally, I don't think most > people stare too long at the above line before figuring it out, and > once they do, they never have trouble spotting it again. > > Then again... If someone sees a quick way to do it... I think you are right. I will recognize what it means next time, and a simple shell-scripting solution doesn't seem to be anywhere near. Thank you for your time :) Greetz, Peter. -- Powered by WUT? - Peter van Dijk [student:sysadmin:developer:madly in love] | `Yes, this was actually a hack and not | (petervd@|www.)vuurwerk.nl | a scritp kiddie clicking a mouse button.' | www.dataloss.net | - hackernews.com, commenting on the apache.org deface To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message