thequickbrownfox

hi guys, thanks for the update and information. I was able to get through the problem. BUt I am observing a strange behavior and really want to consult with you guys, esp. skinnywhiteguy (author) and other members of the group. What is the key criteria for the input. What is mean is not all the key are taken as invalid input by the AES code that I am using from the crypto suite. I tried many keys some of them work some of them do not. I really have no idea why some of the keys do not work. For e.g the following keys work 01234567890123456789 0123456789abcdef0123456789abcdef G0123456789abcdef01234G Wabcdef123456789abcdW But when i put a key such as below it failed W0123456789abcde012345Wabcde So now the issue is which key to be used. I am building an application where I want user to provide the key. This key (USERKEY) will be used to encrypt/decrypt the username and password. Then there would be a key (SECRETKEY) within the code that will be used to encrypt the USERKEY. This gives us the flexibility where by user can update the username, password and the keys to encrypt the username and password whenever they want. Any suggestions are welcome. I would really like to understand what kind of keys are necessary for the crypto suite AES code. Regards, fox

hi, Great work!!! I am using your crypto suite. I am using it for encrypting and decryption the passsword data. I am using AES optimized. It seems to work fine but the problem arises when I write the value to a file. For example, I am encrypting the password "P@ssword01" and writing it to a file dat file pwd.dat. When I am reading encrypted password value from pwd.dat it is not get decrypted as expected. Is there something special I need to take care of this. The idea is I do not want to store the password in clear text. Any suggestions will be appreciated. Also a general question - what is the default encryption of the AES/AES_optimized script - AES 128 or AES 256. Please advise. Thanks.