The StorageTek DMCA decision
[Posted August 29, 2005 by corbet]
Last year, StorageTek (soon to be a subsidiary of Sun) brought a suit
against Custom Hardware Engineering, alleging copyright and DMCA
violations. CHE is a third-party maintenance vendor which was offering
maintenance services for StorageTek's tape libraries. To carry out that
maintenance, CHE built a gadget which would intercept diagnostic messages
sent within the library; CHE also had to bypass StorageTek's "GetKey"
system which protected access to those messages. StorageTek claimed that
running the maintenance code (which generates the diagnostic messages) was
a copyright violation, and that bypassing GetKey went against the DMCA's
anticircumvention measures. A U.S. district court agreed, and issued an
injunction shutting CHE's maintenance service (for these libraries) down.
CHE appealed the injunction, and an appeals court has now produced a ruling [PDF] reversing
the injunction. In doing so, the appeals court has placed some limits,
however small, on the application of the DMCA.
This case matters. It is not hard to imagine similar situations which
could affect the free software community. If StorageTek's internal
diagnostic streams are privileged, many other hardware communication paths
may be as well. Consider a closed network adaptor, for which a free,
reverse-engineered driver exists. The vendor could claim that the
communications between the proprietary driver and the firmware on the card
serve as an access to that (copyrighted) firmware, and that the
(undocumented, complex) interface to the card is a technical measure
preventing unauthorized access. By this reasoning, a free driver would be
a DMCA violation. As DRM systems work their way into (what used to be)
general-purpose computers, this sort of issue will come up in that context
as well.
When viewed in this context, the StorageTek decision, while welcome, does
not give much relief. It is a narrow decision which does little to return
control of hardware to those who have purchased (and believe that they own)
it.
The core of the appeals court decision is that CHE's activities did not, in
fact, constitute copyright infringement. The infringement argued by
StorageTek took the form of CHE loading StorageTek's maintenance code into
the library's processor by means of rebooting the machine. This allegedly
infringing activity is the same thing that happens when the owner of the
machine turns it on. This "copying" of the software into RAM might well
have been a copyright infringement, except that the copyright law contains
an explicit exception for third-party maintenance providers. Even in this
case, CHE might not have been in the clear, however; the company prevailed
in the end because StorageTek had never made a clear separation between its
operational and maintenance programs. The whole mess is loaded when the
system boots, so the appeals court decided that it was all necessary to
operate the library.
In other words, if StorageTek had been more careful to keep its maintenance
software separate, and to not load it automatically when the system boots,
it might have gotten through this appeal. The court also notes that
StorageTek could have written its software license agreement to forbid
third parties (such as CHE) from turning on the machine at all - but
didn't.
Once that decision was reached, the court had little trouble with the DMCA
claim. The DMCA, the court decided, is a copyright law. To that end, the
anti-circumvention provision does not stand on its own, but is tied to
the underlying copyright regime. That limits how this provision can be
read:
To the extent that CHE's activities do not constitute copyright
infringement or facilitate copyright infringement, StorageTek is
foreclosed from maintaining an action under the DMCA....
That result follows because the DMCA
must be read in the context of the Copyright Act, which balances
the rights of the copyright owner against the public's interest in
having appropriate access to the work.
In theory, this interpretation means that circumvention, itself, is not a
crime. It is only when that circumvention is part of a violation of
copyright that the DMCA comes in to play. Unfortunately, anything which is
said to "facilitate" copyright infringement will fall on the wrong side of
that line, so there is nothing good in this ruling for DeCSS (for example).
So, in the end, this ruling does little to enable us "consumers" to keep
control over the devices that we believe we own. It is more likely to
serve as a checklist for companies like StorageTek in the future: their
systems are likely to be designed to avoid the pitfalls encountered by
StorageTek in this case. This ruling has, mainly, increased the number of
lawyers that hardware manufacturers must apply to achieve their aftermarket
goals.
Whenever one buys a device containing proprietary
software, one must accept that said device may serve somebody else's
interests. That is in the nature of proprietary software, but that nature
is made worse by current copyright law, which sees the act of paging
software into RAM to execute it as an act of copying which may be
controlled by the copyright owner. The ruling in the StorageTek case has
drawn some boundaries on how far vendors can use copyright law to assert
control over hardware they have sold, but the situation, fundamentally, has
not changed.
(
Log in to post comments)