Information Security Stack Exchange is a question and answer site for information security professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I need to store encrypted information in a MySQL table. I would like to use the AES algorithm but I don't know if 4096 bit encryption is supported and if it is a good length to encrypt data like: credit card, email etc.

share|improve this question

migrated from stackoverflow.com Nov 23 '11 at 13:38

This question came from our site for professional and enthusiast programmers.

2  
That depends on if you use it correctly. – Brad Nov 22 '11 at 20:17
2  
4096 bit AES? Are you sure you're not talking about RSA? AES 256 is probably the "comparable" key size for AES and as an algorithm my understanding is that it's very secure. – Ben Brocka Nov 22 '11 at 20:20
17  
The fact that you are asking this question tells me you should definitely not be in the business of storing credit card information. If you are going to store credit card information you'll need PCI compliance and that's not exactly trivial. – Null Nov 22 '11 at 20:21
4  
You also might like to read what is the difference between 128, 192 and 256 bit AES in practical terms. – user2213 Nov 23 '11 at 9:22
4  
Do not store credit card information. – Ramhound Nov 28 '11 at 17:04

No, 4096 bit encryption is not good enough to encrypt your data. Becase of a few reasons.

  1. AES does not support 4096 bit encryption.
  2. Even if AES supported 4096 bit encryption, it would be far to slow (most likely). When 128 bit AES is plenty secure why would you want to slow your system down for such little added value?
  3. If you actually meant RSA instead of AES, still the answer is no as 4096 bit RSA is unnecessary. 2048 bit RSA is more than sufficient. But, that said, why would you want to use public-key crypto to encrypt your database? Normally that would be a bad idea. Please post more details so we can determine the best recommendation.
share|improve this answer
    
not to mention, RSA will be really slow, as in I'll have to wait a year for it to encrypt. (for a whole database) – ewanm89 Nov 24 '11 at 1:27
    
Your answer's lacking the the fact that he shouldn't store credit card information at all, and definitely not in a reversible form (encrypted). – Stef Heylen Dec 15 '15 at 15:11
    
@StefHeylen why not? Tons of companies store credit card info. I would prefer that they didn't, but legally (in the US at least) you can. – mikeazo Dec 15 '15 at 15:21
    
@mikeazo: yes, if they comply to the industry standards (PCI-DSS). Why would one encrypt credit card information rather than hashing it? There's no reason to have it in a reversible form is there? – Stef Heylen Dec 15 '15 at 15:24
1  
@StefHeylen I agree. I wouldn't store it either. But, the fact of the matter is that tons of businesses do. Typically for convenience purposes (makes it easier for you to pay them and easier for them to charge you). I wouldn't even store hashes of a credit card number. That could lead to an off-line brute force attack. Credit card number entropy is low enough. – mikeazo Dec 15 '15 at 15:35

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.