Allow using AmazonCorrettoCryptoProvider plugin on Linux to compute hashes faster

[aberenguel]

As discussed in #1849 , the AmazonCorrettoCryptoProvider could have great performance improvement on Linux.

Using default Provider:

[engine.task.HashTask]                  Hash: md5 => 25258ED0BD157CC9D06D9675C9B4B3C3
[engine.task.HashTask]                  Hash: sha-1 => 0229C4D391927DC3B27DA0809F79FFE0EB6DAA2F
[engine.task.HashTask]                  Hash: sha-256 => 792CD8BFD20E81A5C01648D1E45FCC301B255FF94A4865D9183440944FDE0364
[engine.task.HashTask]                  Hash time: 20.032

Using AmazonCorrettoCryptoProvider:

[engine.task.HashTask]                  Hash: md5 => 25258ED0BD157CC9D06D9675C9B4B3C3
[engine.task.HashTask]                  Hash: sha-1 => 0229C4D391927DC3B27DA0809F79FFE0EB6DAA2F
[engine.task.HashTask]                  Hash: sha-256 => 792CD8BFD20E81A5C01648D1E45FCC301B255FF94A4865D9183440944FDE0364
[engine.task.HashTask]                  Hash time: 13.739

As it is not supported in Windows yet, the jar file could be added in plugin folder. The code to support could be:

try {
    Class<?> clazz = Class.forName("com.amazon.corretto.crypto.provider.AmazonCorrettoCryptoProvider");
    Method method = clazz.getMethod("install");
    method.invoke(null);
} catch (Exception e) {
    LOGGER.debug("AmazonCorrettoCryptoProvider not installed", e);
}

[aberenguel]

@lfcnassif Where is the better class to insert this code? Do you think it should be configurable?

[lfcnassif]

Hi @aberenguel! Maybe in the processing Manager, because there are other places that compute hashes, not sure...

I think ExportFileTask would be the one that spend more time with hash computation after HashTask, since it is done for all subitems.

Is this provider loaded by the java service provider mechanism? Because AFAIK any provider installed could be used depending on the service loading order, that is non deterministic... I don't remember if there is a way to prioritize a specific provider if it is installed over the other ones, maybe it is possible.

[aberenguel]

Is this provider loaded by the java service provider mechanism?

Yes. Internally the provider is added as the highest-priority. https://github.com/corretto/amazon-corretto-crypto-provider/blob/296f3821ee8436ea8a311709c0a89e198b19466c/src/com/amazon/corretto/crypto/provider/AmazonCorrettoCryptoProvider.java#L448

  /**
   * Installs the AmazonCorrettoCryptoProvider provider as the highest-priority (i.e. default)
   * provider systemwide.
   */
  public static void install() {
    Security.insertProviderAt(INSTANCE, 1);
  }

[lfcnassif]

Great! Could you take a look if Bouncy Castle dependency uses the same priority? This may cause a conflict or non deterministic behavior...

[aberenguel]

Great! Could you take a look if Bouncy Castle dependency uses the same priority? This may cause a conflict or non deterministic behavior...

The BouncyCastleProvider is added with Security.addProvider which means it is inserted in the end of the provider list (lowest-priority).

IPED/iped-engine/src/main/java/iped/engine/core/Manager.java

Line 162 in 09a8a1e

Security.addProvider(new BouncyCastleProvider());

[lfcnassif]

@arisjr, since you use Linux in your processing farm, this should be of your interest. Just put the Linux x86_64 jar below into IPED's plugin folder and it should work, starting with the future IPED 4.2.0 release:
https://github.com/corretto/amazon-corretto-crypto-provider/releases

[arisjr]

Ótima notícia. Testaremos assim que disponível!