I have logged https://issues.apache.org/jira/browse/HOP-2469 <https://issues.apache.org/jira/browse/HOP-2469>. Please review. We need to know ASAP whether we are out of compliance with ASF encryption policy.
Julian > On Jan 27, 2021, at 12:38 PM, Julian Hyde <[email protected]> wrote: > > If an Apache release includes cryptography we need to declare it. See > https://infra.apache.org/crypto.html <https://infra.apache.org/crypto.html>. > > Julian > > > > >> On Jan 27, 2021, at 12:27 PM, Matt Casters <[email protected] >> <mailto:[email protected]>> wrote: >> >> Dear Hopiverse, >> >> I took the liberty to push out pull request 586 >> <https://github.com/apache/incubator-hop/pull/586 >> <https://github.com/apache/incubator-hop/pull/586>>. It synchronizes the >> password encoding of the metadata with the rest of the Hop platform. >> Mistakes of the past are best not repeated... >> >> To test this fairly small change I then wrote an AES two way password >> encoder plugin also included in the PR. >> I wrote the unit tests I thought were needed and wrote the documentation >> <https://github.com/apache/incubator-hop/blob/43a522b8c7a9f7a03d1c941fb99ebd9468f7f89e/plugins/misc/passwords/src/main/doc/aespasswords.adoc >> >> <https://github.com/apache/incubator-hop/blob/43a522b8c7a9f7a03d1c941fb99ebd9468f7f89e/plugins/misc/passwords/src/main/doc/aespasswords.adoc>> >> to go along with it... but I would appreciate an extra couple of eyes to >> see if it all works as expected to be on the safe side. >> >> Thanks in advance, >> >> Matt >
