-
Enhancement
-
Resolution: Fixed
-
P4
-
9
-
b134
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8201680 | 8u192 | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
JDK-8196160 | 8u172 | Ivan Gerasimov | P4 | Resolved | Fixed | b04 |
JDK-8165598 | 8u171 | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
JDK-8198166 | emb-8u171 | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
JDK-8203746 | openjdk7u | Ivan Gerasimov | P4 | Resolved | Fixed | master |
"javax.crypto.BadPaddingException: Given final block not properly padded" is a vague message.
more often than not, a bad key or password is responsible for the exception. We should hint at this in the exception message.
See also : http://stackoverflow.com/questions/8049872/given-final-block-not-properly-padded
more often than not, a bad key or password is responsible for the exception. We should hint at this in the exception message.
See also : http://stackoverflow.com/questions/8049872/given-final-block-not-properly-padded
- backported by
-
JDK-8165598 Improve javax.crypto.BadPaddingException messages
- Resolved
-
JDK-8196160 Improve javax.crypto.BadPaddingException messages
- Resolved
-
JDK-8198166 Improve javax.crypto.BadPaddingException messages
- Resolved
-
JDK-8201680 Improve javax.crypto.BadPaddingException messages
- Resolved
-
JDK-8203746 Improve javax.crypto.BadPaddingException messages
- Resolved