From owner-freebsd-current Tue Mar 14 9:20:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.telemere.net (www.telemere.net [63.224.9.3]) by hub.freebsd.org (Postfix) with ESMTP id 4421537BAA2 for ; Tue, 14 Mar 2000 09:20:31 -0800 (PST) (envelope-from visigoth@telemere.net) Received: by www.telemere.net (Postfix, from userid 1001) id D038070601; Tue, 14 Mar 2000 11:27:34 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by www.telemere.net (Postfix) with ESMTP id CCCB96C801 for ; Tue, 14 Mar 2000 11:27:34 -0600 (CST) Date: Tue, 14 Mar 2000 11:27:34 -0600 (CST) From: Visigoth To: freebsd-current@freebsd.org Subject: Also... /etc/periodic/daily/200.backup-passwd and MD5 (fwd) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY="0-1574324419-952551298=:16144" Content-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1574324419-952551298=:16144 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Did anybody get a chance to look at this and decide that it wasn't the case or was? I was suprised because I didn't hear _anything_ and am wondering if I was doing something wrong... Resubmiting... Dameion Stark Date: Wed, 8 Mar 2000 15:34:58 -0600 (CST) From: Visigoth To: freebsd-current@freebsd.org Subject: /etc/periodic/daily/200.backup-passwd and MD5 All flames welcome as a learning experience.... ;-) I am currently running a -current on a group of machines where I work. I decided to use the MD5 libscrypt passwords, and noticed something strange in the daily output e-mail. When the MD5 passwords are used the daily output e-mail fails to truncate the encrypted passwd from the /etc/master.passwd file before e-mailing out the diffs. This is the case even on a machine which was built today. I haven't seen any info on -current about it so I thought I would bring it up. I also wrote and attached small patch to take care of the issue in the short term. all it does is change: diff $bak/master.passwd.bak /etc/master.passwd |\ sed 's/^\([<>] [^:]*\):[^:]*:/\1:(password):/' to: diff $bak/master.passwd.bak /etc/master.passwd |\ sed 's/^\([^:]*\):[^:]*:/\1:(password):/' My logic could be messed up, so if there are any issues that I overlooked in the patch I would love to hear about them. I thought it might be a good thing to take care of quick before -RELEASE (yea!) Thanks all... Damieon Stark visigoth@telemere.net --0-1574324419-952551298=:16144 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="200.backup-passwd.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Patch for 200.backup-passwd and MD5 Content-Disposition: ATTACHMENT; FILENAME="200.backup-passwd.patch" KioqIC92YXIvYmFja3Vwcy8yMDAuYmFja3VwLXBhc3N3ZAlNb24gRmViIDIx IDA5OjE5OjAwIDIwMDANCi0tLSAvZXRjL3BlcmlvZGljL2RhaWx5LzIwMC5i YWNrdXAtcGFzc3dkCU1vbiBGZWIgMjEgMDk6MTk6MjggMjAwMA0KKioqKioq KioqKioqKioqDQoqKiogMTYsMjIgKioqKg0KICAgICAgaWYgY21wIC1zICRi YWsvbWFzdGVyLnBhc3N3ZC5iYWsgL2V0Yy9tYXN0ZXIucGFzc3dkOyB0aGVu IDo7IGVsc2UNCiAgCWVjaG8gIiRob3N0IHBhc3N3ZCBkaWZmczoiDQogIAlk aWZmIC11ICRiYWsvbWFzdGVyLnBhc3N3ZC5iYWsgL2V0Yy9tYXN0ZXIucGFz c3dkIHxcDQohIAkJc2VkICdzL15cKFs8Pl0gW146XSpcKTpbXjpdKjovXDE6 KHBhc3N3b3JkKTovJw0KICAJbXYgJGJhay9tYXN0ZXIucGFzc3dkLmJhayAk YmFrL21hc3Rlci5wYXNzd2QuYmFrMg0KICAJY3AgLXAgL2V0Yy9tYXN0ZXIu cGFzc3dkICRiYWsvbWFzdGVyLnBhc3N3ZC5iYWsNCiAgICAgIGZpDQotLS0g MTYsMjIgLS0tLQ0KICAgICAgaWYgY21wIC1zICRiYWsvbWFzdGVyLnBhc3N3 ZC5iYWsgL2V0Yy9tYXN0ZXIucGFzc3dkOyB0aGVuIDo7IGVsc2UNCiAgCWVj aG8gIiRob3N0IHBhc3N3ZCBkaWZmczoiDQogIAlkaWZmIC11ICRiYWsvbWFz dGVyLnBhc3N3ZC5iYWsgL2V0Yy9tYXN0ZXIucGFzc3dkIHxcDQohIAkJc2Vk ICdzL15cKFteOl0qXCk6W146XSo6L1wxOihwYXNzd29yZCk6LycNCiAgCW12 ICRiYWsvbWFzdGVyLnBhc3N3ZC5iYWsgJGJhay9tYXN0ZXIucGFzc3dkLmJh azINCiAgCWNwIC1wIC9ldGMvbWFzdGVyLnBhc3N3ZCAkYmFrL21hc3Rlci5w YXNzd2QuYmFrDQogICAgICBmaQ0K --0-1574324419-952551298=:16144-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message