Why a Locked Floppy Disk Could Be Safer Than a Modern Network

Photo by CCDBarcodeScanner, licensed CC BY-SA 4.0 via Wikimedia Commons.

Dear Cherubs, in the 1990s, office security had the elegance of a locked drawer and the threat model of a very determined coat thief. Floppy disks were the workhorses of the era, and Britannica notes they were popular from the 1970s until the late 1990s, made of flexible plastic coated with magnetic material. Before the internet became an everyday business utility, many workplaces were still mostly offline; Pew Research found that in 1995 only 14% of U.S. adults had internet access, and 42% had never heard of it.

THE LOCKED-BOX LOGIC

If your payroll files, drafts, and backups lived on removable media, the cleanest security move was physical control. Put the disks in a cabinet, lock the cabinet, and hope nobody on the third floor had a master key and a curious streak. It was a blunt system, but it worked because access was local, slow, and obvious. If someone needed a copy, they usually had to walk over, ask, sign something, and maybe endure a suspicious look from whoever guarded the supply room.

That is the part people forget when they romanticize the old days. The security was not magical; the attack surface was just tiny. To steal the data, someone usually had to be in the building, or at least within arm’s reach of the media. Annoyingly low-tech, yes. Also annoyingly effective.

MODERN SECURITY, NEW PROBLEMS

Once files moved onto networks and cloud systems, the game changed. NIST defines intrusion detection as monitoring events in a system or network for signs of possible incidents, and says intrusion prevention systems can also try to stop them. CISA says firewalls shield computers and networks from malicious or unnecessary traffic, while NIST says cryptography is used to protect sensitive digitized information during transmission and while in storage. In other words: the modern office traded one locked box for a whole stack of digital locks, alarms, and panic buttons.

Of course, the modern setup has its own virtues. Data can be backed up automatically, shared instantly, and protected with layered controls that the floppy-disk era never needed. NIST’s storage-encryption guidance still says organizations should physically secure devices and removable media, which is a polite way of saying: the box still matters, even when the box now lives in a server rack. Security did not become less important; it became more complicated, which is basically the same thing with extra meetings.

So yes, a locked plastic box full of floppies could be safer than a badly configured internet-facing system. But that is not because the past was wiser. It is because the past had fewer doors, fewer windows, and fewer strangers trying every handle on the planet at once. Security has always been a trade-off between convenience and control; we just used to do the math with keys instead of passwords.

Sources:
Britannica — https://www.britannica.com/technology/floppy-disk
Pew Research Center — https://www.pewresearch.org/internet/2014/02/27/part-1-how-the-internet-has-woven-itself-into-american-life/
NIST SP 800-94 — https://csrc.nist.gov/pubs/sp/800/94/final
CISA firewalls — https://www.cisa.gov/news-events/news/understanding-firewalls-home-and-small-office-use
NIST SP 800-175B Rev. 1 — https://csrc.nist.gov/pubs/sp/800/175/b/r1/final
NIST SP 800-111 — https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-111.pdf
Wikimedia Commons image page — https://commons.wikimedia.org/wiki/File:Floppy_Disk_HD.jpg

The Thisclaimer logo blends a classic warning symbol with a brain icon to represent critical thinking, curiosity, and thoughtful disclaimers. #cybersecurity #dataSecurity #encryption #firewalls #floppyDisks #internetHistory #intrusionDetection #officeHistory #physicalSecurity #techNostalgia

Little Snitch, the macOS network tool, is now available on Linux

https://squeet.me/display/962c3e10-570ded0e-b43507cbd64709a4

Little Snitch, the macOS network tool, is now available on Linux

“Little Snitch for Linux is written in Rust and uses eBPF for kernel-level traffic interception (this lets sandboxed code run inside the Linux kernel without modifying it). The tool shows processes on your machine making network connections, and giv ...continues

See https://gadgeteer.co.za/little-snitch-the-macos-network-tool-is-now-available-on-linux/

#firewalls #linux #security #technology

Little Snitch, The MacOS Network Tool, Is Now Available On Linux

“Little Snitch for Linux is written in Rust and uses eBPF for kernel-level traffic interception (this lets sandboxed code run inside the Linux kernel without

GadgeteerZA

Blocking Bad Bots With AbuseIPD Blacklist

Sean Conner at The Boston Diaries wrote about trying to block annoying and/or malicious bots from crawling his website. It is a good read. Beginning in late 2024, I started noticing The New Leaf Journal going down periodically. The server logs suggested that it was being overrun by bots and crawlers. I tried various methods to ensure that NLJ would be up all the time, including fiddling with Apache configs and my .htaccess file. I stumbled upon the "solution" (for now, at least) in late […]

https://social.emucafe.org/naferrell/blocking-bad-bots-with-abuseipd-blacklist-04-08-26/

[Reply] Blocking Bad Bots With AbuseIPD Blacklist

I discuss using the AbuseIPD blacklist with Cloudron’s built-in firewall to reduce wasteful traffic to my WordPress websites.

The Emu Café Social

@drscriptt @lobsters I know, because it's basically a poor-persons method of "sharding" data into smaller blocks and then iterating i.e. TXT records

Can you fit a whole game into a QR code?

YouTube
#Google says half of all #zerodays it tracked in #2025 targeted buggy #enterprise tech
Google said security and networking devices, #firewalls, #VPN and #virtualization platforms like Ivanti and VMware, were among targetes last year. All four of the companies said hackers have exploited their products on customer networks in recent months.
The remaining 52% of #zeroday bugs were found in consumer and end-user products, such as those made by Microsoft, Google, and Apple
https://techcrunch.com/2026/03/05/google-says-half-of-all-zero-days-it-tracked-in-2025-targeted-buggy-enterprise-tech/
Google says half of all zero-days it tracked in 2025 targeted buggy enterprise tech | TechCrunch

Enterprise software was a major focus of zero-day activity during 2025, with security and networking devices, like firewalls, VPNs, and virtualization platforms among the most targeted by malicious hackers.

TechCrunch
CAPTCHA check

ayuda #fediverso #redes #seguridad #firewalls

estoy montando un #cluster #proxmox #hibrido un nodo en casa otro en la #nube

tengo muy poca puta idea de firewalls. hasta la fecha, ponia uno en el edge, que bloqueara todo lo feo, y adentro, todo abierto. y aparte de eso, el concepto de un firewall cliente, un firewall servidor

pero me estoy liando que flipas con proxmox. uno a nivel de datacenter. uno a nivel de nodo. uno a nivel de contenedor e incluso puedes activar desactivar por cada tarjeta de red? me estoy volviendo loco. tengo entendido, muy a grandes rasgos que: desde lo mas exterior, hay que bloquear todo salvo los puertos web y VPN. desde lo mas cercano: el contenedor, bloquear todo salvo la actividad de la aplicacion en si, sea la que sea. y en medio, capas inter nodo: la comunicacion entre nodo y contenedores. pero seguramente haya formas mas precisas y correctas de hacerlo. he estudiado esto... un par de horas ayer. no exagero.

me puede alguien ayudar por favor, en guiarme en lograr lo siguiente?

quiero que el cluster pueda comunicar de forma interna (vpn) y externa, exponiendo por netbird.

pensaba tener una vlan 10.0.10.1/24 para interno y 10.0.20.1/24 para exponer

la idea es que la comunicacion interna sea mas laxa, y que al contrario la 20 sea full estricta

en el nodo nube, solo tengo una tarjeta fisica de red con una ip publica.

por ahora lo que tengo hecho es hacer un bridge vlan aware, y de ahi 3 vlans (quiero una para netbird y otra para tailscale. por si se cae una, no quedarme fuera)

tengo forward NAT de la ip publica al bridge

cuando literal, no tengo internet en los contenedores... en el mejor de los casos, no son accesibles los puertos que quiero, el 80 y 443, para desplegar netbird.

y ahi estoy bloqueado.
no hay puta forma de pasar de ese tercer pantallazo.

@t3rr0rz0n3 @z3r0

que estoy haciendo mal? seguramente de mucho a todo. como dije, hasta ahora mis redes eran muy.... libres. y es literal mi primer cluster hibrido y la primera vez que trasteo con vlans.

se agradece mucho #boost

@fboldog @hyc @markhurst @pluralistic interesting, nice that #HLS even has an #RFC, #RFC8216. I've always been wondering why #RTP, which has had many RFCs for decades never got that popular.
Is it mainly because of company and university #firewalls blocking UDP? So we now start to reimplement everything on HTTP(s)?
If only #IPSec, so encryption on layer 3 already instead, had gotten more traction and would be more easy to use...

Blocking Empty UA Outside of Feed Requests

I wanted to add an htaccess rule to NLJ blocking requests from empty user agents (and "-" user agengs). I looked into the best way to do it and found a 2017 answer on Stack Overflow. This solution is interesting because it explicitly allows requests to the site's feed. While I have not noticed empty user agent requests for our feeds, there are many niche feed readers out there, so I went with a modified version of this snippet to be on the safe side.

https://social.emucafe.org/naferrell/blocking-empty-ua-outside-feed-02-04-26/

[Note] Blocking Empty UA Outside of Feed Requests

I borrowed a solution from a Stack Overflow answer for blocking requests from empty UA in my WordPress site’s .htaccess file, exempting requests for feed.

The Emu Café Social