Signing problem
wiktorek140 opened this issue ยท 20 comments
Hi. I can't use my compiled ee3 with forestry(latest version from official forestry wiki), beacouse i have error
"[SEVERE] [Forestry] com.pahimar.ee3.EquivalentExchange3 failed validation. Halting runtime for security reasons. Please replace your mods with untampered versions from the official download sites." That i have question, can u pubish a fingerprints or version without checking validation, or short instruction how to fix that?
It's an issue related to my build script (I'm assuming you are running the "release" target and its attempting and failing to sign the jar). Forestry detects that and stops running as it's detected a modified version of EE3.
Expect a new updated build script shortly that should address this issue (I'm changing it so that I only sign the jars on a release, and offering a default "build" target for folks to use when building the mod locally).
Unfortunately this issue is not resolved with your current version, Forestry is still giving fits. Funny thing is.. Forestry is failing it's OWN verification on this as well.
This is an open source mod, licensed under a GPL-family license. You can't seriously advise people not to modify it within the terms of its license, that's insane.
Dude it's a tip, from the pro himself...
It's an advice not an order...
-----Original Message-----
From: Cannibal Vox [email protected]
Date: Mon, 29 Apr 2013 12:01:37
To: pahimar/[email protected]
Reply-To: pahimar/Equivalent-Exchange-3 [email protected]
Subject: Re: [Equivalent-Exchange-3] Signing problem (#312)
This is an open source mod, licensed under a GPL-family license. You can't seriously advise people not to modify it, that's insane.
Reply to this email directly or view it on GitHub:
#312 (comment)
To CoverJaguar> This is an unmodified version of Forestry AND Equivalent Exchange 3 that I am using. I have ZERO clue how I would even modify them if I did. I've redownloaded the files numerous times and keep trying it to the same result.
So.. if anyone has a tip how to solve this I would love to hear.
"Dude it's a tip, from the pro himself... It's an advice not an order..."
"You can't seriously advise people not to modify it within the terms of its license, that's insane."
Do you know what an advice means ? ;)
-----Original Message-----
From: Cannibal Vox [email protected]
Date: Mon, 29 Apr 2013 12:04:52
To: pahimar/[email protected]
Reply-To: pahimar/Equivalent-Exchange-3 [email protected]
Cc: [email protected]
Subject: Re: [Equivalent-Exchange-3] Signing problem (#312)
"Dude it's a tip, from the pro himself... It's an advice not an order..."
"You can't seriously advise people not to modify it within the terms of its license, that's insane."
Reply to this email directly or view it on GitHub:
#312 (comment)
Yeah sorry...
-----Original Message-----
From: Vaygrim [email protected]
Date: Mon, 29 Apr 2013 12:07:59
To: pahimar/[email protected]
Reply-To: pahimar/Equivalent-Exchange-3 [email protected]
Cc: [email protected]
Subject: Re: [Equivalent-Exchange-3] Signing problem (#312)
Can we bring the attention of this thread back to bear on the actual PROBLEM?
Reply to this email directly or view it on GitHub:
#312 (comment)
BOOM, Log: http://pastebin.com/X8Xm6a6P
D/L'ed EE3 from Pahimar's thread, I have zero clue how to actually 'build it myself'.
The post says pre1g
-----Original Message-----
From: Cannibal Vox [email protected]
Date: Mon, 29 Apr 2013 12:10:10
To: pahimar/[email protected]
Reply-To: pahimar/Equivalent-Exchange-3 [email protected]
Cc: [email protected]
Subject: Re: [Equivalent-Exchange-3] Signing problem (#312)
Vaygrim: did you download EE3 from pahimar's thread or build it yourself?
Reply to this email directly or view it on GitHub:
#312 (comment)
Vaygrim: there's nothing in your log that indicates your issue has anything to do with EE.
The reason you are seeing this is because you have 0 clue how to build it yourself.
Run the build target that doesn't sign the jar. You are signing the jar with a sig other than my own, which is why you are getting these with Forestry.
TL:DR - Run "build" not "release," and learn to ant
Higher up, Pahimar posted: "Should be resolved now, please try the updated build script"
Does this not mean that the version he is offering for download is fixed also? Or do I literally have to BUILD a working version of EE3 myself in order to it working?
Updated: Sorry for the confusion, Pahimar. Apparently I misunderstood what you originally stated.