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

base64 decoding must be done per-chunk #25

Open
nburlett opened this issue Jul 22, 2013 · 0 comments
Open

base64 decoding must be done per-chunk #25

nburlett opened this issue Jul 22, 2013 · 0 comments

Comments

@nburlett
Copy link
Contributor

Individually-encoded base64 chunks must be decoded separately
due to padding at the end of base64-encoded chunks. Concatenating
base64 chunks and then decoding them may result in a different string
than decoding and then concatenating.

Lamson currently concatenates the base64 encoded chunks and then decodes them, potentially resulting in a different message than originally sent.

However, the characterset decoding into unicode must be done jointly,
since some mail clients will split the base64 encoding in the middle
of Unicode characters

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

1 participant