Fingernail on 11/1/2009 at 23:09
Quote Posted by jtr7
The intensity here is profoundly out of proportion. I want to laugh, but I'm fascinated by how serious some of the posts appear to be. Who are you trying to protect? :weird:
this
RavynousHunter on 11/1/2009 at 23:35
Quote Posted by Kolya
It works. Open issues follow:
- It should encrypt files without the user having to put in new filenames. If you cannot get around this at least make two input fields next to each other so one can see which new filename belongs to which original. As it is, it hardly scales well.
- It should be able to restore the original filename.ext when decrypting.
- It should be able to encrypt/decrypt folder-structures and restore them!
- Minor: When a crypt job is done the bar stays at full scale at the moment.
Under the hood you could incorporate a quick zipping mechanism, and encrypt/decrypt those archives. That will get you folder structures and original filenames.
Future development:
- Ability to choose encryption algorithm
- Passwords
- Personal generated encryption keys
- On the fly encryption
I'm going to work on that for the new release. I just wanted to get some more important stuff out of the way first, ya know?
A few things I want to address here, though.
*
Ability to Choose Encryption: Might be good, and I could do it, but it would require writing more than one encryption function. That and they would have to remember what method they used for a given file.
*
Personal Keys: Another good idea, but it would require a bit of record-keeping on the user's side. Unless I appended the key to the end of the file, encrypting it on the way, of course.
*
On-the-Fly Encryption: It'd be nice, but I'm not that knowledgeable when it comes to adding options to the Windows shell context menus. Don't get me wrong, I'm sure I could do it with enough time, its just not something I know off-hand. (Or did you mean something else? :confused:)
As for the progress bar staying full, that was unintentional, I must have forgot to call the Update() function somewhere...
I suppose I could use some compression algorithm to keep all encrypted files in one area. I could also encrypt the compressed file to keep prying taffers out. I think I'll look up how to implement some basic zipping in VC# '08.
Thanks to those who posted up ideas and problems, keep 'em comin! :thumb:
Unless you're thinking of being a complete douchebag, in which case, I kindly ask you to start your own sister thread where you can belittle me to your heart's content.
Thief13x on 11/1/2009 at 23:42
Quote Posted by denisv
You should release the source code so I can rewrite it in five lines of Haskell
Now that's something I would pay to see
dvrabel on 12/1/2009 at 02:00
Quote Posted by RavynousHunter
*
Ability to Choose EncryptionNot a good idea, choose the best available algorithm and use only that. The more complex a system is, the harder it is to verify its security. IPsec fell into this trap.
Kolya on 12/1/2009 at 02:22
What I meant by "On the fly encryption" was that you could open an encrypted file through GEP, edit it and when you save GEP automatically encrypts it again.
Scots Taffer on 12/1/2009 at 02:37
Quote Posted by RavynousHunter
"The man who only learns what others know is as ignorant as if he learns nothing. The treasures of knowledge are the most rare, and guarded most harshly."-- Chronicle of the First Ageso the encryption is powered by keeper-glyphs?
oh god my mind is suddenly filled with some horrid SS2/Thief amalgamation and-
*wet pop*RavynousHunter on 12/1/2009 at 03:32
Quote Posted by Kolya
What I meant by "On the fly encryption" was that you could open an encrypted file through GEP, edit it and when you save GEP automatically encrypts it again.
Aah, ok. That could be difficult, but not impossible. :thumb:
Also, an update! (
http://www.geocities.com/ravynousdezign/GEP_1.4.zip) Version 1.4 is hot off the assembly line! Thanks to Kolya for his suggestion of using original filenames for encrypted files. This should make things much simpler when encrypting and decrypting your files.
However, there is a compatibility issue with v1.4 and previous versions in that the previously generated files do not have their original extensions as part of their filename, which is key to the new method implemented in v1.4.
Also, I added a "Legal" menu selection, giving all the legal crap for the GEP. Basically, just ask me for permission if you want to mirror or modify the GEP. Just give me credit and keep the original Legal dialog intact.
Generic Encryption Program (GEP) © 2009, Ravynous Dezign
Nicker on 12/1/2009 at 03:54
Quote Posted by dethtoll
I don't think you have to worry.
ZZZZing!
I know I shouldn't encourage the lad but it was a "palpable hit".
Kolya on 12/1/2009 at 08:40
I'm hit? :confused:
*looks up and down on himself*
RavynousHunter, consider this: I encrypted a text file on my desktop, then right away decrypted it to the desktop again.
Small problems that occurred:
- The program forgot the destination between en/decrypting.
- When decrypting no message about the original text file with that name already existing in the location was made. (Overwrite? Rename?)
- This decrypt-destination: "F:\desktop\newname.txt" produces "F:\desktop\newname.extoldname.ext".
