this post was submitted on 27 Jul 2023
10 points (100.0% liked)

Malicious Compliance

19145 readers
1 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.

======

======

Also check out the following communities:

!fakehistoryporn@lemmy.world !unethicallifeprotips@lemmy.world

founded 1 year ago
MODERATORS
 

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.

top 7 comments
sorted by: hot top controversial new old
[–] Ret2libsanity@infosec.pub 2 points 1 year ago

I stare at Linux source code very often looking for vulnerabilities.

I unironically have printed pages out to sit down with.

The idea of having the whole kernel printed… is… fun. Lol. How would your organize it for reading? Different chapters that are the directories of the kernel code ?

[–] aard@kyu.de 1 points 1 year ago (1 children)

Did the device happen to be the CueCat?

[–] Blackmist@feddit.uk 1 points 1 year ago

Now that's a name I haven't heard in a long time.

The guy who invented it sounds like a certified nutcase.

In 2016, Pulitzer appeared as a treasure hunter on The Curse of Oak Island on the History Channel. He searched for the Ark of the Covenant and working with amateur historians from the Ancient Artifact Preservation Society he claimed that a sword found in the waters off Oak Island in Nova Scotia had "magical magnetic properties" and was evidence of Roman presence in North America and contact with the Miꞌkmaq, which a historian of that people dismissed. An archaeologist and a science writer criticized Pulitzer's claim, suggested the sword was a replica said that Pulitzer threatened to sue them.

Certainly sounds like the same guy.

[–] BeigeForce@lemmy.world 1 points 1 year ago (1 children)

You’re the hero that GitHub needs.

[–] JackbyDev@programming.dev 1 points 1 year ago (1 children)

The irony is that nowadays you could just say "well, the codes open source and all hosted on GitHub..."

[–] TeoTwawki@lemmy.world 1 points 1 year ago

Double irony is they'd also send a takedown to github claiming the code contains their IP due to being too ignorant to comprehend that none of the code contains any of thiers to do what it does

[–] Kinglink@lemmy.world 1 points 1 year ago

Legally they had been served, so there was nothing they could do about it.

Somehow I doubt this.

Maybe it's true but legally I know in California you are required to do your briefs in 12 point font. While that's briefs, I would imagine evidence would be under the same banner. It definitely WOULD be illegal to do it in 1 pt font or intentionally making it unreadable. I would imagine if the other side wanted to make it an issue they could back to the judge and he's probably have it out with you.

Maybe the lawyers wisely replaced your malicious compliance with correct sized print with out telling you, maybe the other side didn't care.