升级到最新的Oracle JDK 1.8.0_121-b13丢失了PBEWithMD5AndDES算法 [英] Upgrade to latest Oracle JDK 1.8.0_121-b13 loses PBEWithMD5AndDES Algorithm

查看:686
本文介绍了升级到最新的Oracle JDK 1.8.0_121-b13丢失了PBEWithMD5AndDES算法的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

获取:导致:java.lang.Throwable:java.security.NoSuchAlgorithmException:PBEWithMD5AndDES SecretKeyFactory不可用

Getting: Caused by: java.lang.Throwable: java.security.NoSuchAlgorithmException: PBEWithMD5AndDES SecretKeyFactory not available

这与1.8.0_111一起使用 - 什么是最好的解决方法为了向后兼容(例如,使用PBEWithMD5AndDES?j

This worked with 1.8.0_111 -- what is the best workaround for backward compatibility (e.g., to read data obfuscated with PBEWithMD5AndDES?j

推荐答案

读取数据,我相信我已经搞砸了对新安装的JDK的各种引用,导致对121版本和111版本的引用的混合可能导致错误。

I apologize -- I believe I had screwed up the various references to the newly installed JDK that resulted in a mixture of references to both the 121 release and the 111 release that likely caused the error.

查看JAVA_HOME后声明,eclipse.ini vm条目,Java / Installed VM设置和eclipse启动器JRE设置,并确保它们都指向相同的JDK安装位置,问题已经消失。

After reviewing the JAVA_HOME declaration, the eclipse.ini vm entry, the Java / Installed VM settings, and the eclipse launcher JRE setting and ensuring they all pointed to the same JDK installation location, the problem has gone away.

感谢大家的帮助,我会尝试删除任何旧的剩余JDK安装,以确保只有一个活动。

Thank you all for trying to help. I'll try to remove any old remnant JDK installations to ensure only one is active.

这篇关于升级到最新的Oracle JDK 1.8.0_121-b13丢失了PBEWithMD5AndDES算法的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆