PureBasic Forums - English

Hi,
nice Update Tool ! can we have the source ??

Unfortunately, it contains the encryption (protection) algorithm so for now the sources won't be opened. BTW, it has not a big interest, as all the main routines used in this tool have been explain on fr34k's web site

Fred wrote:Unfortunately, it contains the encryption (protection) algorithm so for now the sources won't be opened. BTW, it has not a big interest, as all the main routines used in this tool have been explain on fr34k's web site

The first thing you are taught in Data Security classes, is that a encryption algorithms safety mustn't depend on the safety of the algorithm, i.e. it's only safe if you can openmindedly release the algorithm to public review. The safety of an encryption should only depend on the input variables of the algorithm.

I think you are refering to Fingerprint (MD5, RSA, BlowFish etc..) algorithm, which is not the case here as it's reversible.

PWS32 wrote:Hi,
nice Update Tool ! can we have the source ??

Take a look at viewtopic.php?t=8331 it's easy to create your own update tool with this one

Fred wrote:I think you are refering to Fingerprint (MD5, RSA, BlowFish etc..) algorithm, which is not the case here as it's reversible.

Nope, the said is valid for every encryption method. The DES algorithm for example was published right from the beginning and it still is one of the most powerfull encryption standards. Ok, a little bit dusty and slow, but it works.
Also look at his little brother AES (Rijndael) which was choosen, out of several other competitors, in a public competition of the NIST Organization. None of them kept the algorithm secret.
I also wonder why you're calling RSA and BlowFish algorithms producing fingerprints? That's not true, they both are two way encryptions, although RSA is asynchronous whereas you need to know the public and the private key.

My mistake, RSA and Blowfish are obviously not fingerprint methods. The problem here is than anyone has the key so publish the crypt algo while having access to the key is almost non-sense, no ?

freedimension wrote:

Fred wrote:I think you are refering to Fingerprint (MD5, RSA, BlowFish etc..) algorithm, which is not the case here as it's reversible.

Nope, the said is valid for every encryption method. The DES algorithm for example was published right from the beginning and it still is one of the most powerfull encryption standards. Ok, a little bit dusty and slow, but it works.
Also look at his little brother AES (Rijndael) which was choosen, out of several other competitors, in a public competition of the NIST Organization. None of them kept the algorithm secret.
I also wonder why you're calling RSA and BlowFish algorithms producing fingerprints? That's not true, they both are two way encryptions, although RSA is asynchronous whereas you need to know the public and the private key.

True true though partially converted code for AES have been released a little bit ago... still nobody able to make the corrections needed so it's useless But hey, we now have the first encryption module for PB

Shannara wrote: But hey, we now have the first encryption module for PB

oh, i already have a simple RC4 encryption algo as native library written.
i should post it in the next days....

Rings wrote: oh, i already have a simple RC4 encryption algo as native library written.
i should post it in the next days....

Don't post on a monday

What? frick! That would be helpfull erm.. wait, native library? ie .lib not some external DLL or such? I hope so Looking foward to the release.

Berikco wrote: Don't post on a monday

LOL

i asking myself what happens specialy on a monday ?

Rings wrote:i asking myself what happens specialy on a monday ?

Don't worry, you'l never remember that

Rings, still planning on posting? Im cant wait for a native library, so I can build the server for use in Linux instead of windows