Perhaps I'll sacrificially destroy my stockpile of iridium reinforced tungsteel blocks and make our space station out of manylyuum (i'm sure that's spelled wrong) blocks instead
Make it out of wood planks.
Perhaps I'll sacrificially destroy my stockpile of iridium reinforced tungsteel blocks and make our space station out of manylyuum (i'm sure that's spelled wrong) blocks instead
I still don't think people realize what kind of code bomb Greg made.
Calling it a code bomb is overstating things a bit. Throwing a hard-to-catch exception is not exactly tricky code, and there are a number of folk who already check their compiled code signatures to avoid reverse-engineered versions of their mod flying around. Contrast, say, turning bees into bombs, and it lacks even elegance.No. Bombs are not security measures. They destroy things.
Every mod for Minecraft, by default, runs with the same permissions as the initiating user, and a very large array of commands. For most Windows folk -- and even a large percentage people starting to learn Linux -- that's more than enough to do a lot of negative things. Java has some tools to lock down permissions further, but it's never been the most secure platform, and you'll have to understand how to apply a Java SecurityManager and/or separate users sandboxes to really nail it down further.If greg can make the game crash, can he also compile code to install viruses in the background? Just wondering.
FlowerChild had a number of code design level disagreements with other/new parts of the Forge team, and decided to go through a different implementation process (JarMod, rather than ForgeModLoader-style), and then the profanity came out. It's a bit disrespectful to compare that to this GT action.So, Greg is the new FlowerChild?
What he has done is quite literally the definition of a code bomb. It is a piece of code that crashes the program deliberately under certain circumstances. In this case, the circumstances are 'if anyone tries to make a recipe which is identical to one of mine with different results'. This isn't code signature checking to avoid reverse-engineered versions of his mod. This is 'I want this recipe to be this way, and if anyone else wants a different result, then I'll just crash the user'. This is attacking the *user* for something another mod author did.Calling it a code bomb is overstating things a bit. Throwing a hard-to-catch exception is not exactly tricky code, and there are a number of folk who already check their compiled code signatures to avoid reverse-engineered versions of their mod flying around. Contrast, say, turning bees into bombs, and it lacks even elegance.
I can agree with this.But it is remarkably immature, and pushing me further away from the GT modsphere, especially combined with the other changes and the automatic updating functionality. I've got my Minecraft instances reasonably well sandboxed, but most people don't, and I can't in good conscience encourage folk to be automatically downloading trusted code from a source I can't trust.
Aside, why is Greg mad at Immibis? Besides being contentious, Greg says he "always responds to attacks" which is why Immibis is on the pumpkin of shame list. What did immibis code?
Lol look at Lambert's and Hoff's posts. XD.
I looked at them and I couldn't agree more. He says his "real" user base is small. I say that it wouldn't be so small if he weren't such an annoying prat.
It is about to get smaller if FTB pulls him.
If? More like when. Greg rarely communicates with them, whereas MDiyo is constantly talking to them.It is about to get smaller if FTB pulls him.
If greg can make the game crash, can he also compile code to install viruses in the background? Just wondering.
I personally dont feel go0d about a guy who shows no remorse for what he has done. You know what they say about people with no remorse....
If greg can make the game crash, can he also compile code to install viruses in the background? Just wondering.
I personally dont feel go0d about a guy who shows no remorse for what he has done. You know what they say about people with no remorse....
Possibly, though the game crashing is a built in function designed so that if a program detects an error it can shut down quickly and safely with a message, rather than actually crashing and possibly freezing up the entire java application. GT is just abusing the function to make it so Minecraft wouldn't run.
Well if he ever actually did create a virus that's distributed through his mod, he'd likely be in quite a bit of trouble.
Well if he ever actually did create a virus that's distributed through his mod, he'd likely be in quite a bit of trouble.
Let me give you a thought that could keep you up at night: How would you know if he did?
From a code perspective, the difference between "throw EverythingStopsWorkingException;" and "FileOutputStream.getChannel.transferFrom();" is pretty much trivial, and there's no way to lock the latter down without disabling multiplayer (and causing a lot of other problems). The tricky part to applying malicious code is saving it to disk (which can be blocked at the SecurityManager or the user level) and then getting the OS to run it.Possibly, though the game crashing is a built in function designed so that if a program detects an error it can shut down quickly and safely with a message, rather than actually crashing and possibly freezing up the entire java application. GT is just abusing the function to make it so Minecraft wouldn't run.
That's less a definition, and more an ipse dixit. At the very least, it's not worth being talked up as a novel superweapon from the code writing perspective.What he has done is quite literally the definition of a code bomb. It is a piece of code that crashes the program deliberately under certain circumstances. In this case, the circumstances are 'if anyone tries to make a recipe which is identical to one of mine with different results'. This isn't code signature checking to avoid reverse-engineered versions of his mod. This is 'I want this recipe to be this way, and if anyone else wants a different result, then I'll just crash the user'. This is attacking the *user* for something another mod author did.