From owner-freebsd-questions Thu Sep 3 09:18:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07715 for freebsd-questions-outgoing; Thu, 3 Sep 1998 09:18:58 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from rrnet.com (rrnet.com [206.11.160.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07710 for ; Thu, 3 Sep 1998 09:18:57 -0700 (PDT) (envelope-from lien@rrnet.com) Received: (from lien@localhost) by rrnet.com (8.8.8/8.8.8) id LAA13957 for questions@freebsd.org; Thu, 3 Sep 1998 11:17:49 -0500 (CDT) Date: Thu, 3 Sep 1998 11:17:49 -0500 (CDT) From: Craig Lien Message-Id: <199809031617.LAA13957@rrnet.com> To: questions@FreeBSD.ORG Subject: bug in 2.2.6 passwd(1) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just stubled across kind of an obscure bug, possibly usable as a security hole, don't have time :( to look at it. A seg fault happens when a -u or maybe others is put after the passwd command while using sudo. Since the polite printf "(null)" is showing up there must be a missing char pointer. Craig Lien Red River Net --------8<--------8<--------8<--------8<--------8<--------8<-------- bash$ sudo passwd -u rrnet Changing local password for (null). New password: Please enter a password at least 6 characters in length. New password: Retype new password: Segmentation fault To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message