SAFE USE ~~~~~~~~ (* *) (* Actually, at the current state of technology, its accepted that the *) (* very best method to break a good, and well implemented, crypto prog. *) (* is getting the key from the user or trying to guess it with a brute *) (* force attack... And Blowfish carries all the caracteristics on an *) (* excellent algorithm. It may fail, both, on the implementation side *) (* or on the user side... *) (* *) (* A correct use, and maintenance of passwords and files, is needed!. *) (* And major care has been taken, in this implementation, to avoid any *) (* hidden weaknesses. *) (* *) (* Though the author is confident in is own work, it is up to the user *) (* to decide the adequacy of this program to its own needs... *) (* ... and you have this code to check the correctness of it. *) (* Its all up to you... No magic exists, so you also have an important *) (* role in your own security! *) (* *) WARNING ~~~~~~~ (* *) (* It is possible to create a *Quanta-Computer* that solves a crypto *) (* problem. It may already exist in secret even to the American NSA. *) (* And own by those "above the president". Like the OMEGA Agency. *) (* *) (* MEANING: *) (* Pure mathematical cipher, no matter how powerfull, like it is the *) (* case of RijnDael witch was adopted as the new American Encryption *) (* (alias: AES) ... This may have been the reason to the adoption of *) (* a cipher unbreakable by known computers, present and future, that *) (* everybody has or will have... But not against a Quantum Computer. *) (* A most respected RijnDael rival, the TwoFish cipher, seems to be *) (* less prone to attack by a Quanta-computer. *) (* *) (* SOLUTIONS: *) (* a) Use a safe though less powerfull Cipher but with random PBoxes *) (* like Blowfish or Blowfish based like Cobra or DNA-Blowfish. *) (* *) (* b) The Cipher MUST be implemented in a safe MODE like CBC or CFB. *) (* *) (* c) Use a COMPRESSOR like RAR, ARJ, ZIP, or LHA to hide your info *) (* will be inside, protected and you will also save valuable disk *) (* space and time when sharing it. The ideal woud be to have only *) (* compressed data, with NO references to the method or filenames *) (* inside (just like random data) *) (* --- [E-Mail] dutra.lacerda@mail.telepac.pt [Alternate] dulac@ip.pt [Home-Page] http://planeta.ip.pt/~ip200075/ [Alias] http://www.factor-h.com/ ---