Malicious Compliance

19680 readers

5 users here now

People conforming to the letter, but not the spirit, of a request. For now, this includes text posts, images, videos and links. Please ensure that the “malicious compliance” aspect is apparent - if you’re making a text post, be sure to explain this part; if it’s an image/video/link, use the “Body” field to elaborate.

======

We ENCOURAGE posts about events that happened to you, or someone you know.
We ACCEPT (for now) reposts of good malicious compliance stories (from other platforms) which did not happen to you or someone you knew. Please use a [REPOST] tag in such situations.
We DO NOT ALLOW fiction, or posts that break site-wide rules.

======

Also check out the following communities:

[email protected] [email protected]

founded 2 years ago

MODERATORS

920

Here's all the source code (lemmy.sdf.org)

submitted 1 year ago by [email protected] to c/maliciouscompliance

88 comments fedilink hide all child comments

In 2000, I wrote a Linux device driver that "decrypted" the output of a certain device, and my company, which hosted open-source projects, agreed to host it.

The "encryption" was only a XOR, but that was enough for the maker of said device to sue my company under 17 U.S.C. § 1201 for hundreds of millions in damages.

The story got a lot of press back then because it highlighted how stupid the then-new DMCA was, and also because there was a David open-source enthusiasts vs. Goliath heartless corporation flavor to it.

Our lawyer decided to pick up the fight to generate free publicity for our fledgling company. For discovery, the maker of the device requested "a copy of any and all potentially infringing source code". They weren't specific and they didn't specify the medium.

So we printed the entire Linux kernel source code including my driver in 5-pt font and sent them the boxes of printouts. Legally they had been served, so there was nothing they could do about it.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 153 points 1 year ago* (last edited 1 year ago) (2 children)

So we printed the entire Linux kernel source code including my driver in 5-pt font

Please tell me you used comic sans.

[–] [email protected] 91 points 1 year ago (2 children)

I hope they did. Now that you mention it, it would have been an amusing twist :)

[–] [email protected] 83 points 1 year ago (1 children)

The year is 2025. A massive geomagnetic storm has fried all forms of technology, wiping out hard drives and solid-state drives alike, and scrambled all backup tapes. Coincidentally, a new plastic-eating bacterium has munched on all the compact discs without anyone noticing.

Humanity will rebuild...

The computer chip manufacturing pipeline has been restored, but there is no software to run them. In a dusty office previously owned by a lawyer from a long-defunct dotcom, a treasure trove is discovered. Five metal cabinets filled with paper: the printed Linux kernel source code, in 5-pt comic sans font. One brave soul will enter to transcribe. Mistakes are not an option. We all thank you for your sacrifice.

[–] [email protected] 23 points 1 year ago

Final twist, nobody can compile it because it uses GCC extensions that no recovered compiler supports.

[–] iks 27 points 1 year ago

Printed in wingdings + given ascii conversion table to decypher

[–] BeigeForce 13 points 1 year ago* (last edited 1 year ago)

Doubly-devilish as it’s not fixed width. Microsoft Bob would be proud.