- Problem: increasing privacy strength, even though the a/symmetric key sizes are somewhat limited by default/regulation/implementation etc (to decrease the ruler power of the statistics feeding the AI-big-brother-golem serving the corporations-and-governments two-heads-hydra capturing humanity in disasters).
- Solution: letting the user to chose N to magnify the strength derived from key size, such that
- N can be chosen for specific case of communication, messages and participants etc, while being demonstrated as weight of keys measured by the required time to compute with these keys in some specific environment;
- N is the number of rounds to re-encrypt with different symmetric for asymmetric keys of sevral users, where
- 0 <= n < N,
- m(0) is the padded plaintext (default to 32),
- k(n) = hash(m(n),rnd(n)) is used as symmetric key (default SHA-3 ),
- m(n+1) = symmetric_encrypt(m(n),k(n)) (default aes256/Twofish),
- r(u,n) is the encrypted k(n) with the public-key(n) of the user u, (default rsa),
- b(u) is a block of all r(u,n) per u starting with the size of all b(u),
- only m(N-1) after all b(u) are kept.

-
Notifications
You must be signed in to change notification settings - Fork 0
License
comcomized/sksp-Scale-Key-Size-Protocol
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Resources
License
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published