-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Another bunch of potential trackers missing #71
Comments
Hi @IzzySoft Thanks a lot! |
Thanks! I don't expect you'll pick them all. One third would be a good rate I guess – but I thought to send them all nevertheless (couldn't tell which third you'd like 🤣). |
FYI @IzzySoft there are 10 trackers which seem good candidates for an integration into exodus. For the rest, some didn't have package name so I didn't look into them, some didn't match with our list of apps in exodus, some where already in exodus, and the rest I didn't have time to review yet :) |
Thanks for looking into it @simpnu! Yeah, I expected something along those lines. Those without package name come solely from Appbrain (and I haven't found a match yet for them). Some are so unknown that even Appbrain (who lists them) couldn't find a hit (so I wonder why they list them at all)… Btw: I've noticed that one of my "mergers" failed for a while until shortly after I sent you the extract. If you want, I can send you "fresh data" for the above, which might have more package names matching (that's what the merge script does: try to match Appbrain stuff with IDs/packageNames from Exodus and me). Just let me know, I still kept the steps for creating the CSV so it should be a thing of 2 minutes. But probably doesn't change much. |
While you are still processing this, let me add my latest find right away: {
"id": "/com/google/cloud/audit",
"details": "writes audit log entries to Google Cloud Services to help answer the questions of „who did what, where, and when?”",
"name":"Cloud Audit Logs",
"type":"Mobile Analytics",
"url":"https://cloud.google.com/logging/docs/audit"
} |
Are you just looking for buzzwords? Here are a few partial strings that I think of when I try to identify 3rd party undesirables:
|
I added about 30 to my list of things to maybe add to ETIP (which has like 800 companies that may or may not end up being trackers. https://github.com/jawz101/potentialTrackers/blob/master/potentialTrackers.csv |
Nope. Those are libraries my own scanner identified. For yet-unknown-to-me packages I then try to find background information. If they turn out to be trackers, I mark them such – and from time to time bring up small collections of them here. @pnu-s as this issue was dormant now for 2 month, just a little heads-up that you wanted to pick some of the candidates 😉 |
Would @pnu-s try to check some of these?
|
To give you an update, I just reviewed a bunch of the recent additions to ETIP and selected 10 good candidates to be imported into exodus. This will need a second review and then we'll push them there. Then I plan to take a look at the remaining trackers in ETIP and your list @jawz101, but this all takes time 😞 |
Thanks @pnu-s! |
@rivkakarasik did you come across any of these in your recent search? |
@jawz101 I will make a small script with all your entries and check how many times we found each of them in our dataset to have a better idea of good candidates. Btw @pnu-s this script could be useful to "bathc" detection for new tracker. A list in a file and a loop to check each line… Did you think it make sens? |
@jfoucry thank you. In light of your work, it would also be nice to have the ability to submit apps for scanning from the Android app. With approx. 80,000 in the Exodus library, the Exodus library represents about 2% of the apps on Google Play Store. It would be nice to have easier ways to scan apps besides keying in package names on the Exodus website. |
I cannot agree more with you, that's why I already have that script written somewhere. I'll try to take some time to show you someday :) @jawz101 I agree with you about the importance of such a feature (the first option being the easy one - at least for a first implementation). The issue here is that the only person from Exodus Privacy working on the Android app (and who wrote most of it) doesn't have any free time to work on it. So we have a blocking point to improve the app currently :/ |
@pnu-s is your script on the production machine? If yes, just send me a mail with the path, I will have look on it |
@pnu-s I've been in contact with @PerfectSlayer of the Adaway project about asking if someone involved in the Exodus Project might be able to take over maintenance of the Adaway list. Conversely, I wonder if he might be interested in pitching in on the Android app. And, coincidentally, he's French :P And @IzzySoft if you'd ever be interested in participating in the Adaway blocklist you definitely have the understanding of the mobile landscape. |
@jawz101 That's very cool, thanks (again) for everything you are doing! 👍 🥇 |
I've added a new virtual column to my tracker table and found that there are 104 entries which are not covered by Exodus. Table data are based on definitions by Appbrain plus from my own scanner. Condition for the virtual column
is_tracker
is:So I did a
select * from libs where is_tracker=1 and exodus_id is null;
using theINTO OUTFILE
clause of MariaDB (sorry, the JSON functions are not yet available in 10.0 – and no, I cannot simply upgrade but will do eventually). I've added a header line, and attached the results as.gz
here:zz_exodus.csv.gz
I guess not all of them are worth being added (some are almost completely unknown/unused) – but things like
amazon_aws_metrics
oramazon_mobile_analytics
probably are 😉Related for reference: #31
The text was updated successfully, but these errors were encountered: