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

Invalid encryption #1

Open
danielgindi opened this issue Oct 29, 2021 · 2 comments
Open

Invalid encryption #1

danielgindi opened this issue Oct 29, 2021 · 2 comments

Comments

@danielgindi
Copy link

This code always appends a length int to the encrypted data, which is not part of the spec.
This makes it impossible to get valid XXTEA results.
Could you add an option for avoiding that?

@Berrysoft
Copy link
Owner

Berrysoft commented Oct 29, 2021

This code is, originally, a translation of JS version, with some optimization. If you find any inconsistency, fell free to point out. If you would like more features, I'm afraid I don't have enough time at present. You can fork the repo, or even copy the code to your project, along with the MIT license. Then you can add any features you'd like. It would be better for me if you would like to open a pull request for that.

@danielgindi
Copy link
Author

Thank you, I'll try to make a PR for this soon.

I was actually trying to see what's on Nuget to migrate from an old .NET Framework lib of mine, but I had to migrate that piece of code to Standard when I found that this lib adda extra logic over the XXTEA.

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