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

feat(aes):-specify-the-initialization-vector-in-aes-encryption #256

Conversation

sunnydanu
Copy link
Owner

@sunnydanu sunnydanu commented Oct 27, 2024

When I use AES encryption, I find that the result is different every time after encryption. The reason is due to the problem of not specifying the initialization vector. So I added an input item to specify the initialization vector. The initialization vector is only valid for AES and TripleDES encryption.

Note: This PR incorporates contributions from upstream PR-#373 of CorentinTh/it-tools. All original commits and authorship are retained. Some adjustments may have been made for compatibility or bug fixes.

Copy link

vercel bot commented Oct 27, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
godev-run ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 2, 2024 0:15am

….run into feat(aes)--specify-the-initialization-vector-in-aes-encryption
@sunnydanu sunnydanu added enhancement New feature or request P1 Priority 1 : ready to review labels Nov 2, 2024
@sunnydanu sunnydanu enabled auto-merge November 2, 2024 10:44
sunnydanu added 2 commits November 2, 2024 17:05
….run into feat(aes)--specify-the-initialization-vector-in-aes-encryption

Merge branch 'developing/2.0.0' of https://github.com/sunnydanu/godev.run into feat(aes)--specify-the-initialization-vector-in-aes-encryption
@sunnydanu sunnydanu merged commit c879124 into developing/2.0.0 Nov 2, 2024
6 checks passed
@sunnydanu sunnydanu mentioned this pull request Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P1 Priority 1 : ready to review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants