DMCA Vs Hacker

This week featured a large kerfuffle over a hack that you probably read about here on Hackaday: [Neutrino] wedged an OLED screen and an ESP32 into a Casio calculator. REACT, an anti-counterfeiting organization, filed DMCA copyright takedowns on Casio’s behalf everywhere, including GitHub and YouTube, and every trace of [Neutrino]’s project was scrubbed from the Internet.

The DMCA is an interesting piece of legislation. It’s been used to prevent people from working on their tractors, from refilling printer ink cartridges, and to silence dissenting opinions, but it’s also what allows us to have the Internet that we know and love, in a sense.

In particular, the “safe harbor” provision absolves online platforms like YouTube and GitHub from liability for content they host, so long as they remove it when someone makes a copyright claim on it. So if a content owner, say Casio, issues a takedown notice for [Neutrino]’s GitHub and YouTube content, they have to comply. If he believes the request to be made in error, [Neutrino] can then file a counter-notice. After ten to fourteen days, presuming no formal legal action has been taken, the content must be reinstated. (See Section 512(g).)

cardboard cnc machineBoth the takedown notice and counter-notice are binding legal documents, sworn under oath of perjury. Notices and counter-notices can be used or abused, and copyright law is famously full of grey zones. The nice thing about GitHub is that they publish all DMCA notices and counter-notices they receive, so here it is for you to judge yourself.

Because of the perjury ramifications, we can’t say that the folks at REACT who filed the takedown knowingly submitted a bogus request in bad faith — that would be accusing them of breaking federal law — but we can certainly say that it looks like they’re far off base here. They’re certainly not coders.

The good news is that the code is back up on GitHub, but oddly enough the video describing the hack is still missing on YouTube.

But here’s how this looks for Casio and REACT: they saw something that was unflattering to a product of theirs — that it could be used for cheating in school — and they sent in the legal attack squad. If that’s the case, that’s rotten.

This article is part of the Hackaday.com newsletter, delivered every seven days for each of the last 200+ weeks. It also includes our favorite articles from the last seven days that you can see on the web version of the newsletter.

Want this type of article to hit your inbox every Friday morning? You should sign up!

Spacing Out: All The Orbital News You’re Missing

We keep finding more great space stories than we can cover, so here’s a speed-run through the broader picture of the moment as it applies to space flight.

The big news this week was the first launch of a manned SpaceX Crew Dragon capsule to the ISS. I was excited because the pass en route to the space station was scheduled to be visible from the UK at dusk, and on Wednesday evening I perched atop a nearby hill staring intently at the horizon. Except it had been cancelled due to bad weather. The next launch window is planned for today and you can watch it live.

Meanwhile, fashion is the other piece of this manned-launch’s appeal. Their sharply-designed spacesuits have attracted a lot of attention, moving on from the bulky functional Michelin Man aesthetic of previous NASA and Roscosmos garments for a positively futuristic look that wouldn’t be out of place in Star Trek. Never mind that the two astronauts are more seasoned space dog than catwalk model, they still look pretty cool to us. Against the backdrop of a political upheaval at the top of NASA, this first crewed orbital mission from American soil since the retirement of the Shuttle has assumed an importance much greater than might be expected from a run-of-the-mill spaceflight.

While we’re on the subject of the ISS, it’s worth noting that we’re approaching twenty years since the first crew took up residence there, and it has been continuously crewed ever since as an off-planet outpost. This is an astounding achievement for all the engineers, scientists, and crews involved, and though space launches perhaps don’t have the magic they had five decades ago it’s still an awe-inspiring sight to see a man-made object big enough to discern its shape pass over in the night sky. We understand that current plans are to retain the station until at least 2030, so it’s a sight that should remain with us for a while longer.

Closer to Earth are a couple of tests for relative newcomers to the skies. When Richard Branson’s Virgin group isn’t trying to boot millionaires off the planet through its Virgin Galactic operation, it’s aiming to cheaply fling small satellites into orbit from a rocket-toting airborne Boeing 747 with its Virgin Orbit subsidiary. Their first test launch sadly didn’t make it to space, once the rocket had flawlessly launched from the airliner it suffered a fault and the mission had to be aborted. Getting into space is hard.

The second test was never intended to make it into space, but is no less noteworthy. The British company Skyrora have performed a successful ground test of their Skylark L rocket, aiming for a first launch next year and for offering low-earth orbit services by 2023. This is significant because it will be the first British launch since the ill-fated Black Arrow launch in 1971, and with their Scottish launch site the first ever from British soil. If you’ve seen Skyrora mentioned here before, it is because they were behind the retrieval of the Black Arrow wreckage from the Aussie outback that we mentioned when we wrote about that programme.

Looking forward to the coming week, especially today’s rescheduled SpaceX launch. This time however, I’ll check the weather conditions before climbing any hills.

Books You Should Read: The Design Of Everyday Things

With everything from APIs to Raspberry Pis making it even easier for us to create and share objects shaped by personal whim, it’s high time that Don Norman’s sage design advice falls on not just the design student, but the hardware hacker and DIY enthusiast too. Grab yourself a coffee and a free weekend, and settle into the psychology of people-struggling-how-to-use-that-widget-they-just-purchased in The Design of Everyday Things: Revised and Expanded Edition.

Who’s to blame for a door that opens with a pull when everything about how it looks says it should open with a push? In Don Norman’s world, it’s not you; its the designer. Enter a world where blame is inverted and mistakes can be critically categorized. Norman takes us example by example showing us how common items in the world poorly serve the needs of their user, mainly because the designer simply ignores key aspects of our humanity. This book is a crisp, concise overview of human psychology when applied to engaging with things combined with a language of ideas to help us apply this psychology to better interactions. (And it reads like butter!)

Opening Up to the Language of Design

What’s an affordance, you might ask? Well, simply put, it’s a way that an object can be used by a human. How about a signifier? That’s a communication “signposting” scheme that object uses to suggest to you how it should be used. If that sounds a bit fluffy, just think about the last time you tried to push open a door that needed to be pulled. Something about that door was suggesting that you could push it open, but it couldn’t! It “fooled” you because all the object’s signifiers were telling you otherwise. Continue reading “Books You Should Read: The Design Of Everyday Things”

Hackaday Podcast 069: Calculator Controversy, Socketing SOIC, Metal On The Moon, And Basking In Bench Tools

Hackaday editors Mike Szczys and Elliot Williams march to the beat of the hardware hacking drum as they recount the greatest hacks to hit the ‘net this week. First up: Casio stepped in it with a spurious DMCA takedown notice. There’s a finite matrix of resistors that form a glorious clock now on display at CERN. Will a patio paver solve your 3D printer noise problems? And if you ever build with copper clad, you can’t miss this speedrun of priceless prototyping protips.

Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Direct download (60 MB or so.)

Continue reading “Hackaday Podcast 069: Calculator Controversy, Socketing SOIC, Metal On The Moon, And Basking In Bench Tools”

This Week In Security: Leaking Partial Bits, Apple News, And Overzealous Contact Tracing

Researchers at the NCCGroup have been working on a 5-part explanation of a Windows kernel vulnerability, targeting the Kernel Transaction Manager (KTM). The vulnerability, CVE-2018-8611, is a local privilege escalation bug. There doesn’t seem to be a way to exploit this remotely, but it is an interesting bug, and NCCGroup’s work on it is outstanding.

They start with a bit of background on what the KTM is, and why one might want to use it. Next is a handy guide to reverse engineering Microsoft patches. From there, they describe the race condition and how to actually exploit it. They cover a wide swath in the series, so go check it out.

Left4Dead 2

Just a reminder that bugs show up where you least expect them, [Hunter Stanton] shares his story of finding a code execution bug in the popular Valve game, Left4Dead 2. Since the game’s code isn’t available to look at, he decided to go the route of fuzzing. The specific approach he took was to fuzz the navigation mesh data, part of the data contained in each game map. Letting the Basic Fuzzing Framework (BFF) run for three days turned up a few possible crashes, and the most promising turned out to have code execution potential. [Hunter] submitted the find through Valve’s HackerOne bug bounty program, and landed a cool $10k bounty for his trouble.

While it isn’t directly an RCE, [Hunter] does point out that malicious mesh data could be distributed with downloadable maps on the Steam workshop. Alternatively, it should be possible to set up a fake game server that distributes the trapped map. Continue reading “This Week In Security: Leaking Partial Bits, Apple News, And Overzealous Contact Tracing”

Hackaday Prize And Conservation X Labs Issue Design Challenges To Address Extinction Crisis

When most people think of extinct species, they likely imagine prehistoric creatures such as dinosaurs or woolly mammoths. Extinction is something you read about in history books, nature’s way of removing contestants in the great game of life. It’s a product of a cruel and savage world, and outside of a few remaining fringe cases, something that humanity’s advanced technology has put a stop to.

Unfortunately, the truth is far more complicated than that. The planet is currently going through its sixth major extinction event, and this time, it’s our fault. Humanity might not be willfully destroying the natural habitats of the plants, fish, birds, and other lifeforms that have been eradicated, but we’re responsible for it just the same. Humans are an apex predator unlike any the world has ever seen before, and the only force that can stop us is ourselves.

Founded in 2015, Conservation X Labs is devoted to doing everything it can to end this sixth wave of extinction. Unsatisfied with the pace of traditional conservation, they leverage technology and open innovation to develop unique new ways of combating the damage our species has done to life on this planet. After all, it’s the only one we’ve got.

We’ve partnered with this organization to help develop solutions to some of these problems. This includes an open call challenge that anyone can enter, and a Dream Team program that you can get involved with if you act quickly. Let’s take a look at what Conservation X Labs is all about, and what is involved with the challenges at hand.

Continue reading “Hackaday Prize And Conservation X Labs Issue Design Challenges To Address Extinction Crisis”

Peeking Inside Executables And Libraries To Make Debugging Easier

At first glance, both the executables that a compiler produces, and the libraries that are used during the building process seem like they’re not very accessible. They are these black boxes that make an application go, or make the linker happy when you hand it the ‘right’ library file. There is also a lot to be said for not digging too deeply into either, as normally things will Just Work™ without having to bother with such additional details.

The thing is that both executables and libraries contain a lot of information that normally is just used by the OS, toolchain, debuggers and similar tools. Whether these files are in Windows PE format, old-school Linux a.out or modern-day .elf, when things go south during development, sometimes one has to break out the right tools to inspect them in order to make sense of what is happening.

This article will focus primarily on the Linux platform, though most of it also applies to BSD and MacOS, and to some extent Windows.

Continue reading “Peeking Inside Executables And Libraries To Make Debugging Easier”