![]() ![]() However I would more like to know If I'm on the right path or have missed something obvious. The code has some limitations with Attributes and handling " that is escaped in strings etc. The program then creates a random password for every string making the same values unique and then adds the decrypt method to the solution. The program encrypts a string using the following algorithm: I decided to write a Stand-Alone Code Analysis Tool for the. Identical strings should not look the same.Given the C# preprocessor directives I don't think it can be done like this anyway. I've seen some examples in C++ using a preprocessor at compile time but this is not what I want. With these statements out of the way let's look at the problem at hand: I'm also fully aware that whatever I do can be broken and yes security through obscurity has been rejected as far back as 1851 and in more recent years even for. ![]() This is not for encrypting connectionStrings, passwords or other sensitive data, that is being done with protected section in App.Config and has already been handled in other questions. I'm looking at a task to obfuscate strings in my application like URLs, paths and queries at compile time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |