Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Directive SSLVerifyClient require doesn't work in Location/Directory configuration section #34

Open
amarthadan opened this issue Sep 14, 2017 · 2 comments

Comments

@amarthadan
Copy link

When is directive SSLVerifyClient require used inside of configuration section Location/Directory it seems like gridsite won't do anything with the request and I'll get an error from ssl module saying: Certificate Verification: Error (40): proxy certificates not allowed, please set the appropriate flag.

I need the setup where some locations are authorized with gridsite and some are not so I can't use the directive globaly.

I attach apache configurations and logs (of one request) - both working and not working.
apache-conf-bad.txt
apache-conf-good.txt
apache-log-bad.txt
apache-log-good.txt

@kouril
Copy link
Member

kouril commented Sep 27, 2017

I fail to see a feasible way to get this configuration working. When you change the SSLVerifyClient directive, the mod_ssl triggers re-negotiation of the TLS connection and uses its own verification routine, which can't be overridden by Gridsite as in case when usual connection is being handled.

What could work is the the other way round, ie. specifying SSLVerifyClient Require on the Server level and using SSLVerifyClient None on Locations/Direstories where no client authentication is requested. (I haven't tried though).

@amarthadan
Copy link
Author

Ok, I can try that. I'll let you know what I find out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants