Deomid Ryabkov
Deomid Ryabkov
so, e.g. CN value will be put into `TLS_CN`, O into `TLS_O`, etc.
TLS certificate can be accessed via the `http.Request.TLS.PeerCertificates` field. we only need to examine the first entry of the slice, which is the client certificate itself, the rest (if any)...
no, should work. please post verbose log (-v 2)
fyi, SPDY has been deprecated in favour of HTTP/2. http://blog.chromium.org/2015/02/hello-http2-goodbye-spdy-http-is_9.html
the idea is: someone (you?) writes an [Authenticator](https://github.com/cesanta/docker_auth/blob/master/auth_server/authn/authn.go) or [Authorizer](https://github.com/cesanta/docker_auth/blob/master/auth_server/authz/authz.go), sends a PR and i review it.
@raphink so, i found a bit of free time over the weekend and put together #139 with that, all you need is add some code to github_auth to assign gh_team...
no objections in principle. what criteria for lockout do you propose?
there: https://github.com/ARMmbed/littlefs-fuse/pull/7 now, you will definitely want to change authorship and may also want to sort out licensing for some files that are currently marked as no copyright/license. the latter...
yes, makes sense
sorry, extremely busy with other stuff... but there might be some development here in a couple weeks.