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 50 comments

sorted by: hot top controversial new old
[–] 158 points 3 years ago* (5 children)

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

Please tell me you used comic sans.

  • source
  • hideshow 5 child comments
  • [–] [S] 96 points 3 years ago (3 children)

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

  • source
  • parent
  • hideshow 3 child comments
  • [–] 92 points 3 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 120 points 3 years ago (23 children)

    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 ?

  • source
  • hideshow 23 child comments
  • [–] 85 points 3 years ago* (5 children)

    Why would they organize it in any way? It was not one of the requirements… so, alphabetically.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 24 points 3 years ago (4 children)

    Obviously and we are talking per line and not per file are we?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 24 points 3 years ago (14 children)

    I'd love to hear more about this - do you do it professionally (for preventative reasons), as a side hobby, or as an attacker for malicious/selfish reasons? No judgement, genuinely curious as it takes a certain personality type to do this kind of work and I find it really interesting.

  • source
  • parent
  • hideshow 14 child comments
  • [–] 34 points 3 years ago (2 children)

    I think they just stare at it, hoping the vulnerabilities come to them in a moment of revelation. A Linux Joseph Smith, the kernel playing the part of the Golden Plates.

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (2 replies)
    [–] 93 points 3 years ago (3 children)

    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.

  • source
  • hideshow 3 child comments
  • [–] 42 points 3 years ago (1 child)

    I don't think the font size matters too much in this, it's just the printing the whole source code, including a lot of not directly relevant things, and sending all of that over in a few boxes instead of sharing the project files with them that is very malicious.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 57 points 3 years ago (11 children)

    So you like source code? Well then! HAVE ALL THE SOURCE CODE IN THE WORLD!

  • source
  • hideshow 11 child comments
  • [–] 27 points 3 years ago (10 children)
  • [–] 44 points 3 years ago (14 children)

    Just out of curiosity...
    How many pages were there?

  • source
  • hideshow 14 child comments
  • [–] [S] 123 points 3 years ago* (13 children)

    I don't know. I didn't do the printing. The law firm did it. But I remember our lawyer mentioning that they fedexed over 20 cartons of printing paper. Assuming 500 sheets per ream and 5 reams per carton, that would be 50,000 sheets, or 100,000 pages since it was printed on both sides to be even more annoying.

  • source
  • parent
  • hideshow 13 child comments
  • [–] 26 points 3 years ago (6 children)

    Damn. Did they ever find your actual source code in there

  • source
  • parent
  • hideshow 6 child comments
  • load more comments (5 replies)
  • [–] 37 points 3 years ago (3 children)

    You’re the hero that GitHub needs.

  • source
  • hideshow 3 child comments
  • [–] 20 points 3 years ago (2 children)

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 31 points 3 years ago

    I was a tech journalist in the early 00's and I remember writing about that story or one like that.

    A similar thing happened with Microsoft, who either delivered or was served the full documentation of some office format printed out. It's a pretty popular form of malicious compliance, also paying people in bags of coins.

  • source
  • [–] 24 points 3 years ago (3 children)

    Please tell me all the newlines were removed from the source code and it was minified to save paper.

  • source
  • hideshow 3 child comments
  • [–] 21 points 3 years ago (1 child)

    Did the device happen to be the CueCat?

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 10 points 3 years ago

    Amazing! What a great story.

  • source
  • [–] 8 points 3 years ago (1 child)

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

    Pretty sure the can go to the judge and as you to deliver the information in a more friendly format.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 8 points 3 years ago

    Should have sent it xor since they already know how to decode it.

  • source
  • [–] 7 points 3 years ago

    "only an xor" would pretty much imply any of most stream ciphers. It's what you xor with that matters.

  • source
  • [–] 6 points 3 years ago

    It makes me happy to know people are pulling these capers. What was the divisor polynomial?

  • source
  • load more comments
    view more: next ›