Skip to content

binary file support and optimization#1

Open
TEX479 wants to merge 12 commits intonot-pyroman:masterfrom
TEX479:master
Open

binary file support and optimization#1
TEX479 wants to merge 12 commits intonot-pyroman:masterfrom
TEX479:master

Conversation

@TEX479
Copy link

@TEX479 TEX479 commented Feb 2, 2025

yea

this is just so VSCode stops yelling at me, that there are like a milion errors.
and it makes it easier to see what goes in and out of a function
@TEX479 TEX479 closed this Feb 2, 2025
@TEX479
Copy link
Author

TEX479 commented Feb 2, 2025

wrong repo, sorry

@not-pyroman
Copy link
Owner

not-pyroman commented Feb 14, 2025

@TEX479 no worries, what was the intended repo? I might merge these changes as i was going to get around to binary support eventually, i just forked the project initially because i was planning on using it as a library for a different project, and i was only processing text, so it wasn't a major concern for me, but it trying to use the algorithm for the OS of my hosts was annoying (one was windows and the other was linux)

@not-pyroman not-pyroman reopened this Feb 14, 2025
@TEX479
Copy link
Author

TEX479 commented Feb 15, 2025

i was working on cipherOS. the day was hecktic, and I had to open multiple pull requests that day. i just misclicked my for of your dec-enc repo and hit "create pull request" without checking the repository. i only noticed when i tried to go to the previous page in the browser, that i was on this repo instead of the cipherOS's.

and yea, sure you can merge my fork, but note that i didn't really test the changes much, though i did type-check the whole program and it looked like it should work just fine.
i still got some plans for my fork, mostly storing encrypted binaries as binaries, otherwise encryption increases the file size to 5 times the original.

@TEX479 TEX479 changed the title split files again binary file support and optimization Mar 15, 2026
@TEX479
Copy link
Author

TEX479 commented Mar 15, 2026

Just in case anyone ever sees this:
I figured you can calculate a valid password hash instead of brute forcing. This gives an average of 4000x speedup, meaning the program can find the passcode in under 0.1ms
I don't know if there is any application for such speeds, but now we got them either way.

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

Successfully merging this pull request may close these issues.

2 participants