public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Sshd and key based authentication
Date: Mon, 18 Nov 2013 18:11:00 -0000	[thread overview]
Message-ID: <528A581F.2060607@cygwin.com> (raw)
In-Reply-To: <5289C8BD.1010109@netfence.it>

On 11/18/2013 2:58 AM, Andrea Venturoli wrote:
> Hello.
>
> I'm trying to set up sshd on a Windows 2003 domain controller.
> Everything works with password authentication; however I need this for a
> script, so, in order to get non-interactive login, I must use keys.
> Tried as hard as I could, but I could not achieve this: I'm always asked for
> a password.

<snip>

> Is this supposed to work? Several posts say so, but no one mentions a domain
> controller... Does it bring in anything special?

If you want/have to use domain user logins, then you need to create a
domain equivalent of 'cyg_server'.  You can use the scripts that
'ssh-host-config' uses as a guide to do this but the actual process
must be done by hand and you need access and permission on your domain
controller to set this up.

'ssh-host-config' will not handle this case for you.

> Are the above users correct? Any problem with it?

For local users, no, no problem.

> What are correct ownership and permissions of /home, /home/myuser,
> /home/myuser/.ssh and /home/myuser/.ssh/authorized_keys?

'ssh-host-config' will set these up for you.  I suggest you use it.

> According to some how-tos, ssh-host-confing should have prompted with
> "CYGWIN=" and I should have replied "tty ntsec", but this did not happen.
> Other how-tos suggest putting this variable in the environment.
> Is this information current or obsolete? I tried and it didn't seem to
> matter...

<http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview>

Yes, this information is obsolete.  This is the main reason we
recommend not using various How-To guides that you'll find littered
around the Internet.

> Any other hint?

If a domain service account isn't an option, look at the other
options listed in the User's Guide:

<http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview>

Method 2 or 3 might be sufficient for your need.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

      parent reply	other threads:[~2013-11-18 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18  7:59 Andrea Venturoli
2013-11-18  8:35 ` Andrey Repin
2013-11-18  9:18   ` Andrea Venturoli
2013-11-20 17:37     ` Andrea Venturoli
2013-11-20 21:50       ` Andrey Repin
2013-11-26 17:12         ` Andrea Venturoli
2013-11-26 20:25           ` Larry Hall (Cygwin)
2013-11-20 23:00       ` Larry Hall (Cygwin)
2013-11-18 18:11 ` Larry Hall (Cygwin) [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=528A581F.2060607@cygwin.com \
    --to=reply-to-list-only-lh@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).