User talk:GeoSn0wOLD

Firmware Manager page
Hi there! I noticed that you created a program to help facilitate decrypting firmware files. While all of us encourage contributions, we have had issues with an influx of GUI wrappers (specifically VFDecrypt GUIs) in the past. In addition, as the creator of the program, I think it would be best for an unsolicited person to add your program — otherwise, it looks a little like you're trying to use The iPhone Wiki as a billboard to advertise on. (Listings on the Main Page are also reserved for software with a unique function and a significant number of users.) As such, I made the decision to delete your page from the wiki, as this appeared to conflict with section 3.8 of the Ground rules. If you have any questions about my decision, feel free to respond to this message. --Dialexio (talk) 03:33, 12 October 2015 (UTC)
 * -M'kay. Can I publish it as a page if I don't list it to main page? It has 3192 users.
 * That's an oddly specific number. (If it's a download count, do keep in mind one person might download it multiple times... but I digress.) I suppose that it's fine, considering the feature set and amount of users it has. I'll undelete the page so you don't have to recreate it from scratch. --Dialexio (talk) 00:57, 25 October 2015 (UTC)
 * MM'kay, thanks You can rest asure the app will be updated with more and more features so that will be useful for all users. Have a great day and thanks for recovering the page.

--GeoSn0w

Firmware Manager Source Code
I wish to inform you that as your app uses xpwn applications (specifically xpwntool and hfs), the GNU General Public License requires you to release your source code under the GNU GPL v3. --5urd (talk) 22:12, 3 November 2015 (UTC)
 * For sure, may I create a Github repo for it? --The preceding unsigned comment was added by GeoSn0w (talk). Please consult this page for more info on how to sign pages, and how to fix this.
 * A GitHub repo with the source code is fine— it's disclosing the source code, after all. Please address this issue promptly, though— otherwise, I will delete the page once again by the end of the month. (libimobiledevice is also licensed under the similar GNU GPL v2.) --Dialexio (talk) 19:21, 28 November 2015 (UTC)
 * Git REPO for GPL v3 version (not including my graphical design and icons) is available on https://github.com/GeoSn0w/Firmware-Manager-GPLv3
 * I see that you made a GitHub repo, but I do not see any of the required source code in it. --Dialexio (talk) 23:10, 29 November 2015 (UTC)
 * Pay more attention. Check this one https://github.com/GeoSn0w/Firmware-Manager-GPLv3/blob/master/StartSmart.vb
 * It's from the same repo (StartSmart is the main form).
 * There is no source code for any of the components from XPwn or libimobiledevice that you used. Heck, "xpwn" appears exactly once in that file, and it's only a reference to xpwntool.exe (which isn't even provided in the repo).
 * On an unrelated note, please add your signature to future talk page entries— you can do this by either typing, or clicking the second-to-last button in the editing toolbar (next to the horizontal line). --Dialexio (talk) 16:59, 30 November 2015 (UTC)

Sorry to say, but I have to teach you VB.NET. Let's roll. The source code for example has this:

Private Sub Button12_Click(sender As Object, e As EventArgs)

Dim psi As ProcessStartInfo Dim pat1 As String = Application.StartupPath Dim procname = pat1 + "/Data/xpwntool.exe" Dim filename = TextBox9.Text Dim newfile = TextBox7.Text Dim kapa = "-k" Dim iv = TextBox10.Text Dim ivname = "-iv" Dim key = TextBox8.Text Dim args = String.Format(" {0} {1} {2} {3} {4} {5}", filename, newfile, kapa, key, ivname, iv) psi = New ProcessStartInfo(procname, args) Dim proc As New Process proc.StartInfo = psi proc.Start

End Sub

In this code, is the actual part where I call xpwntool with some parameters. Dim procname = pat1 + "/Data/xpwntool.exe" will call the app from Data folder, and Dim args = String.Format(" {0} {1} {2} {3} {4} {5}", filename, newfile, kapa, key, ivname, iv) are parameters to be passed (from textboxes and radiobuttons of the gui). proc.start will launch the app xpwntool from App's Data folder and will pass the parameters to it as it is a CLI.

The same for libi where code is:

Private Sub Button21_Click(sender As Object, e As EventArgs)

Dim psi2 As ProcessStartInfo Dim proc As New Process Dim process3 = pat1 + "/Data/idevicerestore.exe" Dim udid = udidval.Text Dim ipswname1 = ipswname.Text Dim param1 = param.Text Dim finalpatch = TextBox16.Text Dim args3 = String.Format("{0}{1} {2} {3}", parameter1, udid, param1, ipswname1) psi2 = New ProcessStartInfo(process3, args3) proc.StartInfo = psi2 proc.Start proc.WaitForExit If proc.HasExited = True Then MsgBox("Finish Message", MsgBoxStyle.Information) End If   End Sub The code is pasted here from https://github.com/GeoSn0w/Firmware-Manager-GPLv3/blob/master/StartSmart.vb If you don't know Vb.NET please let someone you trust and knows to analyze the source.

--GeoSn0w (talk) 21:48, 30 November 2015 (UTC)
 * I have no problem admitting that I don't know VB.NET. However, you don't even need to know VB.NET to know that this isn't the source code for xpwntool— there's no way you ported xpwntool to VB.NET (which is all I saw in the repo), and you just mentioned yourself that you're calling xpwntool. (I saw this in your repo, and was able to conclude prior to your explanation that you were calling xpwntool.) That's like telling me that this simple shell script:

/usr/local/bin/xpwntool
 * 1) !/bin/bash
 * …is the source code for xpwntool, which it clearly isn't. Don't get me wrong— it's fine if your program calls xpwntool. However, your release violates the GNU GPL because you are bundling a copy of xpwntool, and you are not providing the source code for said copy of xpwntool. --Dialexio (talk) 23:57, 30 November 2015 (UTC)

But I don't port it to VB.NET, I used the already compiled one and called it. Just point me out what to add to repo and I will :)

From what I understand about GPL (yes, this is my first release under GPL). I need to make MY source code public as GPL, but what if I use binaries? What is the actual code of xpwntool and how should I insert it into my repo?

In this case I must add the used binaries?

I have added xpwn-source from https://github.com/planetbeing/xpwn and all binaries used. --GeoSn0w (talk) 01:23, 1 December 2015 (UTC)
 * All you needed to add was the source code for the copy of xpwntool that you're using. (The same applies to any other GPL-licensed components you're using, including but not limited to libimobiledevice.) Please refer to the GNU GPL v2.0 and v3.0 for any further questions about the GPL and its requirements. --Dialexio (talk) 01:45, 1 December 2015 (UTC)
 * Source code for the parts of libimobiledevice you use (and possibly other GPL-licensed components) is still missing. --Dialexio (talk) 07:21, 2 December 2015 (UTC)

Yes, sorry, I'mma create a good repo tonight!--GeoSn0w (talk) 21:29, 5 December 2015 (UTC)

The new REPO containing all sources - Hopefully https://github.com/GeoSn0w/F.C.E.-365-Firmware-Manager GeoSn0w (talk) 21:49, 7 December 2015 (UTC)
 * Hey, why not just create git submodules for the libraries/tools used? Also, VB.Net is easy to learn and all, but dump it for C# or even C or C++ when you can. Trust me, you won't regret it. --Haifisch (talk) 00:05, 8 December 2015 (UTC)