You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/07/04 17:19:00 UTC
[jira] [Commented] (OFBIZ-12275) Upgrade Apache Shiro to 1.7.1
[ https://issues.apache.org/jira/browse/OFBIZ-12275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17374332#comment-17374332 ]
ASF subversion and git services commented on OFBIZ-12275:
---------------------------------------------------------
Commit 46722b713f299a4f8725d341dbb6bf220d88f52f in ofbiz-framework's branch refs/heads/trunk from Xin Wang
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=46722b7 ]
Improved: Upgrade Shiro to 1.7.1 (OFBIZ-12275) (#309)
The default padding scheme of ECB mode for
org.apache.shiro.crypto.AesCipherService is different between v1.4.1 and
v1.7.1, i.e.:
v1.4.1 getPaddingSchemeName() result is "PKCS5Padding"
v1.7.1 getPaddingSchemeName() result is "NoPadding"
This patch specify padding scheme explicitly, after that exception
mentioned in build.gradle does not raise anymore, and initial data can
load successfully.
> Upgrade Apache Shiro to 1.7.1
> -----------------------------
>
> Key: OFBIZ-12275
> URL: https://issues.apache.org/jira/browse/OFBIZ-12275
> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: Trunk
> Reporter: Xin Wang
> Priority: Major
>
> As stated by comment, after upgrading Shiro to latest version, an EntityCrypto exception will be triggered when loading data.
> After some investigation, I found that the default padding scheme of ECB mode in Shiro is different between v1.4.1 and v1.7.1, i.e.:
> v1.4.1 getPaddingSchemeName() output: PKCS5Padding
> v1.7.1 getPaddingSchemeName() output: NoPadding
> After specifying padding scheme explicitly, EntityCrypto exception does not raise anymore.
> I'll create a pull request in GitHub.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)