Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 24 Oct 2003 13:38:50 -0500
Message-Id: <200310241838.h9OIcofD006268@tigris.pounder.sol.net>
X-Authentication-Warning: tigris.pounder.sol.net: rodmant set sender to nicebounce AT trodman DOT com using -f
From: Tom Rodman <nicebounce AT trodman DOT com>
Reply-to: Tom Rodman <nicebounce AT trodman DOT com>
To: cygwin AT cygwin DOT com
X-note: 1G0!G/usr/sbin/sendmail -v -t -f"nicebounce AT trodman DOT com" # less traceable, bypasses MUA
Subject: ssh-host-config: "mkpasswd -l -u sshd"; should it be "-d" on domain controller?

consider:

  bash-2.05b$ uname -r; grep mkpasswd /bin/ssh-host-config
  1.5.5(0.94/3/2)
            mkpasswd -l -u sshd | sed -e 's/bash$/false/' >> ${SYSCONFDIR}/passwd

Does "mkpasswd -l" make any sense on a domain controller?

On an NT domain controller I tested 

  mkpasswd -d -u sshd | sed -e 's/bash$/false/' >> /etc/passwd

and "ssh localhost" worked fine after stopping and starting sshd.  The '-d"
option creates a user entry that apparently has the same SID, but
different uid offset.

Using only the "-d" switch on a domain controller would simplify
the cron script I use to automatically rebuild /etc/passwd.

--
thank/regards,
Tom Rodman
pls run for my address:  
  perl -e 'print unpack("u", "1\:6UP\,\$\!T\<F\]D\;6\%N\+F\-O\;0H\`");'


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/