現象描述:
windows上加解密正常,linux上加密正常,解密時發生 以下異常: java
Des修改方式以下: linux
public void getKey(String strKey) { try { KeyGenerator _generator = KeyGenerator.getInstance("DES"); SecureRandom secureRandom = SecureRandom.getInstance("SHA1PRNG"); secureRandom.setSeed(strKey.getBytes()); _generator.init(secureRandom); this.key = _generator.generateKey(); } catch (Exception e) { e.printStackTrace(); } }
AES修改方式以下:
javax.crypto.BadPaddingException: Given final block not properly padded
at com.sun.crypto.provider.SunJCE_f.b(DashoA13*..)
at com.sun.crypto.provider.SunJCE_f.b(DashoA13*..)
at com.sun.crypto.provider.AESCipher.engineDoFinal(DashoA13*..)
at javax.crypto.Cipher.doFinal(DashoA13*..)
at chb.test.crypto.AESUtils.crypt(AESUtils.java:386)
at chb.test.crypto.AESUtils.AesDecrypt(AESUtils.java:254)
at chb.test.crypto.AESUtils.main(AESUtils.java:40) windows
解決方法:
通過檢查以後,定位在生成KEY的方法上,以下:
- public static SecretKey getKey (String strKey) {
- try {
- KeyGenerator _generator = KeyGenerator.getInstance( "AES" );
- _generator.init(128, new SecureRandom(strKey.getBytes()));
- return _generator.generateKey();
- } catch (Exception e) {
- throw new RuntimeException( " 初始化密鑰出現異常 " );
- }
- }
修改到以下方式,問題解決:
- public static SecretKey getKey(String strKey) {
- try {
- KeyGenerator _generator = KeyGenerator.getInstance( "AES" );
- SecureRandom secureRandom = SecureRandom.getInstance("SHA1PRNG" );
- secureRandom.setSeed(strKey.getBytes());
- _generator.init(128,secureRandom);
- return _generator.generateKey();
- } catch (Exception e) {
- throw new RuntimeException( " 初始化密鑰出現異常 " );
- }
- }
緣由分析
SecureRandom 實現徹底隨操做系統自己的內部狀態,除非調用方在調用 getInstance 方法之後又調用了 setSeed 方法;該實如今 windows 上每次生成的 key 都相同,可是在 solaris 或部分 linux 系統上則不一樣。
緣由二:
一、加密完byte[] 後,須要將加密了的byte[] 轉換成base64保存,如:
BASE64Encoder base64encoder = new BASE64Encoder();
String encode=base64encoder.encode(bytes);
二、解密前,須要將加密後的字符串從base64轉回來再解密,如:
BASE64Decoder base64decoder = new BASE64Decoder();
byte[] encodeByte = base64decoder.decodeBuffer(str);
完整例子: