GitXplorerGitXplorer
A

Encryption-from-scratch

public
0 stars
0 forks
0 issues

Commits

List of commits on branch master.
Verified
5a75c9e3f84714b534882e3ad2d137c76f78a4d7

Spelling

AArthurRab committed 5 years ago
Verified
53f4baa6587d441e01d284c952207d0cfd37ffc1

Spelling mistake

AArthurRab committed 5 years ago
Verified
b8862b023fd6187f3f5f99827714e53e853c2a7c

Only run test code if file is called directly

AArthurRab committed 5 years ago
Verified
84e3b6166578f8a354e3422883d3408deccc26c9

Add more info about the project into the README

AArthurRab committed 5 years ago
Verified
d321ed67ec8153417ad54ecbf1e5fb7c20e2fed4

Update README.md

AArthurRab committed 6 years ago
Verified
faba033b6270769d4e165954004bdda52fb7d4ee

Create README.md

AArthurRab committed 7 years ago

README

The README file for this repository.

Encryption-from-scratch

Out of personal interest. Absolutely no security guarantees. I did not know how encryption algorithms worked and decided to have a crack at it. I would call this a fairly succesful attempt at hashing and symmetric encryption, though it still has some room for optimizing which I may get around to at some point.

The main property I was trying to achieve was that if you have E(text, key) and you change even one bit of the key, the new output would not have any clear realtionship to the original one.

Hashing here is implemented as H(text) = E('AAAAAAAAA', text) Basically, we use the encryption algorithm, but put in the string we want to hash as the key instead of the input. Thus, since we use a constant as the string we are "encrypting", we get an output of constant size, which also changes completely when the input string is changed even slightly.