現象描述:
windows上加解密正常,linux上加密正常,解密時發生以下異常:java
複製代碼代碼以下:linux
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的方法上,以下:dom
複製代碼代碼以下:ide
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( " 初始化密鑰出現異常 " );
}
} 加密
修改到以下方式,問題解決:操作系統
複製代碼代碼以下:ip
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( " 初始化密鑰出現異常 " );
}
} get
緣由分析
SecureRandom 實現徹底隨操做系統自己的內部狀態,除非調用方在調用 getInstance 方法以後又調用了 setSeed 方法;該實如今 windows 上每次生成的 key 都相同,可是在 solaris 或部分 linux 系統上則不一樣。generator