public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problem with ssh-host-config?
Date: Wed, 16 Mar 2016 10:05:00 -0000	[thread overview]
Message-ID: <20160316100536.GC15577@calimero.vinschen.de> (raw)
In-Reply-To: <74652658081042b6aed140a56c397df0@R01UKEXCASM112.r01.fujitsu.local>

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

On Mar 15 15:42, Nick.Battle@uk.fujitsu.com wrote:
> Hi Corinna,
> 
> >> In theory this should only happen if you *only* use passwd in
> >> /etc/nsswitch.conf.  If you use default settings (passwd db), this
> >> branch should not be hit either.
> >>
> >> So I wonder how your /etc/nsswitch.conf looks like.  Are you using 
> >>
> >>  passwd: passwd
> >>  group: passwd
> >
> > We install the following in nsswitch.conf just before running ssh-host-config:
> >
> > passwd:   files
> > group:    files 
> > db_home:  windows
> >
> > Does that explain the path we're taking?
> 
> Looking at the csih scripts, that would take the code into the mkpasswd branch with the bug.
> So perhaps no one has noticed this before simply because the default behaviour skips it.

Yup, makes sense.  Thanks for checking.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-03-16 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 12:39 Nick.Battle
2016-03-11 14:01 ` Achim Gratz
2016-03-11 15:41   ` Corinna Vinschen
2016-03-15 15:42     ` Nick.Battle
2016-03-16 10:05       ` Corinna Vinschen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160316100536.GC15577@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).