After trying to have the Kodi team and myself reach out to SUUP and no response, I discussed taking over the DEV after my own use cases needed more feedback of what was actually going on while the tool ran and solve the output of 0KB file result issue. I spent some time developing and updating the existing tool and it is nearly ready. The main feature that is NOT ready is the ability for it to update. The mechanism is still in place, the notification still shows, but there is nothing to call home to. I will at some point get that working but for now, let’s just see if the update passes the muster before I spend time in an area that may or may not require my time. I am still knee deep in Madnox skinning, so this was a diversion, but I think it improves the overall user experience and will be interested in your thoughts and feedback.
I would personally like to thank SUUP directly if this is seen. Thanks for a good tool and providing me a starting point. Feel free to reach out to me if warranted.
Now, for the gotcha. I can’t state this more emphatically, this version of it is NOT a virus, of any kind, in any way, the source is clearly available for you to dissect, review, piss on, whatever. I know exactly what that sounds like when you read it or hear it from someone on the internet, all the red flags go up. What has happened here even has my head shaking…. and the cliff notes are basically this: The program used to DEV this is called AutoIt, totally free to use, download or you can edit with Notepad if you really want to. The entire thing is basically a GUI script converted for ease of use. You are probably saying, ok then, what’s the deal. Well my understanding is that the signatures that the program uses have been flagged by multiple AV companies even if the script is not maliciously written. It had me questioning it at the beginning what was going on, turns out, AutoIt is a nice fast why to deliver hacks, keygens, worms, Trojans and anything else that you can think of, so now, it is flagged like crazy. You can send your file to the AVs to whitelist it, but what a PITA is to do and it takes time.
Why not just rewrite it in VB, or C++, because it is a PITA and there is no direct converter (if there is, show me!) and I have multiple other things going on. It seems the x32 gets hit harder than x64, but they are both built as the same time, I assume the dependencies are what cause it to fail AV scanning one over the other.
I even did a test where I built, literally, as single line of code in the default project creator, added a call to the library, compiled that, and submitted it to VirusTotal and it was flagged as malicious. literally, 1 line of code that basically does nothing but import a keyboard.dll….. high malicious score…. so you can thank the script kiddies for that.
If you’ve made it this far, you can see the initial development starting here (Video in a post & also shown below):
https://forum.kodi.tv/showthread.php?tid…pid3188440
The source, x32, x64 are all on GitHub, they will not be part of my skin repo and act as a separate tool. If more comes of it, I will consider getting the updater going as I will be maintaining this for quite a while as I use it in my skin dev.
If there are any questions, issues, comments, all will be handle HERE, not on GitHub, I want all info centralized in one location and it makes the most sense to do it here.
Hopefully you find the update worthy and of use. If it ultimately meets the Kodi’s team requirements, maybe they can/will link it in the WIKI page which still points to v2.9.2.
Verbiage hybrid copy from SUUP’s original tool thread (with updated links):
How to decompile:
1. Select Source File.
2. Select Destination Directory/Folder
3. Press Start
4. Wait until done.
How to compile:
1. Select source
2. Select Destination
3. Press Start
4. Wait until done.
Download (32 Bit)Download (64 Bit)Github Source FilesExample Usage (Video):
http://www.kittmaster.com/imagedump/kodi…iTool.html