Private Text Encryption (Protect Your Secrets..!)

Hello every body.
How are you all?
I hope you are in the best of health.

Many developers working on the .NET Framework depend on “Windows Registry keys" and "Application Settings files" to store and retrieve application settings. Using such a technique will result in a security hole, because these settings (such as server connection data, your user passwords, and so on) could be accessed by malicious users.

The simplicity of opening the Setting xml file and seeing all of your application’s sensitive data that you save and retrieve, made me thinking for a new approach that introduces a new idea and offers a complex encryption algorithm for texts. So please greet my new own Class called "Private Text Encryption".
It’s just a small and simple dll file but it’s not trivial! Let’s see the class features:


1- A new encrypted text every time.
2- You’ll be able to decrypt encrypted texts only the same computer that has made the encryption.
3- Although I'm the developer of this class, I wasn’t able to decrypt any encrypted text generated by this class.

Follow the link below to download the dll file:

< link to compiled file removed by moderator >

An example to use the class (Attached as (VS 2010) solution):

Attachment 94045

Code:

PHP Code:

---

Imports PrivateTextEncryption
Public Class frmMain
Dim PrivateText As New PrivateTextEncryption.PrivateTextEnc
Private Sub btnEncryption_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnEncryption.Click
txtEncryption.Text = PrivateText.EncryptText(txtRealText.Text)
End Sub
Private Sub btnDecrypt_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnDecrypt.Click
txtDecryptedText.Text = PrivateText.DecryptText(txtEncryptedText.Text)
End Sub
End Class 


---

I hope this class would be useful for you.
Your comments will be appreciated....
Thanks
OmarNegm

Thanks for sharing it, but a few things...

Never... never ever attach compiled binaries here... that's a sure fire way to make sure it never gets downloaded. Instead, include the source code, let people inspect the code and compile it themselves. We've been burned before.

That said, seems like a cool concept... again, thanks for sharing it.
My comment is about "You’ll be able to decrypt encrypted texts only the same computer that has made the encryption." -- which is fine if the data to be encrypted first exists unencrypted on the user's machine... If it's something like a connection string, or a key, or something that *I* want to encrypt and then send to the client as part of the deployment... that may not help. Just pointing that out.

-tg

Thank you so much.
first i accept that we should not to share a compiled binary here. but i had made this class to use it inside my own software but i said that "May any other people wanna something like this class so why i didn't share it to be helpful for any one?" so that i had share it just to help others.
About your comment: the target of this class is to save the values inside "application settings" and "windows registry keys" in safe. so that i had added the second feature("You’ll be able to decrypt encrypted texts only the same computer that has made the encryption.") :).
Any way i so respect your comment and thank you so much techgnome.

So, Who wants to try out my Snake Game?

Quote:

---

Originally Posted by claws135

So, Who wants to try out my Snake Game?

---

I'm ready if its will be helpful for me or for any one else. Thanks for comment.

I think the joke went over Programmation's head there.... it was a "Snake Game" that got people burned and is the (one of at least) reasons why we don't post compiled binary files here... someone years ago, was allegedly working on a Snake Game... built it, compiled it, and posted it here for others to try... people downloaded it and installed it... turned out he'd built a trojan horse, wrecked a lot of people's computers... so it's left something of a bit of a bad taste in our mouths ever since. That's why I said to never post the compiled code... sharing is fine, but post the original source code.

-tg

Yaa, and the snake game sucked too :D

It was a fun time. He posted the source code, so people saw what he had put in there. The wheels came off pretty quick. It was an excellent example of why one shouldn't take compiled binaries from a site, including this one.

I have removed your DLL attachment/link (and the executable files from your other attachment) to protect our members, because we have no way of knowing what an executable file actually does - which could include something malicious, such as if there is a virus on your computer.