ZPF Encryption Library

[Killswitch]

Hey,

I've decided to release this text encryption library that I've been working on! It uses my own, custom, shift chiper to make the chiper text from the cleartext.

It includes two functions:

ZPFEncryptString(Key.s,String.s)

ZPFDecryptString(Key.s,String.s)

There is an example source file included!

I hope you can get some use out of this libary - we're (that is ShadowRunnerX and I) are making some improvements for v2.0 which should make the encryption even harder to break.

BTW. This is freeware as far as NON-COMMERICAL applications are concerned, however there will be a small fee if you plan to use this library in a COMMERCIAL application.

Enjoy!

Download Here!

[NoahPhense]

Not that it really matters.. But you have a bunch of things that are
spelled wrong in your readme ..

- np

[Karbon]

No offense intended here, but I'm curious as to why you would brew up your own encryption scheme rather than use the industry standard stuff that has been in development for decades. Paul implemented some RC4 encryption ages ago and put it out to the community to use for free. I'd trust RC4 a lot more than a home brew encryption scheme! Is there something this library of yours does that I can't get anywhere else?

Not that I'm opposed to commercial software, quite the opposite, but if you want to sell me a new encryption library it better support industry standard stuff!

Good luck!

[Killswitch]

Sorry about the readme, I am a terrible speller.

@Karbon

That's a really good point, I must say. I am in the process of writing an encryption package (that does support industry standard stuff) but as I got halfway through I had a thought. Basically I was writing an encryption program that used other peoples encryptions algorithms, so (I thought) why can't I write my own? So I did.

The ZPF encryption does scramble test very well, for example here's this sentance encrypted with the key 'Bob':

Ÿ™§Ô´l…ëªÐ’ªÍæeÍæ®Ü’©ÊæµÞä¨Ó×eÊÕ³Ææ³ÊåeØÛ­Ù’¸Œ×·ÊÚeÊÞµÒӽʒ·ÔØe‘Þ±ÊéeÞäªÛ’¹Ø×¹…×±Çߦ×Õ¸…åªÔÖeÓá®Ùâ¾×ճʒ‹µÌeÊÚ™

I'm sure no one would have any idea what that above section of chiper text actually said if I hadn't already told you. Just so you know I'm not cheating you can unscramble the text yourself.

In the end it's upto you weather or not you choose to use the library. If you would prefer to use industary standards than that is up to you - my intention was never, and will never be to repalce industry standard encryption, just to compliment it and offer my own little contribution.

Edit:

As Purebasic internally suports DES, MD5 and CR32 - and there is that really great, free, library out there that you mentioned is there much point in me including all of that in this library?

My next step will be to introduce some sort of file encryption - I've no idea how to go about it so I guess I'll be glued to google for a while!

[Karbon]

Point well taken, Killswitch, and I commend your creativity!

[thefool]

Hi!

I was just wondering, if the encrypted text has same lenght as the decrypted text? If so its much easier to decrypt than if you have a more complex algo that will find out what to put where with more chars.. Of course i know this is a new algo just telling you that most other algo's use that way.. 128bit
encryption, and that way..

[Killswitch]

At the moment the encrypted text does have the same numebr of characters as the decrypted text. I'm trying to think of a way of adding some, or removing some, characters in a way in which they can be seen by the algorithim.

Thanks for the suggestion, if anyone else has any then please feel free to mention them!

[Killswitch]

Oki doki I've updated the algorithm! As well as spell checking the Readme! The length of the chiper text will now be somewhere between Len(String)+1 and Len(String)*2. This is because I've used a random element in the algorithim.

The download link above still works and is where you can find the updated version.