Thanks @richardk that is definitely the culprit.
Of the data sent, the only two that can be considered a bit worrying are:
Unique System ID - probably made up from a few serial numbers from various pieces of hardware on the system. Most processors will have a CPU serial number, the hard disks each have a number, and each network card will have a unique MAC address.
IP address - from this your ISP and country can be determined.
Must however mention that the “internal” network address will not be known, it will be your
public IP address assigned by your ISP.
As @rorywalsh mentioned, this analytical data sending, has been included from several versions back.
The question is, what to do about it, if anything?
On any given day, I use Windows, Mac and Linux (Debian) but currently,
only trying Cabbage on Windows, hence the solutions I’ve written about, pertain only to that OS.
My approach then was as follows:
- Modify my hosts file.
- Patch/modify any VSTs that I already compiled.
- Patch/modify my existing version of Cabbage so that future VSTs are “taken care of”.
Found this much easier and quicker than trying to find a version of Cabbage without it.
(and certainly much less work than re-compiling Cabbage).
This of course, may not suit other users that are concerned with the analytical data and have
supplied plugins to clients or, use another OS.
For now, I only intend to use Cabbage on Windows and for my own personal use, so I’m sorted.
The patching can of course be applied to Mac and Linux as well, albeit slightly differently.
This then negates the need to change the current version of Cabbage being used.
@rorywalsh can I send you a PM with the details rather?
You can then decide if you would like to implement the patching of existing plugins via a dedicated
program with versions for the different OS’s.
The user then has several options:
Do nothing, carry on as before, it’s not that big of a threat anyway, but it is irritating and sneaky.
Upgrade to another version that does not contain the sending of analytical data.
Patch the existing version of Cabbage and any plugins that have already been made.
This would involve a program (one per OS) that Rory could make available on the Cabbage website.
You could call it the…“CabbagePatch”… Couldn’t resist, sorry.