buzhash64e: with rolling hash encryption#8920
Draft
ThomasWaldmann wants to merge 3 commits into
Draft
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #8920 +/- ##
==========================================
- Coverage 85.17% 85.11% -0.06%
==========================================
Files 93 93
Lines 15372 15389 +17
Branches 2318 2322 +4
==========================================
+ Hits 13093 13099 +6
- Misses 1583 1592 +9
- Partials 696 698 +2 ☔ View full report in Codecov by Harness. |
8f120dd to
bf26a50
Compare
bf26a50 to
c603fb4
Compare
|
(As a sidenote on speed). I've found it quite interesting that fast PCG RNG (numpy's default prng) is predictable, but seed reconstruction out of 64 consecutive values is a non-trivial operation — 2¼ CPU-years of computation. However, it's still just a €108, if we assume a CPU core to cost 4 €/month. |
c603fb4 to
e7ad355
Compare
e7ad355 to
caa9fdc
Compare
Encrypting the rolling hash should make it better resist against attacks. use aes128-ecb (slow, not optimized)
this will detect if there is anything going wrong regarding deduplication with the encrypted buzhash mode.
Co-authored-by: Junie <junie@jetbrains.com>
caa9fdc to
d95d503
Compare
Member
Author
|
rebased on current master, extended chunker comparison script to fastcdc, force pushed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rather simple and very slow encryption code, needs to be tuned later IF we find this worthwhile doing.
Note:
.encrypt_many()call and then do another loop over the esums to decide where to cut. would be much less overhead than now, but needs maintaining yet another buffer efficiently.