GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps

#1

Post by ummjackson » Fri, May 18, 2018, 3:37 PM UTC

GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps
medium.com

Re: GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps

#2

Post by salad77 » Fri, May 18, 2018, 3:58 PM UTC

But for compliance many interpretations say it's EU /citizens/; I don't think there are 3 simple steps to block any EU citizen...

I'm sure many Governments would love to be able to so simply identify what their citizens do online though.

Re: GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps

#3

Post by jiveturkey » Fri, May 18, 2018, 4:24 PM UTC

salad77 wrote: post #2

But for compliance many interpretations say it's EU /citizens/; I don't think there are 3 simple steps to block any EU citizen... I'm sure many Governments would love to be able to so simply identify what their citizens do online though.

those interpretations are wrong. but even so, blocking eu traffic by IP isn’t sufficient.

Re: GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps

#4

Post by splintercell » Fri, May 18, 2018, 5:13 PM UTC

HN crowd loves GDPR, so get ready for this never making to the front page.

Re: GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps

#5

Post by olliej » Fri, May 18, 2018, 5:15 PM UTC

If you have a side project that siphons personal information from people for no reason, then maybe the gdpr isn’t the problem...

Re: GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps

#6

Post by LinuxBender » Fri, May 18, 2018, 5:24 PM UTC

Geo IP blocking will not block the EU citizens that are not physically in the EU at the time.

Just for fun, I would add

    server {
        # snip....
        access_log  off;
        error_log   off;
        return 307 https://www.google.com/search?q=gdpr;
    }

That should block anyone that might be a EU citizen. /s

Re: GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps

#7

Post by hathathat » Fri, May 18, 2018, 5:24 PM UTC

What would be a GDPR-compliant yet useful access_log setting?

Re: GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps

#8

Post by itake » Fri, May 18, 2018, 5:26 PM UTC

olliej wrote: post #5

If you have a side project that siphons personal information from people for no reason, then maybe the gdpr isn’t the problem...

I don't have time to build user exporting, user deletion, user notifications, amongst other required features on top of the already big backlog of fearures to do.

I use third party tools to help worth logging and error tracking.

Its just not worth my time to support gdpr on a website that makes no money.

Re: GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps

#9

Post by inetsee » Fri, May 18, 2018, 5:27 PM UTC

olliej wrote: post #5

If you have a side project that siphons personal information from people for no reason, then maybe the gdpr isn’t the problem...

My reading of the GDPR says that the MINIMUM fine is 20,000,000 Euros, which I think would be a pretty big problem for an individual working on a side project.

I also think the 403 error page explaining that the GDPR is the reason the visitor can't access the page is a nice touch.

Re: GDPR for side-projects? Blocking all EU traffic with Nginx in 3 simple steps

#10

Post by silsha » Fri, May 18, 2018, 5:42 PM UTC

jiveturkey wrote: post #3

salad77 wrote: post #2

But for compliance many interpretations say it's EU /citizens/; I don't think there are 3 simple steps to block any EU citizen... I'm sure many Governments would love to be able to so simply identify what their citizens do online though.

those interpretations are wrong. but even so, blocking eu traffic by IP isn’t sufficient.

> those interpretations are wrong.

Source?