这种情况你遇到过吗?
[SEVERE] [ForgeModLoader] minecraft jar 文件:/home/una/.local/share/PrismLauncher/libraries/com/mojang/minecraft/1.6.4/minecraft-1.6.4-client.jar!/net/minecraft/client/ClientBrandRetriever.class 似乎已损坏!Minecraft 遭到严重篡改,Minecraft 极有可能无法正常运行!请立即停止,获取一份完整副本并重试!
[SEVERE] [ForgeModLoader] 出于安全考虑,FML 不会启动 Minecraft。你需要重新获取一份完整的 minecraft jar 文件。
[SEVERE] [ForgeModLoader] 技术信息:类 net.minecraft.client.ClientBrandRetriever 本应与 minecraft jar 文件关联,并为我们返回一个有效且完整的 minecraft jar 位置。但此操作未成功。要么是你修改了 minecraft jar 文件(如果是这样,请重新运行 Forge 安装程序),要么你正在使用一个更改了此类(可能还有其他类)的基础编辑版 jar。如果你确实想在此配置下运行 Minecraft,请在启动器配置的 'JVM 设置' 中添加参数 -Dfml.ignoreInvalidMinecraftCertificates=true。
没?那这个呢?
[SEVERE] [Forestry] railcraft.common.core.Railcraft 验证失败。出于安全原因,运行时已中止。请使用来自官方下载站点的未经篡改的模组版本替换你的模组。
进程以代码 1 退出。
这是由于较新的 Java 8 版本放弃了对 SHA-1 签名的支持,而这些旧版本依赖这些签名来进行考虑不周且实现糟糕的“防篡改检测”。(FML 的初衷是善意的——它只是想警告那些安装了 jar 格式模组的用户,它们将无法正常工作。)
与其尝试移除这种检测并触发谁知道会引发何种“反盗版”检查(特别是 Forestry 1.2 版本对此闻名遐迩——还记得最初的 Technic Pack 吗?),SHA-1 Redemption 直接侵入 Java 的核心机制,重新启用对 SHA-1 签名的信任。
这将适用于任何版本的 Minecraft,事实上也适用于任何 Java 程序。我已经为最常出现此问题的版本打上了标签。
警告
SHA-1 是一个已损坏的算法,不再值得信赖——这正是支持被移除的原因。现在向 Java 程序添加此 nilmod 意味着签名基础设施也不再可信。在 Minecraft 整合包的背景下这没问题,因为我们绕过的系统由于实现错误已经彻底崩坏。
然而,在其他签名具有实际意义的场景中,不应使用此方法。请考虑编辑你的 Java 安全策略以添加更针对性的例外,或者如果你能做到的话,重新签署受影响的 jar 文件。
Has this ever happened to you?
[SEVERE] [ForgeModLoader] The minecraft jar file:/home/una/.local/share/PrismLauncher/libraries/com/mojang/minecraft/1.6.4/minecraft-1.6.4-client.jar!/net/minecraft/client/ClientBrandRetriever.class appears to be corrupt! There has been CRITICAL TAMPERING WITH MINECRAFT, it is highly unlikely minecraft will work! STOP NOW, get a clean copy and try again!
[SEVERE] [ForgeModLoader] For your safety, FML will not launch minecraft. You will need to fetch a clean version of the minecraft jar file
[SEVERE] [ForgeModLoader] Technical information: The class net.minecraft.client.ClientBrandRetriever should have been associated with the minecraft jar file, and should have returned us a valid, intact minecraft jar location. This did not work. Either you have modified the minecraft jar file (if so run the forge installer again), or you are using a base editing jar that is changing this class (and likely others too). If you REALLY want to run minecraft in this configuration, add the flag -Dfml.ignoreInvalidMinecraftCertificates=true to the 'JVM settings' in your launcher profile.
No? How about this:
[SEVERE] [Forestry] railcraft.common.core.Railcraft failed validation. Halting runtime for security reasons. Please replace your mods with untampered versions from the official download sites.
Process exited with code 1.
This is caused by newer Java 8 releases dropping support for SHA-1 signatures, and these older versions rely on those for ill-considered and poorly implemented "tamper detection". (FML's reasoning is benign, at least — it wants to warn people who have installed jar mods that it won't work correctly.)
Rather than attempt to remove this detection and trigger god-knows-what kind of "anti-piracy" checks (Forestry for 1.2 is particularly well known for this — remember the original Technic Pack?), SHA-1 Redemption hacks into Java's guts to re-enable SHA-1 signature trust.
This will work on any version of Minecraft, or indeed any Java program. I've tagged support for the versions where this problem is most frequently seen.
Warning
SHA-1 is a broken algorithm that can no longer be trusted — this is why support was removed. Adding this nilmod to a Java program now means the signing infrastructure also cannot be trusted. This is fine in the context of Minecraft modpacks, where the systems we're bypassing are already horribly broken due to implementation mistakes.
However, in another context, where the signing is actually meaningful, this really should not be used. Consider editing your Java security policy to add a more targeted exception instead, or re-signing the affected jars if you can.
评论 0
登录后参与评分
还没有评论,来抢沙发吧