sshd and smart card support

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

sshd and smart card support

Jarek C.
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.

--
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 | Threaded
Open this post in threaded view
|

RE: [cygwin] sshd and smart card support

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