aes

SslStream is supposed to negotiate the cipher type, key length, hash algorithm, etc. with its peer SSL stack. When using it in my code, I find that the negotiation always defaults to RC4 & MD5. I would like to use 3DES or AES for some added security. Looking around the web I find only a few references to this problem and no solutions; one poster is claiming this actually makes sense, since the lowest common denominator between the two stacks is secure while has the added benefit of being faster/using less CPU resources. While this may be technically correct, my particular trade-off between

I am using the CCCrypt method. Can I use a longer key than than 128bit? Can it be arbitrarily long? Or perhaps multiples of 128? If so how would I do this? I didn't think this woas possible but I found this text: here Some algorithms such as AES and RSA allow for keys of different lengths , but others are fixed, such as DES and 3DES. Encryption using a longer key generally implies a stronger resistance to message recovery. As usual, there is a trade off between security and time, so choose the key length appropriately. How does AES allow for different lengths, does it ignore the bits higher

I want to decrypt an Encrypted Sting using AES/CBC/Nopadding in c# Windows Phone 8 application. My string is in file of IsolatedSorage . I pasted the string HERE which is junk. From this Article I am using AesManaged class to decrypt. But how to set padding to NoPadding because by default the padding set to PKCS7 from here. string fileName = "titlepage.xhtml"; if (fileStorage.FileExists(fileName)) { IsolatedStorageFileStream someStream = fileStorage.OpenFile(fileName, System.IO.FileMode.Open, FileAccess.Read); using (StreamReader reader = new StreamReader(someStream)) { str1 = reader.ReadToEnd

It seems that I have a thread-safety issue with Cipher and/or PBEKeySpec. JDK : 1.8.0_102, 1.8.0_151 and 9.0.1+11 PBKDF2 algorithm: PBKDF2WithHmacSHA1 Cipher algorithm: AES/CFB/NoPadding Key algorithm: AES I know these classes aren't tread-safe if we use the same instances, but that's not the case, I'm getting a new instance at each decode. But even that, sometimes the decode fails, there is no exception, just an unexpected decoded value. I've been able to reproduce the problem: @Test public void shouldBeThreadSafe() { final byte[] encoded = { 27, 26, 18, 88, 84, -87, -40, -91, 70, -74, 87,

Why Pycrypto AES decryption gives different output when decrypted with AES object used for encryption and right output when decrypted with AES object used solely for decryption? from Crypto.Cipher import AES obj = AES.new('0123456789012345', AES.MODE_CBC, '0123456789012345') message = '0123456789012345' ciphertext = obj.encrypt(message) plaintext = obj.decrypt(ciphertext) # plaintext here is byte array obj2 = AES.new('0123456789012345', AES.MODE_CBC, '0123456789012345') plaintext = obj2.decrypt(ciphertext) # plaintext here is 0123456789012345 According to BlockAlgo#encrypt from which the AES