From owner-freebsd-ports Mon Jul 17 6:38: 1 2000 Delivered-To: freebsd-ports@freebsd.org Received: from mail.mdanderson.org (mail.mdacc.tmc.edu [143.111.87.47]) by hub.freebsd.org (Postfix) with ESMTP id 6006A37B978 for ; Mon, 17 Jul 2000 06:37:50 -0700 (PDT) (envelope-from fosburgh@flash.net) Received: from jefnt (jef-nt.mdacc.tmc.edu [143.111.64.202]) by mail.mdanderson.org (8.9.1b+Sun/8.9.1) with SMTP id IAA24067; Mon, 17 Jul 2000 08:34:24 -0500 (CDT) Message-ID: <01db01bfeff4$2ded5350$ca406f8f@mdacc.tmc.edu> From: "Jonathan Fosburgh" To: "Andrew M. Miklic" Cc: "Conrad Sabatier" , , "Will Andrews" References: <397304CA.958E1396@attglobal.net> Subject: Re: GDM Date: Mon, 17 Jul 2000 08:37:40 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ----- Original Message ----- From: "Andrew M. Miklic" To: Cc: "Conrad Sabatier" ; ; "Will Andrews" Sent: Monday, July 17, 2000 8:06 AM Subject: Re: GDM > > Here is a red flag to look for. FreeBSD passwords are encrypted differently > > than passwords in most UNIX systems. I have run into some code (such as the > > LambdaMOO server) that expect old style passwords, and so you have to do > > some special patching to fix that. I would check there if it is not > > authenticating correctly. > > Interesting...if this is true, do you know how kdm does it (we have a port for > kde-core, which contains kdm, and it works fine)--do they do this same big bandaid? > I have no idea how they handle it, that is why I mention it as something that may be a problem. I have never looked at the source code for *dm, and it is entirely possible that none of them have a problem. It basically depends on how they handle the authentication. The problem with LambdaMOO was that it used crypt() (I think) to encrypt the passwords, but when someone attempted to log in it used something different, and was expecting the old format. If you look at the encrypted passwords in FreeBSD, you will notice they all begin something like $1$ and then have the actual password, so you get something like $1$fghYTd.gfjd, and the server was just wanting the fghYTd.gfjd, and so it couldn't authenticate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message