*BSD News Article 11741


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA1989 ; Wed, 24 Feb 93 13:00:15 EST
Newsgroups: comp.os.386bsd.questions
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!wupost!newsfeed.rice.edu!rice!news.Rice.edu!rich
From: rich@Rice.edu (Richard Murphey)
Subject: Re: xdm for XFree86 1.2 & crypt
In-Reply-To: hissam@source.asset.com's message of Mon, 22 Feb 1993 03:23:52 GMT
Message-ID: <RICH.93Feb22220751@omicron.Rice.edu>
Sender: news@rice.edu (News)
Reply-To: Rich@Rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
References: <1993Feb22.032352.33872@source.asset.com>
Date: Tue, 23 Feb 1993 04:07:51 GMT
Lines: 30

In article <1993Feb22.032352.33872@source.asset.com> hissam@source.asset.com (Scott A. Hissam) writes:
	   I think xdm is compiled with crypt.c as opposed as crypt_dummy.c
   README.386bsd from XFree86 1.2 directory on agate.berkeley.edu says that
   this is the other way around.

Yep, the README.386BSD was wrong.  I've uploaded a revised
README.386BSD and XFree86-1.2-386BSD-errata and put an xdm linked with
crypt_dummy.c in /pub/incoming/XFree86-1.2 on agate.berkeley.edu
(128.32.136.1).  If you don't see it there, Chris has moved it to
/pub/386BSD/0.1-ports/XFree86-1.2.  

The following item has been added to the errata.  Rich

  
5: xdm in XFree86-1.2-bin.tar.Z uses des (encryption) contrary to the
  README.386BSD.
  
  This distribution was unintentionally built with a working crypt
  (des).  If you have replaced crypt on your system (see Chris
  Demetriou's /usr/386bsd.errata/crypt.instructions) and use encrypted
  passwords you can use the xdm binary in XFree86-1.2-bin.tar.Z.
  
  If you have not replaced crypt, get XFree86-1.2-xdm-nodes.tar.Z and
  install the xdm it contains. Otherwise xdm will not accept passwords.
  This latter xdm binary uses the 386BSD 0.1's dummy crypt routine that
  prints the message 'Crypt not present in system' in the xdm-errors
  file each time a user logs in.  You can ignore this.  It merely tells
  you that passwords in /etc/passwd are unencrypted.