python273
Smart Voting website is hosted on Google App Engine (appspot.com). The Russian government had no ability to block it for long time without affecting other Google services, since ISPs could block mostly by IP and via DNS spoofing.
To block reliably by domain they would need to have DPI (deep packet inspection) hardware, and most ISPs had no DPI, since it's expensive. Even if they had it, they could only block by domain/ip, not by traffic signatures and reaction time was relatively slow.
Now they improved censorship infrastructure and basically building Great Firewall. As I understand government controlled DPIs are now installed on Internet exchange points. So it's easier to block specific domains and protocols. Recently they:
- were throttling Twitter (and every website with t.co substring, yeah)
- blocked some opposition websites hosted on Appspot
- DNS over HTTPS (DoH) servers used in the app (Google, Cloudflare, OpenDNS)
- Bunny CDN, used in the app
- docs.google.com, telegra.ph (voting list was published there)
- DHT and BitTorrent
- started blocking some VPN providers and attempted to block Wireguard protocol
I think some of blocks (e.g. torrent) were used to test capability. Now that they can slow down websites and block more accurately, they have more leverage over tech companies.
Apps have more ways to avoid blocking than websites and PWAs. E.g. by getting endpoints/data via updates, notifications, domain fronting. So the obvious next step was to attack app stores.
---
You could enter your email on the website, but some of the emails got leaked. Considering many people used personal email addresses, it was possible to combine it with other leaks/DBs to get more personal information. Police visited some people registered on the website. So I guess people trust less giving their email addresses now.
DigitalOcean Support Thursday, March 15, 2018 9:53 PM
Hello,
Thank you very much for bringing this to our attention.
I will create an internal escalation to our images team to review this. :)
[...]And DO still have this in motd for newly created droplets:
Welcome to DigitalOcean's 1-Click Docker Droplet.
To keep this Droplet secure, the UFW firewall is enabled.
All ports are BLOCKED except 22 (SSH), 2375 (Docker) and 2376 (Docker).
Full motd: https://pastebin.com/cdaecHU8Though it links to https://do.co/3j6j3po and it mentions ufw problem:
> Note: The default firewall for the Docker One-Click is UFW, which is a front end to iptables. However, Docker modifies iptables directly to set up communication to and from containers. This means that UFW won’t give you a full picture of the firewall settings. You can override this behavior in Docker by adding --iptables=false to the Docker daemon.