I hope your "NumOfBytes" is badly named, and is really "NumOfInt64Blocks" :-)

Unless your "//      NextKey := *removed*" fetches a value from a One-Time-Pad with the same length as the data you're encrypting, that you're never re-using the OTP, and that you have a guaranteed non-surveilled channel for getting the OTP to the other side... then this is pretty useless.

I'm sorry if "useless" seems like a harsh word, but it's true nonetheless. If there's any reason to use crypto at all, use proper crypto. A scheme like this is definitely not good enough for "a crypted Chat-Session" - if you're discussing sensitive matters you need a whole lot more (there are perfectly good reasons Signal has a complex protocol), if you're not... well, who cares, send plaintext or use a HTTPS connection. Doesn't matter much if NSA knows when you're gonna hook up with your girlfriend, or what groceries you need to pick up on your way home from work :-)

Also, the code is pretty slow - no loop unrolling, and EMMS'ing for every block? Ouch! :)

I happened to find a similar(actually i think the same) program Text-2-EXE

-chashnniel (February 15, 2019, 03:37 AM)

Ugh, missed forum reply notifications for this one!

At first glance, this seems to be a very clear ripoff of fSekrit (although with internationalization added?). The maxa-tools site seems to be down at the moment (Domain Status    On-hold (redemption Period)), but it seems the tool has been shared to a bunch of sites (portablefreeware, softpedia, heise, ...).

I've taken a quick look at the text2exe.exe downloaded from Heise in a hex editor, and... it looks like it's a Visual Basic application. So, not a hackjob that's just replacing resources, and not somebody doing a few modifications to the open-source version of fSekrit... but doing pretty much a reimplementation?

The mind, it boggles :huh: