News for hackers. Stuff that matters.

A comment on Privacy: Is That iPhone?. Parent comment

Re:Privacy: Is That iPhone? by thenewnewguy on Tuesday November 12, 2019 @09:53PM (#21520795)
The point is that the app can just record the old IDFA, and when the IDFA changes whoever is doing the comparison between two apps knows that the old and new IDFA are one and the same.
[ Parent | on HN ]
Re:Privacy: Is That iPhone? by tgsovlerkhgsel on Wednesday November 13, 2019 @02:30AM (#21521823)
A likely-good-enough fix would be for Apple to first make extremely clear that this is not allowed, then catch one ad framework/library provider violating the rule and ban every single app/publisher using it to ensure the rule is actually taken seriously.
[ Parent | on HN ]
Re:Privacy: Is That iPhone? by scarface74 on Wednesday November 13, 2019 @05:30AM (#21522652)
How do you “catch” them? The ID is sent from the app and not in plaintext.
[ Parent | on HN ]
Re:Privacy: Is That iPhone? by tgsovlerkhgsel on Friday November 22, 2019 @01:23AM (#21603284)
Through the usual software analysis methods (reverse engineering, static and dynamic analysis, ...)
[ Parent | on HN ]
Re:Privacy: Is That iPhone? by afiori on Wednesday November 13, 2019 @08:07AM (#21523567)
I imagine with the usual review process
[ Parent | on HN ]
Re:Privacy: Is That iPhone? by scarface74 on Wednesday November 13, 2019 @07:51PM (#21531616)
The review process can’t tell the contents of the data being sent back.
[ Parent | on HN ]
Re:Privacy: Is That iPhone? by marc3842h on Wednesday November 13, 2019 @05:53AM (#21522783)
What I think is that if the ID would be reused this would be kinda eliminated? I don't see a reason to not make them reusable.
[ Parent | on HN ]