Click here to Skip to main content
15,868,030 members

Comments by 1337Architect (Top 4 by date)

1337Architect 5-Oct-14 17:18pm View    
Reason for my vote of 1 \n Nice that you encrypt the querystring but using MD5 checksum ECB cipher mode TripleDES is a horrible idea, specially when .net offer better alternatives. I would not advice anyone to use your code in this state.
1337Architect 5-Oct-14 16:49pm View    
Reason for my vote of 1 \n This is article is almost the worst possible combo of crypto settings you can do. I strongly advice people to find something else.
1337Architect 24-Aug-14 3:45am View    
Reason for my vote of 1 \n The use of a hard coded ENCRYPTION_SIGNATURE, the choice of ECB as cipher mode, MD5CryptoServiceProvider to generate the key and the choice of tripleDES as algorithm. All of this is very poor choices which shows that you don't really know what you are doing.
1337Architect 23-Aug-14 1:18am View    
Reason for my vote of 1 \n I have to say the choice of algorithm, generation of key, choice of chiphermode is all quite poor choices.

This code is not written with security in mind and I would not recommend people to use it.

If you want to improve it use Rfc2898DeriveBytes to generate the key and IV, use CFB as cipher mode and change the encryptionalgorithm to be AES or Rijndael.

You should probably rethink the strategy of having a constant hardcoded password in your code.