Alright mates, welcome back to Taverna Linux!
Have you ever stopped to imagine the absolute chaos of counting millions of paper ballots by hand in a country the size of a continent? Total madness, isn’t it? It used to take days — sometimes weeks — to figure out who had won an election in Brazil. But the game changed entirely, and a massive part of that revolution is thanks to our favourite penguin.
In today’s post, we are doing a serious deep dive into the software engineering behind the Brazilian Electronic Voting Machines. We’ll look at how the electoral court ditched a messy web of old operating systems to build Uenux — one of the most heavily audited machines on the planet.
From Chaos to the Penguin: The Arrival of Linux
Back in the early days, the voting machines ran on proprietary systems like VirtuOS and even Windows CE. It was a logistical and cybersecurity headache. Imagine trying to audit closed-source code from private corporations?
That all changed around 2008 when the Superior Electoral Court (TSE) decided to throw out the rulebook and create their own custom Linux distribution: Uenux (short for Urna Eletrônica com Linux). The goal was crystal clear: slash licensing costs, drop the reliance on a single foreign company, and above all, achieve total auditability. Because it’s open-source, researchers and experts could finally look “under the bonnet” of the operating system.
How Does This “Technological Armour” Work?
If you’re picturing the machine running a pretty Ubuntu desktop with flashy graphics, think again. Uenux is what we call an embedded mission-critical system. It has been stripped down to the absolute bare bones to run only what is strictly necessary.
To give you an idea, the system is completely air-gapped. What does that mean? It means it is physically isolated from any external network. No network cards, no Wi-Fi, no Bluetooth. It’s impossible to hack the machine over the internet simply because the machine doesn’t know what the internet is.
Furthermore, the TSE created an incredibly heavy Chain of Trust. To explain it didactically: imagine every bit of software (from the system bootloader to the voting app itself) comes inside a sealed envelope with a unique wax stamp. If the stamp is broken or fake, the machine instantly freezes and shuts down. That wax stamp is a cryptographic digital signature. The Linux Kernel itself was modified to unconditionally reject any code that hasn’t been signed in the TSE’s highly secure vault.
The Government’s Hackathon: Public Security Test (TPS)
No software is 100% perfect, and the Brazilian authorities know this. That’s why, since 2009, they’ve been running the TPS, which is basically an official government hackathon.
They open up the source code to researchers, universities, and federal cybersecurity experts and say: “There’s the machine. Try to break it.” It is a far superior security approach than just trying to hide the code (security by obscurity). When the white-hat hackers find a loophole (like the time they managed to record the acoustic sounds of the keys being pressed), the TSE patches the code and invites them back months later for a Re-test to prove the vulnerability is actually gone.
At the end of the day, the voting machine isn’t secure because nobody knows its code. It is secure precisely because incredibly clever people spend months trying to destroy it, ensuring that on election Sunday, the gears run flawlessly.
Enjoyed the chat? There’s plenty more on our Podcast! 🎧
This post is just the tip of the iceberg! If you want to dive deeper into the technical details of how Linux saves election day, hit play and listen to our full episode.
щ(゜ロ゜щ)
ReplyDelete