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
LDAP password authentication fails when SVN password is 52 chars or longer #242
Labels
Comments
Tested with version |
May be related to #156 ? |
slonopotamus
added a commit
to slonopotamus/git-as-svn
that referenced
this issue
May 6, 2019
Turns out, not all Base64 was born equal. RFC-4648 that we used, only allows strict Base64 alphabet in input string while RFC-2045 also allows whitespace, newlines and other funny stuff. And native Subversion sends \n for long logins/passwords Fixes git-as-svn#242
slonopotamus
added a commit
to slonopotamus/git-as-svn
that referenced
this issue
May 6, 2019
Turns out, not all Base64 was born equal. RFC-4648 that we used, only allows strict Base64 alphabet in input string while RFC-2045 also allows whitespace, newlines and other funny stuff. And native Subversion sends \n for long logins/passwords Fixes git-as-svn#242
This bug was fixed in git-as-svn 1.10.1 that was just released: https://github.com/bozaro/git-as-svn/releases/tag/1.10.1 |
@slonopotamus awesome, thank you for the quick fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've set
git-as-svn
with LDAP authentication to aglauth
server. When the password is 52 chars or longer git-as-svn throws an exception:When the password is
51
chars everything works as expected and I get the plain password on my LDAP server bind request so I can verify.Subversion client used:
Quite bizarre!
The text was updated successfully, but these errors were encountered: