Skip to content
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

GDPR fix may not be great #112

Open
archon810 opened this issue May 17, 2018 · 11 comments
Open

GDPR fix may not be great #112

archon810 opened this issue May 17, 2018 · 11 comments
Assignees

Comments

@archon810
Copy link

Hey @lesterchan,

I just looked at 7c5149a, and from what I can tell you're now substituting the last part of the IP with xxx, like so:

substr( $ip, 0, strrpos( $ip, '.' ) ) . '.xxx'
: string = 123.456.789.xxx

Am I correct in understanding that this will prevent anyone on the same subnet from voting, meaning a single vote will dupe with 255 other IPs, thus potentially disqualifying people in the same office, home, or even unrelated groups of people. And it's done for everyone, not just people in EEU.

I don't know what the right solution here is, and whether salting and storing a one-way hash as an identifier goes against GDPR, but it's something to consider.

Thoughts?

@lesterchan
Copy link
Owner

I am not an GDPR expert. But it seems to me one way hash still can identify the user as all the same hashes means it is from the same user. so it might not be GDPR compliant.

This way was told by a few EU users. So I implemented it. So unfortunately, the subnet issue is a trade off.

@lesterchan
Copy link
Owner

@archon810 since you are a heavy user of this plugin, what do you think? I will probably probably go read yo more when I am back! Oh and Hi!

@archon810
Copy link
Author

I wonder if there's another way to somehow be compliant, or at least restrict the GDPR compliance to EEU countries via some library. Maybe GeoIP?

@lesterchan
Copy link
Owner

Haha the reason I put this sort of “hack” quickly is because I have only two days to do it. And when the deadline comes, I will be in japan (still is) without time to fix it.

Do you think a setting will help? Like GDPr compliant yes? If yes just use the mast the last subnet. If not we just log the full IP?

@archon810
Copy link
Author

Well, not really because it's the visitor's location that matters, not the company's that's hosting the poll. We still have to cater to EEU users even though we're in the US. So a setting like that is pointless, since it needs to be on, but only for EEU users.

@lesterchan
Copy link
Owner

I see. But most GeoIP services are chargeable and if a heavy site uses it, it will hit the free limit pretty soon!

@lesterchan
Copy link
Owner

It seems you can still store the IP if the site consents it. I wonder will it be better to revert this and hook on to the privacy policy page in 4.9.6 to tell this plugin uses your ip to prevent double voting.

@lesterchan
Copy link
Owner

It seems WordPress Comments now also anonymize IP. https://core.trac.wordpress.org/ticket/43442

@lesterchan
Copy link
Owner

It seems other ratings/voting plugins are hashing the IP. So I have done that =)

@archon810
Copy link
Author

What's the plan for the public release?

@lesterchan
Copy link
Owner

@archon810 probably need more people to test it!

@lesterchan lesterchan self-assigned this May 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants