public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin@cygwin.com>
Subject: RE: [cygwin] sshd and smart card support
Date: Sun, 27 Sep 2015 18:18:00 -0000	[thread overview]
Message-ID: <34B38F182E57409AA0C31A520B919160@black7> (raw)
In-Reply-To: <BLU436-SMTP9682B9119087422F606D599E400@phx.gbl>

> -----Original Message-----
> From: Jarek C.
> Sent: Sunday, September 27, 2015 4:45 AM
> 
> After a lot of struggling with trying to get sshd work with 
> regular domain accounts I found an alternative bit of 
> software I then installed for a test. After a failed test, 
> looking thrugh the logs of that ssh server I found an 
> interesting piece of information possibly explaining why it 
> wouldn't work with my initial setup. It turned up that all 
> the domain accounts I used for testing have a requirement 
> associated with the account AD object to use smart cards for 
> logon pourposes. I never seen this mentioned in cygwin sshd 
> logs as a reason for failed connection but only a statement 
> that the logon name or password was incorrect. I don't 
> suppose there is a workaround but maybe something worth 
> implementing in sshd logs to cover this sort of scenerios as 
> likely no one was expecting this to be causing access problems.

1. Getting ssh to work with smartcards would be the first step.

This requires working with the smartcard middleware / applets. There are
many people out there who would be interested in this.

2. Getting sshd to interact as if a smart card was presented...

This is a lot less likely to succeed.

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Principal Consultant              10 West 24th Street #100    -
- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 


--
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

      reply	other threads:[~2015-09-27 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-27  8:45 Jarek C.
2015-09-27 18:18 ` Jason Pyeron [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=34B38F182E57409AA0C31A520B919160@black7 \
    --to=jpyeron@pdinc.us \
    --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).