From owner-freebsd-isp Wed Sep 29 10:23:47 1999 Delivered-To: freebsd-isp@freebsd.org Received: from cliff.i-plus.net (cliff.i-plus.net [209.100.20.42]) by hub.freebsd.org (Postfix) with ESMTP id A5AC615847 for ; Wed, 29 Sep 1999 10:22:33 -0700 (PDT) (envelope-from st@i-plus.net) Received: from ARCADIA (arcadia.i-plus.net [209.100.20.198]) by cliff.i-plus.net (8.9.3/8.9.3) with SMTP id NAA51283; Wed, 29 Sep 1999 13:22:15 -0400 (EDT) From: "Troy Settle" To: , Subject: RE: changing server platforms Date: Wed, 29 Sep 1999 13:22:13 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Importance: Normal Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org James, I assume that /etc/shadow and /etc/passwd are identical, with the exception of the passwords. I also assume that solaris uses DES encryption for it's passwords. If this is the case, your solution is simple: Install DES for FreeBSD, then write a perl script to dismantle /etc/shadow, and re-write it in the same format you see in FreeBSD's /etc/master.passwd. Once done, run pwd_mkdb, and yer all set. Untested, but should get you started: #!/usr/bin/perl while(<>) { ($login,$passwd,$uid,$gid,$gecos,$home,$shell) = split(/:/); $new_pwd = join(':',$login,$passwd,$uid,$gid,'',0,0,$gecos,$home,$shell); print $new_pwd; } Good luck, -Troy > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG > [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of up@3.am > Sent: Wednesday, September 29, 1999 10:21 AM > To: freebsd-isp@FreeBSD.ORG > Subject: changing server platforms > > > > I'm getting ready to change our main server (mail, user web, ftd, > secondary radius, etc) from Sparc Solaris 2.6 to FreeBSD 3.2-RELEASE > soon. My main concern is going to be getting > 1100 usernames and > passwords moved over. > > I can see that just moving /etc/passwd and /etc/shadow over isn't going to > work. In fact, I can see that FBSD doesn't even have an /etc/shadow, but > what I assume contains that data, /etc/pwd.db, which appears to be some > sort of hashed file. > > So far, I can think of a few ways to do this, none of them ideal: > > 1: gather all the usernames and passwords from a customer database and > write a script to add them all in. Problem with this is that database > isn't 100% up-to-date with the passwords. > > 2: run a crack program (any recommendations?) on a copy of the Solaris > /etc/shadow file, then trim out the username/passwd pairs for same script. > > Or There's a well-known utility to translate Solaris /etc/passwd > and /etc/shadow files into a working FreeBSD format . > > Suggestions appreciated... > > James Smallacombe PlantageNet, Inc. CEO and Janitor > up@3.am http://3.am ========================================================================= ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans 3 days of clues, news, and views from the industry's best and brightest. Visit for information and registration. ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message