-
Notifications
You must be signed in to change notification settings - Fork 403
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
Windows agent with some locales cannot do proper security check #296
Comments
@schwabe I am not sure what cause problem and how it could be fixed properly. I double checked:
Man here has the same problem: |
From what I found, Windows doesn't allow to set entire drive as case-sensitive. So administator can set I tried |
Any comments in the new context? |
I am not able to reproduce this. I used We could use
|
We have faced with ovpnagent problem. In some cases Windows paths of client and server differ. It leads to server rejecting client connection via named pipe. I double checked source code and found nothing suspicious, but after adding additional logging we've found this:
As you can imagine check compares paths and fails.
We have found that it was users who have English localization instead of Russian (as many others in our case). Probably it's easy to fix but converting both paths to lower case, but I am not it's good from security point.
The text was updated successfully, but these errors were encountered: