goalrefa.blogg.se

1. Making a tinkertool unbreakable how to#
2. Making a tinkertool unbreakable registration#
3. Making a tinkertool unbreakable verification#
4. Making a tinkertool unbreakable software#

Making a tinkertool unbreakable how to#

Of course, as Don Marti says, they may also be hiding some sort of personally identifying information in a less obvious place, but even in this case it’s probably only a matter of time before someone figures out how to strip this out too.* My point is that as long as Apple doesn’t do this, it would be trivial to write a program that takes the Apple’s DRM-less AAC files as input and outputs fully functional AAC files that have been sanitized of any personally identifying information. Nick, I agree that Apple is highly unlikely to require the headers in all music files. It’s unlikely that we could reliably tell the difference between a scofflaw user and one victimized by malware, so there seems to be no escape from this problem. If punishments are mild, then users might be willing to distribute their own files and claim innocence if they’re caught. If these people are punished severely, the result will be unfair and no prudent person will buy and keep the labeled files.

Which brings us to the usual problem with systems that try to label files and punish people whose labels appear on infringing files.

Making a tinkertool unbreakable software#

This scenario is very plausible, given that as many as 10% of the machines on the Net contain bot software that could easily be directed to swipe iTunes files. If a file is swiped from a customer’s machine and then distributed, you’ll know where the file came from but you won’t know who is at fault. All a digital signature can do is verify that a file is the same one that was sold to a particular customer.

Making a tinkertool unbreakable verification#

Apple could choose to publish this verification key if they wanted to let third parties verify the name information in files.īut there’s another problem – and a pretty big one. There’s a separate key used for verifying that the data hasn’t been modified. (You might worry that somebody could transplant the name header from one file to another, but proper crypto will detect that.) Whether to use this kind of integrity check is a separate question from whether to encrypt the information – you can do either, or both, or neither.įrom a security standpoint, the best way to do guarantee integrity in this case is to digitally sign the name data, using a key known only to Apple. Done right, this would let Apple detect whether the name information in a file was accurate. If you’re not a crypto person, you may not realize that there are different tools for keeping information secret than for detecting tampering – in the lingo, different tools for ensuring confidentiality than for ensuring integrity.Īpple apparently used crypto to protect the integrity of the data. Worse yet, it would be easy to change the data in a file to frame an innocent person – which makes the name information pretty much useless for enforcement. Fred predicts that somebody will make a tool for changing the name to “Steve Jobs” or something. This makes it pretty easy to change the name in a file. More interesting than the lack of encryption is the apparent lack of integrity checks on the data. Randy responded that there was a benefit to letting third parties do enforcement. Or so the theory goes.įred von Lohmann responded, suggesting that Apple should have encrypted the information, to protect privacy while still allowing Apple to identify the original buyer if necessary. It would be easy for Apple, or a copyright owner, to identify the culprit. Randy Picker suggested that this might be designed to deter copying – if you redistribute a file you bought, your name would be all over it.

Public static final ArmorMaterial ARMOR_MATERIAL_COLORITE = EnumHelper.addArmorMaterial("armor_material_colorite", Reference.MOD_ID + ":colorite", 0, new int, 100, SoundEvents.ITEM_ARMOR_EQUIP_DIAMOND, 0.0F) Įdit: I haven't changed anything, but now for some reason the helmet and chestplate are unbreakable and unenchantable, while the boots and leggings still take damage and are enchantable.Recently it was revealed that Apple’s new DRM-free iTunes tracks come with the buyer’s name encoded in their headers. Public static final ToolMaterial DAGGER_MATERIAL_COLORITE = EnumHelper.addToolMaterial("dagger_material_colorite", 3, 0, 24.0F, 16.0F, 100)

public static final ToolMaterial TOOL_MATERIAL_COLORITE = EnumHelper.addToolMaterial("tool_material_colorite", 3, 0, 24.0F, 26.0F, 100)

Making a tinkertool unbreakable registration#

Any ideas? here's my init registration code for these. The prior works just fine, and only makes it so you can see the durability bar, which I don't like, but while the latter makes the item unbreakable, it can't be enchanted. I found two solutions so far: the obvious one, giving the item millions for a durability value and the second, setting the durability as 0 or a negative to make it infinite. I'm trying to make a set of armor and tools that I've made unbreakable.