-
Notifications
You must be signed in to change notification settings - Fork 15
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
attribute followed by 2nd colon results in "illegal base64 data at input" #23
Comments
curious enough this happens in a file with 8 entries. In a file with roughly 6371008 entries this doesn't get processed by what I'm using. It's possible that this is why hspark0582@96ec9ec was done in a fork |
Strange enough I'm unable to reproduce this in a test so far. |
I had an error in a function dealing with the empty value bug as a workaround.. |
we have lines like (attribute names and values changed): The double "::" seems to trip up ldif where the python one presumably deals fine with it. |
given an LDIF dump with an entry containing this attribute:
dircount: some.server.domain.tld 1 76 846
I get:
Error in line 84: illegal base64 data at input byte 15
The python implementation for ldif dumps does not complain about this.
This include SPACE (32) if I'm right, so is the error right? The specs say that spaces are allowed.
The text was updated successfully, but these errors were encountered: