https://github.com/github/dmca/commit/d6b2d97e801dc16d2aeb25...
I am not a lawyer, but I would encourage the people targeted by these notices to find a lawyer and fight back.
Hell, that might just be what github is trying to encourage by open sourcing these notices, to get the community involved and defending against baseless DMCA takedowns.
Procedurally, it looks like a standard infringement takedown case, but as far as I can tell, it isn't covered by that law. Sony's notice probably has no more legal force than any ordinary C&D letter, and GitHub's cooperation probably doesn't get them any guarantee of immunity. Sony's C&D is simply formatted to look like a real DMCA takedown, probably to scare GitHub in to automatically complying without even asking their lawyers.
For all we know, by complying GitHub may have reduced their ability to defend themselves on the basis of the reverse-engineering exception to the circumvention prevention, without gaining any significant legal security.
The DMCA's prohibition on DRM circumvention is in a different section (17 USC 1201) from the section on copyright infringement (17 USC 512), in which the safe harbor/takedown notice stuff is defined. It's not clear to me that DRM circumvention thus qualifies as copyright infringement, or that any of the safe harbor stuff would apply to hosts of circumvention tools.
Certainly, Sony's notice doesn't identify any of their works that are being infringed, so the notice seems to be invalid according to the usual rules, specifically 17 USC 512(c)(3)(A)(ii).
Can anybody more familiar with the law explain what's going on with this? Why is the procedure from 17 USC 512 being applied to a (alleged) violation of 17 USC 1201? Or is this just another flaw in Sony's handling of this mess?