From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 4 01:55:20 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2FF0F445 for ; Tue, 4 Jun 2013 01:55:20 +0000 (UTC) (envelope-from gs_stoller@juno.com) Received: from outbound-mail03.dca.untd.com (outbound-mail03.dca.untd.com [64.136.47.37]) by mx1.freebsd.org (Postfix) with SMTP id D0A081261 for ; Tue, 4 Jun 2013 01:55:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juno.com; s=alpha; t=1370310917; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; l=0; h=From:Date:To:Subject:Message-Id:Content-Type; b=nODFwUPR2R2JV2pTEI2XUzSl9Z7o+tCl0ug5aA5raMLPW0q6ZxLPyPcgYn14Eku1j wj6Trdli8g8ZjBdjYxzNOGOMJm8DLUirA8xSVmIc6uPRR87a3b4gnDMcaay/lE9yTg Rmfa5fXTbmCZfPbEII3nNFUAY6hK//swj7QDDQBk= X-UOL-TAGLINE: true Received: from outbound-bu1.dca.untd.com (webmail02.dca.untd.com [10.171.12.142]) by smtpout02.dca.untd.com with SMTP id AABJ44T5GACCLHEJ for (sender ); Mon, 3 Jun 2013 18:48:22 -0700 (PDT) Received: from [108.21.243.160] by webmail02.dca.untd.com with HTTP: Tue, 4 Jun 2013 01:47:55 GMT X-Originating-IP: [108.21.243.160] Mime-Version: 1.0 From: "gs_stoller@juno.com" Full-Name: "gs_stoller@juno.com" Date: Tue, 4 Jun 2013 01:47:55 GMT To: FreeBSD-hackers@FreeBSD.org Subject: pw X-Mailer: Webmail Version 4.0 Message-Id: <20130603.214755.24886.0@webmail02.dca.untd.com> Content-Type: multipart/mixed;boundary="--__JWM__J6ed34e02.a28f112S.21ea087M" X-UNTD-BodySize: 2022 X-ContentStamp: 2:1:1860089499 X-UNTD-OriginStamp: /s5f1SIGSI3+WdnoYQ8yRCf96fIKT5RNqJE3btq3Fk8xiVELU4XJHA== X-UNTD-Peer-Info: 10.171.12.142|webmail02.dca.untd.com|outbound-bu1.dca.untd.com|gs_stoller@juno.com X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 01:55:20 -0000 ----__JWM__J6ed34e02.a28f112S.21ea087M Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Type: text/plain; charset=windows-1252 ____________________________________________________________ NetZero now offers 4G mobile broadband. Sign up now. http://www.netzero.net/?refcd=3DNZINTISP0512T4GOUT1 ----__JWM__J6ed34e02.a28f112S.21ea087M Content-Type: text/plain Content-Description: forgot-PW.txt Content-Disposition: attachment; filename="forgot-PW.txt" Content-Transfer-Encoding: quoted-printable I have 2 FreeBSD systems (they are using versions 4.3 and 4.7 of the Fr= eeBSD Operating System) that I have not used for a long time, and I have= forgotten their passwords. I have information on these systems that I = want to retrieve but I have not been able to log into these Systems. My= problem was put on the internet several years ago and the usual ways of= getting into the systems (basically by being the operator) were suggest= ed and tried, unsuccressfully. A friend and I discussed my problem and = he suggested that I zero out the root password so that I can get in as r= ooy (to set a new password and then continue operating as root). Does the FreeBSD community have a program (either on a floppy or a CD R= OM, preferably the latter) that can do this? If not, I suggest that you= write one that would work with all the (formats of) password files that= have ever been used. If it can determine the format of password files = just by examining them, that would be fine. If it can't, then it should= ask the user in which version of the FreeBSD Operating System the passw= ord file was used, try to verify it by the structure of the password fil= e and if it is verified make a copy of the password file (in case someth= ing goes wrong, so that the system can be restored to its original condi= tion and so undo anything that this program has done), and zero out the = root password. After this is done, one could log in as root to set the = root password and afterwards (as root) set other user passwords. Operating Systems that have ever been run. You could set it up to look ----__JWM__J6ed34e02.a28f112S.21ea087M--