Acheron.exe
Member
- Downloaded
- 33.5 GB
- Uploaded
- 443.1 GB
- Ratio
- 13.21
- Seedbonus
- 56,030
- Upload Count
- 0 (0)
Member for 1 years
Some intersting facts about FlipPDF:
If one were to hypothetically download and install FlipPDFPlusPro, extract the zip that the official download gives you such that you have an installer with the md5sum 55e11e2c7c5ceb648149ef6832d72dfc, run the program and open the electron dev tools with 'CTRL SHIFT i', use the electron debugger until the file 'index.f0b8fd22.js' gets loaded, then pretty-print the file and navigate to line 47612, the following lines of javascript would be visible:
Here is a table I made with the strings found in the aforementioned lines:
How the publisher constructs the URLs hosting the current builds of each of the versions:
Here's where I need help: What should be done with this information? It would seem a shame to do nothing with these strings that the software publisher incredibly helpfully left in their app. A friend who downloaded the referenced files using the URL construction above verified that the strings were indeed useful. After using the correct string in one of the FlipPDF products, files that match the following get generated in directories that match the following:
Those files are non-transferrable, but the active.bin is able to succeed when applied to the appropriate edition of the app.
If one were to hypothetically download and install FlipPDFPlusPro, extract the zip that the official download gives you such that you have an installer with the md5sum 55e11e2c7c5ceb648149ef6832d72dfc, run the program and open the electron dev tools with 'CTRL SHIFT i', use the electron debugger until the file 'index.f0b8fd22.js' gets loaded, then pretty-print the file and navigate to line 47612, the following lines of javascript would be visible:
JavaScript:
, xT = vn((()=>(0,
n._)("span", null, "plus: NBWDY-YXSMW-NVBDG-FADYZ", -1)))
, IT = vn((()=>(0,
n._)("br", null, null, -1)))
, ET = vn((()=>(0,
n._)("span", null, "pro: HXPYG-XZOAB-WXKXH-MFIUF", -1)))
, _T = vn((()=>(0,
n._)("br", null, null, -1)))
, LT = vn((()=>(0,
n._)("span", null, "corp: RECBN-IQFIW-KYYTX-PPVBN", -1)))
, DT = vn((()=>(0,
n._)("br", null, null, -1)))
, FT = vn((()=>(0,
n._)("span", null, "cmdLine: RIWXP-KKCSI-RKIIA-GUCZT", -1)))
, HT = vn((()=>(0,
n._)("br", null, null, -1)))Here is a table I made with the strings found in the aforementioned lines:
| Product | Version | IsSuccessful? | Installer md5sum | StringUsed | DownloadedFileName |
|---|---|---|---|---|---|
| FlipPDFPro | 4.26.19.0 (Latest) | Yes | 55e11e2c7c5ceb648149ef6832d72dfc |
Code:
| Flip_PDF_Plus_Pro_x64.zip |
| FlipPDFPlus | 6.25.5 (Latest) | Yes | 0179ca3a47f3743ae03f8e9b8e3dc507 |
Code:
| Flip_PDF_Plus_x64.zip |
| FlipPDFCorp | 6.12.19 (Latest) | Yes | 648720c60c9c0c612082e81c6247e772 |
Code:
| Flip_PDF_Plus_Corp_x64.zip |
How the publisher constructs the URLs hosting the current builds of each of the versions:
Code:
https\://static.flipbuilder.com/download/flippdf2/DownloadedFileNameHere's where I need help: What should be done with this information? It would seem a shame to do nothing with these strings that the software publisher incredibly helpfully left in their app. A friend who downloaded the referenced files using the URL construction above verified that the strings were indeed useful. After using the correct string in one of the FlipPDF products, files that match the following get generated in directories that match the following:
Code:
%appdata%\\com\.wonderidea\.newflippdf(corp|pro|)\\active\.bin
%appdata%\\com\.wonderidea\.newflippdf(corp|pro|)\\macs\.fmz
%appdata%\\com\.wonderidea\.newflippdf(corp|pro|)\\eleStore\\config\.json
Last edited: