Tue Apr 23 21:28:45 2024
EVENTS
 FREE
SOFTWARE
INSTITUTE

POLITICS
JOBS
MEMBERS'
CORNER

MAILING
LIST

NYLXS Mailing Lists and Archives
NYLXS Members have a lot to say and share but we don't keep many secrets. Join the Hangout Mailing List and say your peice.

DATE 2018-04-01

HANGOUT

2024-04-23 | 2024-03-23 | 2024-02-23 | 2024-01-23 | 2023-12-23 | 2023-11-23 | 2023-10-23 | 2023-09-23 | 2023-08-23 | 2023-07-23 | 2023-06-23 | 2023-05-23 | 2023-04-23 | 2023-03-23 | 2023-02-23 | 2023-01-23 | 2022-12-23 | 2022-11-23 | 2022-10-23 | 2022-09-23 | 2022-08-23 | 2022-07-23 | 2022-06-23 | 2022-05-23 | 2022-04-23 | 2022-03-23 | 2022-02-23 | 2022-01-23 | 2021-12-23 | 2021-11-23 | 2021-10-23 | 2021-09-23 | 2021-08-23 | 2021-07-23 | 2021-06-23 | 2021-05-23 | 2021-04-23 | 2021-03-23 | 2021-02-23 | 2021-01-23 | 2020-12-23 | 2020-11-23 | 2020-10-23 | 2020-09-23 | 2020-08-23 | 2020-07-23 | 2020-06-23 | 2020-05-23 | 2020-04-23 | 2020-03-23 | 2020-02-23 | 2020-01-23 | 2019-12-23 | 2019-11-23 | 2019-10-23 | 2019-09-23 | 2019-08-23 | 2019-07-23 | 2019-06-23 | 2019-05-23 | 2019-04-23 | 2019-03-23 | 2019-02-23 | 2019-01-23 | 2018-12-23 | 2018-11-23 | 2018-10-23 | 2018-09-23 | 2018-08-23 | 2018-07-23 | 2018-06-23 | 2018-05-23 | 2018-04-23 | 2018-03-23 | 2018-02-23 | 2018-01-23 | 2017-12-23 | 2017-11-23 | 2017-10-23 | 2017-09-23 | 2017-08-23 | 2017-07-23 | 2017-06-23 | 2017-05-23 | 2017-04-23 | 2017-03-23 | 2017-02-23 | 2017-01-23 | 2016-12-23 | 2016-11-23 | 2016-10-23 | 2016-09-23 | 2016-08-23 | 2016-07-23 | 2016-06-23 | 2016-05-23 | 2016-04-23 | 2016-03-23 | 2016-02-23 | 2016-01-23 | 2015-12-23 | 2015-11-23 | 2015-10-23 | 2015-09-23 | 2015-08-23 | 2015-07-23 | 2015-06-23 | 2015-05-23 | 2015-04-23 | 2015-03-23 | 2015-02-23 | 2015-01-23 | 2014-12-23 | 2014-11-23 | 2014-10-23 | 2014-09-23 | 2014-08-23 | 2014-07-23 | 2014-06-23 | 2014-05-23 | 2014-04-23 | 2014-03-23 | 2014-02-23 | 2014-01-23 | 2013-12-23 | 2013-11-23 | 2013-10-23 | 2013-09-23 | 2013-08-23 | 2013-07-23 | 2013-06-23 | 2013-05-23 | 2013-04-23 | 2013-03-23 | 2013-02-23 | 2013-01-23 | 2012-12-23 | 2012-11-23 | 2012-10-23 | 2012-09-23 | 2012-08-23 | 2012-07-23 | 2012-06-23 | 2012-05-23 | 2012-04-23 | 2012-03-23 | 2012-02-23 | 2012-01-23 | 2011-12-23 | 2011-11-23 | 2011-10-23 | 2011-09-23 | 2011-08-23 | 2011-07-23 | 2011-06-23 | 2011-05-23 | 2011-04-23 | 2011-03-23 | 2011-02-23 | 2011-01-23 | 2010-12-23 | 2010-11-23 | 2010-10-23 | 2010-09-23 | 2010-08-23 | 2010-07-23 | 2010-06-23 | 2010-05-23 | 2010-04-23 | 2010-03-23 | 2010-02-23 | 2010-01-23 | 2009-12-23 | 2009-11-23 | 2009-10-23 | 2009-09-23 | 2009-08-23 | 2009-07-23 | 2009-06-23 | 2009-05-23 | 2009-04-23 | 2009-03-23 | 2009-02-23 | 2009-01-23 | 2008-12-23 | 2008-11-23 | 2008-10-23 | 2008-09-23 | 2008-08-23 | 2008-07-23 | 2008-06-23 | 2008-05-23 | 2008-04-23 | 2008-03-23 | 2008-02-23 | 2008-01-23 | 2007-12-23 | 2007-11-23 | 2007-10-23 | 2007-09-23 | 2007-08-23 | 2007-07-23 | 2007-06-23 | 2007-05-23 | 2007-04-23 | 2007-03-23 | 2007-02-23 | 2007-01-23 | 2006-12-23 | 2006-11-23 | 2006-10-23 | 2006-09-23 | 2006-08-23 | 2006-07-23 | 2006-06-23 | 2006-05-23 | 2006-04-23 | 2006-03-23 | 2006-02-23 | 2006-01-23 | 2005-12-23 | 2005-11-23 | 2005-10-23 | 2005-09-23 | 2005-08-23 | 2005-07-23 | 2005-06-23 | 2005-05-23 | 2005-04-23 | 2005-03-23 | 2005-02-23 | 2005-01-23 | 2004-12-23 | 2004-11-23 | 2004-10-23 | 2004-09-23 | 2004-08-23 | 2004-07-23 | 2004-06-23 | 2004-05-23 | 2004-04-23 | 2004-03-23 | 2004-02-23 | 2004-01-23 | 2003-12-23 | 2003-11-23 | 2003-10-23 | 2003-09-23 | 2003-08-23 | 2003-07-23 | 2003-06-23 | 2003-05-23 | 2003-04-23 | 2003-03-23 | 2003-02-23 | 2003-01-23 | 2002-12-23 | 2002-11-23 | 2002-10-23 | 2002-09-23 | 2002-08-23 | 2002-07-23 | 2002-06-23 | 2002-05-23 | 2002-04-23 | 2002-03-23 | 2002-02-23 | 2002-01-23 | 2001-12-23 | 2001-11-23 | 2001-10-23 | 2001-09-23 | 2001-08-23 | 2001-07-23 | 2001-06-23 | 2001-05-23 | 2001-04-23 | 2001-03-23 | 2001-02-23 | 2001-01-23 | 2000-12-23 | 2000-11-23 | 2000-10-23 | 2000-09-23 | 2000-08-23 | 2000-07-23 | 2000-06-23 | 2000-05-23 | 2000-04-23 | 2000-03-23 | 2000-02-23 | 2000-01-23 | 1999-12-23

Key: Value:

Key: Value:

MESSAGE
DATE 2018-04-18
FROM From: "Donald Robertson, III, DBD"
SUBJECT Subject: [Hangout - NYLXS] Meet the latest DRM Drones
From hangout-bounces-at-nylxs.com Thu Apr 19 09:39:58 2018
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: from www2.mrbrklyn.com (www2.mrbrklyn.com [96.57.23.82])
by mrbrklyn.com (Postfix) with ESMTP id 63C8816113A;
Thu, 19 Apr 2018 09:39:50 -0400 (EDT)
X-Original-To: hangout-at-www2.mrbrklyn.com
Delivered-To: hangout-at-www2.mrbrklyn.com
Received: by mrbrklyn.com (Postfix, from userid 1000)
id 7A663161134; Thu, 19 Apr 2018 09:39:44 -0400 (EDT)
Resent-From: Ruben Safir
Resent-Date: Thu, 19 Apr 2018 09:39:43 -0400
Resent-Message-ID: <20180419133943.GA12971-at-www2.mrbrklyn.com>
Resent-To: hangout-at-mrbrklyn.com
X-Original-To: ruben-at-mrbrklyn.com
Delivered-To: ruben-at-mrbrklyn.com
Received: from eggs.gnu.org (eggs.gnu.org [208.118.235.92])
by mrbrklyn.com (Postfix) with ESMTP id 1892F161132
for ; Wed, 18 Apr 2018 17:33:33 -0400 (EDT)
Received: from crmserver2p.fsf.org ([208.118.235.223]:46516)
by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
(Exim 4.71)
(envelope-from )
id 1f8uhp-0001DL-53
for ruben-at-mrbrklyn.com; Wed, 18 Apr 2018 17:33:33 -0400
Received: from localhost ([127.0.0.1] helo=my.fsf.org)
by crmserver2p.fsf.org with esmtp (Exim 4.86_2)
(envelope-from )
id 1f8uho-0000GU-U2
for ruben-at-mrbrklyn.com; Wed, 18 Apr 2018 17:33:32 -0400
MIME-Version: 1.0
From: "Donald Robertson, III, DBD"
job_id: 156575
To: Ruben Safir
Precedence: bulk
X-CiviMail-Bounce: crmmailer+b.156575.33640053.f9b07a9961a0eaf0-at-fsf.org
Date: Wed, 18 Apr 2018 17:33:32 -0400
Message-Id:
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
Subject: [Hangout - NYLXS] Meet the latest DRM Drones
X-BeenThere: hangout-at-nylxs.com
X-Mailman-Version: 2.1.17
Reply-To: "Donald Robertson, III, DBD"
List-Id: NYLXS Tech Talk and Politics
List-Unsubscribe: ,

List-Post:
List-Help:
List-Subscribe: ,

Content-Type: multipart/mixed; boundary="===============0575501776=="
Errors-To: hangout-bounces-at-nylxs.com
Sender: "Hangout"

--===============0575501776==
Content-Type: multipart/alternative;
boundary="=_b7ba445a6ab2d6ba73689644f71c8d05"

--=_b7ba445a6ab2d6ba73689644f71c8d05
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=utf-8

*Read online and share: https://www.defectivebydesign.org/blog/meet_latest_drm_drones*


Dear Ruben Safir,

The latest round of opposition comments in the Digital Millennium
Copyright Act's (DMCA) exemption process shows which government
entities oppose user freedom.

Back during the last round of the DMCA anti-circumvention exemptions
process, we wrote about the [DRM Drones who were opposing
exemptions][0]. These companies, along with the [US Environmental
Protection Agency][1] (EPA), were trying to stifle the work of
activists working to claw back a bit of freedom in the face of the
DMCA's draconian provisions. A few years later, and it's a new round
of the exemptions process, with perhaps some new faces, but the same
old problem.

[0]: https://www.defectivebydesign.org/meet-the-drm-drones
[1]: https://www.defectivebydesign.org/epa-drm-drone

As we've often said, Digital Restrictions Management (DRM) is not
about copyright, it's about control. And these opposition comments
truly demonstrate that that is the case. The DMCA is allegedly meant
to aid in copyright enforcement, but goes about its task in the worst
way possible, creating legal penalties for circumventing DRM. By
itself, DRM is harmful to users, who all have the right to control
their own computing. Adding legal penalties only compounds the harm of
DRM. Even if DRM were an effective tool for enforcing copyright (and
if copyright were not already extremely excessive), it is unethical to
place such onerous control over users.

So what does the US Food and Drug Administration (FDA), or the US
Federal Aviation Administration (FAA) for that matter, care about
enforcing copyright? The reality is that they don't, but they realize
the nefarious power of DRM to lock down and control users for any
purpose, using copyright as an excuse. Like the EPA, the FDA and the
FAA are also trying to use DRM to enforce the laws and regulations
they are tasked with upholding.

The cause [the FDA and FAA][2] have chosen to champion is the ability
to force users to buy particular feedstock for 3D printers. These
printers take simple materials and transform them into virtually
anything a user can imagine, but you still need that base material
(known as feedstock) in order to print anything. Companies want to use
DRM on their 3D printers so they can lock users into only using their
feedstock, believing that they thereby will reap a large financial
benefit. The FDA apparently worries about users using non-approved
feedstock to create 3D-printed medical devices. The FAA has the same
concern for aviation parts.

[2]:http://advancedmanufacturing.org/controls-feedstock-used-3d-printers/

Do any of these purposes have anything to do with copyright? No, none
whatsoever, except for the fact that the DMCA exists. Because the
DMCA's anti-circumvention provisions prop up the use of DRM, these
companies and agencies want to use it for all their non-copyright
related purposes. DRM is a tool of control, and instead of just doing
their job, the FDA and the FAA want copyright law to do it for them.

Their laziness is harmful to users, as the current exemption for 3D
printers has a qualification that it does not apply to any software or
device "which is subject to legal or regulatory oversight or a related
certification process."

A lawyer for Shapeways Inc. submitted the new exemption, pointing out
that as currently written, it renders the exemption as a whole
useless, as virtually any use could be subject to some other
non-copyright regulation. The Free Software Foundation (FSF) submitted
the sole comment in support of the updated exemption. We are fighting
to end DRM and the DMCA anti-circumvention exemptions process, but
until we achieve that goal, [we support every single exemption][3] that is
proposed. The FDA and FAA should join us in this goal, stop trying to
use the DMCA for their own purposes, and start supporting the rights
of users.

[3]: https://www.defectivebydesign.org/blog/help_fight_against_dmca_anticircumvention_rules_december_15th

Next up is the [National Association of Secretaries of State][4]
(NASS), representing 40 different US state governments. NASS are
apparently unfamiliar with the fact that security through obscurity is
a recipe for disaster. They've submitted opposition comments trying to
stop an exemption for security researchers. Being able to circumvent
DRM's obstruction in order to test the security of a device or piece
of software is one of the most important reasons why DRM is so
damaging. How can anyone trust a device or piece of software if they
can't pull it apart and study its internals?

[4]: https://www.copyright.gov/1201/2018/comments-021218/class10/Class_10_Opp'n_National_Association_of_Secretaries_of%20State.pdf

NASS thinks that letting security researchers test the security of
voting machines would somehow make those machines less secure. But as
everyone else knows by now, you can't make a system secure by
pretending it can never be cracked. The only way to verify its
security is to test it, and to have lots of people test it. As in the
case of the FDA and the FAA, there are other legal tools already
available for punishing anyone who tries to damage or interfere with
elections. So why try to rope copyright law into this entirely
unrelated matter? Again, the only reason these government officials
are getting involved is because they want the control that DRM
provides, a level of control they have no ethical right to exert.

During the last exemption round, we were afraid that the EPA meddling
in the DMCA anti-circumvention process was only the beginning. We
worried that more and more, the government would seek to turn the DMCA
anti-circumvention penalties and the DRM controls it supports into a
further tool of oppression. This latest round of exemptions does
nothing to dispel that fear. It's getting worse and worse. If we don't
act now, government will begin to use DRM to control every aspect of
our lives. If you thought having corporations controlling the keys to
your digital life was a nightmare, it is about to get infinitely
worse.

The time to fight back is now. Here is what you need to do:

If you microblog, please share the following messages (or your own)
with the hashtag #DRMshame:

*-at-US_FDA You should be ashamed of yourself for trying to use Digital
Restrictions Management to do your job #DRMshame
*

*-at-FAANEWS You should be ashamed of yourself for trying to use Digital
Restrictions Management to do your job #DRMshame
*

*-at-NASSorg Security through obscurity does not work, say no to Digital
Restrictions Management #DRMshame *

We strongly suggest that if you use [Twitter][5], you do it in a way
that avoids using proprietary software.

[5]: https://www.fsf.org/twitter

Here's what else you can do:

* Sign up for the FSF's monthly newsletter, [the *Free Software
Supporter*][6], to keep up to date on all the latest news in free
software.

* To help fund our work, consider [donating][7] to the Free Software
Foundation, or becoming an [Associate Member][8].

[6]: https://www.fsf.org/free-software-supporter/
[7]: https://donate.fsf.org
[8]: https://www.fsf.org/join

Sincerely,

Donald Robertson, III
Licensing & Compliance Manager
--
* Follow us at .
* Subscribe to our blog via RSS at .
* Donate to support the campaign at .

You can unsubscribe from the Defective by Design mailing list by visiting the link .

To stop all email from the Free Software Foundation, including
Defective by Design and the Free Software Supporter newsletter, click
this link: .

Defective by Design is a campaign of the Free Software Foundation:

51 Franklin St, Fifth Floor
Boston, Massachusetts 02110-1335
United States

--=_b7ba445a6ab2d6ba73689644f71c8d05
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8








































Read online and share: https://www.defectivebydesign.org/blog/meet_latest_drm_drones





Dear Ruben Safir,



The latest round of opposition comments in the Digital Millennium Copyright Act's (DMCA) exemption process shows which government entities oppose user freedom.



Back during the last round of the DMCA anti-circumvention exemptions process, we wrote about the DRM Drones who were opposing exemptions. These companies, along with the US Environmental Protection Agency (EPA), were trying to stifle the work of activists working to claw back a bit of freedom in the face of the DMCA's draconian provisions. A few years later, and it's a new round of the exemptions process, with perhaps some new faces, but the same old problem.



As we've often said, Digital Restrictions Management (DRM) is not about copyright, it's about control. And these opposition comments truly demonstrate that that is the case. The DMCA is allegedly meant to aid in copyright enforcement, but goes about its task in the worst way possible, creating legal penalties for circumventing DRM. By itself, DRM is harmful to users, who all have the right to control their own computing. Adding legal penalties only compounds the harm of DRM. Even if DRM were an effective tool for enforcing copyright (and if copyright were not already extremely excessive), it is unethical to place such onerous control over users.



So what does the US Food and Drug Administration (FDA), or the US Federal Aviation Administration (FAA) for that matter, care about enforcing copyright? The reality is that they don't, but they realize the nefarious power of DRM to lock down and control users for any purpose, using copyright as an excuse. Like the EPA, the FDA and the FAA are also trying to use DRM to enforce the laws and regulations they are tasked with upholding.



The cause the FDA and FAA have chosen to champion is the ability to force users to buy particular feedstock for 3D printers. These printers take simple materials and transform them into virtually anything a user can imagine, but you still need that base material (known as feedstock) in order to print anything. Companies want to use DRM on their 3D printers so they can lock users into only using their feedstock, believing that they thereby will reap a large financial benefit. The FDA apparently worries about users using non-approved feedstock to create 3D-printed medical devices. The FAA has the same concern for aviation parts.



Do any of these purposes have anything to do with copyright? No, none whatsoever, except for the fact that the DMCA exists. Because the DMCA's anti-circumvention provisions prop up the use of DRM, these companies and agencies want to use it for all their non-copyright related purposes. DRM is a tool of control, and instead of just doing their job, the FDA and the FAA want copyright law to do it for them.



Their laziness is harmful to users, as the current exemption for 3D printers has a qualification that it does not apply to any software or device "which is subject to legal or regulatory oversight or a related certification process."



A lawyer for Shapeways Inc. submitted the new exemption, pointing out that as currently written, it renders the exemption as a whole useless, as virtually any use could be subject to some other non-copyright regulation. The Free Software Foundation (FSF) submitted the sole comment in support of the updated exemption. We are fighting to end DRM and the DMCA anti-circumvention exemptions process, but until we achieve that goal, we support every single exemption that is proposed. The FDA and FAA should join us in this goal, stop trying to use the DMCA for their own purposes, and start supporting the rights of
users.



Next up is the National Association of Secretaries of State (NASS), representing 40 different US state governments. NASS are apparently unfamiliar with the fact that security through obscurity is a recipe for disaster. They've submitted opposition comments trying to stop an exemption for security researchers. Being able to circumvent DRM's obstruction in order to test the security of a device or piece of software is one of the most important reasons why DRM is so damaging. How can anyone trust a device or piece of software if they can't pull it apart and study its
internals?



NASS thinks that letting security researchers test the security of voting machines would somehow make those machines less secure. But as everyone else knows by now, you can't make a system secure by pretending it can never be cracked. The only way to verify its security is to test it, and to have lots of people test it. As in the case of the FDA and the FAA, there are other legal tools already available for punishing anyone who tries to damage or interfere with elections. So why try to rope copyright law into this entirely unrelated matter? Again, the only reason these government officials are getting involved is because they want the control that DRM provides, a level of control they have no ethical right to exert.



During the last exemption round, we were afraid that the EPA meddling in the DMCA anti-circumvention process was only the beginning. We worried that more and more, the government would seek to turn the DMCA anti-circumvention penalties and the DRM controls it supports into a further tool of oppression. This latest round of exemptions does nothing to dispel that fear. It's getting worse and worse. If we don't act now, government will begin to use DRM to control every aspect of our lives. If you thought having corporations controlling the keys to your digital life was a nightmare, it is about to get infinitely worse.



The time to fight back is now. Here is what you need to do:



If you microblog, please share the following messages (or your own) with the hashtag #DRMshame:



-at-US_FDA You should be ashamed of yourself for trying to use Digital Restrictions Management to do your job #DRMshame https://u.fsf.org/2k1



-at-FAANEWS You should be ashamed of yourself for trying to use Digital Restrictions Management to do your job #DRMshame https://u.fsf.org/2k1



-at-NASSorg Security through obscurity does not work, say no to Digital Restrictions Management #DRMshame https://u.fsf.org/2k1



We strongly suggest that if you use Twitter, you do it in a way that avoids using proprietary software.



Here's what else you can do:





Sincerely,



Donald Robertson, III

Licensing & Compliance Manager







--=_b7ba445a6ab2d6ba73689644f71c8d05--

--===============0575501776==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout

--===============0575501776==--

--===============0575501776==
Content-Type: multipart/alternative;
boundary="=_b7ba445a6ab2d6ba73689644f71c8d05"

--=_b7ba445a6ab2d6ba73689644f71c8d05
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=utf-8

*Read online and share: https://www.defectivebydesign.org/blog/meet_latest_drm_drones*


Dear Ruben Safir,

The latest round of opposition comments in the Digital Millennium
Copyright Act's (DMCA) exemption process shows which government
entities oppose user freedom.

Back during the last round of the DMCA anti-circumvention exemptions
process, we wrote about the [DRM Drones who were opposing
exemptions][0]. These companies, along with the [US Environmental
Protection Agency][1] (EPA), were trying to stifle the work of
activists working to claw back a bit of freedom in the face of the
DMCA's draconian provisions. A few years later, and it's a new round
of the exemptions process, with perhaps some new faces, but the same
old problem.

[0]: https://www.defectivebydesign.org/meet-the-drm-drones
[1]: https://www.defectivebydesign.org/epa-drm-drone

As we've often said, Digital Restrictions Management (DRM) is not
about copyright, it's about control. And these opposition comments
truly demonstrate that that is the case. The DMCA is allegedly meant
to aid in copyright enforcement, but goes about its task in the worst
way possible, creating legal penalties for circumventing DRM. By
itself, DRM is harmful to users, who all have the right to control
their own computing. Adding legal penalties only compounds the harm of
DRM. Even if DRM were an effective tool for enforcing copyright (and
if copyright were not already extremely excessive), it is unethical to
place such onerous control over users.

So what does the US Food and Drug Administration (FDA), or the US
Federal Aviation Administration (FAA) for that matter, care about
enforcing copyright? The reality is that they don't, but they realize
the nefarious power of DRM to lock down and control users for any
purpose, using copyright as an excuse. Like the EPA, the FDA and the
FAA are also trying to use DRM to enforce the laws and regulations
they are tasked with upholding.

The cause [the FDA and FAA][2] have chosen to champion is the ability
to force users to buy particular feedstock for 3D printers. These
printers take simple materials and transform them into virtually
anything a user can imagine, but you still need that base material
(known as feedstock) in order to print anything. Companies want to use
DRM on their 3D printers so they can lock users into only using their
feedstock, believing that they thereby will reap a large financial
benefit. The FDA apparently worries about users using non-approved
feedstock to create 3D-printed medical devices. The FAA has the same
concern for aviation parts.

[2]:http://advancedmanufacturing.org/controls-feedstock-used-3d-printers/

Do any of these purposes have anything to do with copyright? No, none
whatsoever, except for the fact that the DMCA exists. Because the
DMCA's anti-circumvention provisions prop up the use of DRM, these
companies and agencies want to use it for all their non-copyright
related purposes. DRM is a tool of control, and instead of just doing
their job, the FDA and the FAA want copyright law to do it for them.

Their laziness is harmful to users, as the current exemption for 3D
printers has a qualification that it does not apply to any software or
device "which is subject to legal or regulatory oversight or a related
certification process."

A lawyer for Shapeways Inc. submitted the new exemption, pointing out
that as currently written, it renders the exemption as a whole
useless, as virtually any use could be subject to some other
non-copyright regulation. The Free Software Foundation (FSF) submitted
the sole comment in support of the updated exemption. We are fighting
to end DRM and the DMCA anti-circumvention exemptions process, but
until we achieve that goal, [we support every single exemption][3] that is
proposed. The FDA and FAA should join us in this goal, stop trying to
use the DMCA for their own purposes, and start supporting the rights
of users.

[3]: https://www.defectivebydesign.org/blog/help_fight_against_dmca_anticircumvention_rules_december_15th

Next up is the [National Association of Secretaries of State][4]
(NASS), representing 40 different US state governments. NASS are
apparently unfamiliar with the fact that security through obscurity is
a recipe for disaster. They've submitted opposition comments trying to
stop an exemption for security researchers. Being able to circumvent
DRM's obstruction in order to test the security of a device or piece
of software is one of the most important reasons why DRM is so
damaging. How can anyone trust a device or piece of software if they
can't pull it apart and study its internals?

[4]: https://www.copyright.gov/1201/2018/comments-021218/class10/Class_10_Opp'n_National_Association_of_Secretaries_of%20State.pdf

NASS thinks that letting security researchers test the security of
voting machines would somehow make those machines less secure. But as
everyone else knows by now, you can't make a system secure by
pretending it can never be cracked. The only way to verify its
security is to test it, and to have lots of people test it. As in the
case of the FDA and the FAA, there are other legal tools already
available for punishing anyone who tries to damage or interfere with
elections. So why try to rope copyright law into this entirely
unrelated matter? Again, the only reason these government officials
are getting involved is because they want the control that DRM
provides, a level of control they have no ethical right to exert.

During the last exemption round, we were afraid that the EPA meddling
in the DMCA anti-circumvention process was only the beginning. We
worried that more and more, the government would seek to turn the DMCA
anti-circumvention penalties and the DRM controls it supports into a
further tool of oppression. This latest round of exemptions does
nothing to dispel that fear. It's getting worse and worse. If we don't
act now, government will begin to use DRM to control every aspect of
our lives. If you thought having corporations controlling the keys to
your digital life was a nightmare, it is about to get infinitely
worse.

The time to fight back is now. Here is what you need to do:

If you microblog, please share the following messages (or your own)
with the hashtag #DRMshame:

*-at-US_FDA You should be ashamed of yourself for trying to use Digital
Restrictions Management to do your job #DRMshame
*

*-at-FAANEWS You should be ashamed of yourself for trying to use Digital
Restrictions Management to do your job #DRMshame
*

*-at-NASSorg Security through obscurity does not work, say no to Digital
Restrictions Management #DRMshame *

We strongly suggest that if you use [Twitter][5], you do it in a way
that avoids using proprietary software.

[5]: https://www.fsf.org/twitter

Here's what else you can do:

* Sign up for the FSF's monthly newsletter, [the *Free Software
Supporter*][6], to keep up to date on all the latest news in free
software.

* To help fund our work, consider [donating][7] to the Free Software
Foundation, or becoming an [Associate Member][8].

[6]: https://www.fsf.org/free-software-supporter/
[7]: https://donate.fsf.org
[8]: https://www.fsf.org/join

Sincerely,

Donald Robertson, III
Licensing & Compliance Manager
--
* Follow us at .
* Subscribe to our blog via RSS at .
* Donate to support the campaign at .

You can unsubscribe from the Defective by Design mailing list by visiting the link .

To stop all email from the Free Software Foundation, including
Defective by Design and the Free Software Supporter newsletter, click
this link: .

Defective by Design is a campaign of the Free Software Foundation:

51 Franklin St, Fifth Floor
Boston, Massachusetts 02110-1335
United States

--=_b7ba445a6ab2d6ba73689644f71c8d05
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8








































Read online and share: https://www.defectivebydesign.org/blog/meet_latest_drm_drones





Dear Ruben Safir,



The latest round of opposition comments in the Digital Millennium Copyright Act's (DMCA) exemption process shows which government entities oppose user freedom.



Back during the last round of the DMCA anti-circumvention exemptions process, we wrote about the DRM Drones who were opposing exemptions. These companies, along with the US Environmental Protection Agency (EPA), were trying to stifle the work of activists working to claw back a bit of freedom in the face of the DMCA's draconian provisions. A few years later, and it's a new round of the exemptions process, with perhaps some new faces, but the same old problem.



As we've often said, Digital Restrictions Management (DRM) is not about copyright, it's about control. And these opposition comments truly demonstrate that that is the case. The DMCA is allegedly meant to aid in copyright enforcement, but goes about its task in the worst way possible, creating legal penalties for circumventing DRM. By itself, DRM is harmful to users, who all have the right to control their own computing. Adding legal penalties only compounds the harm of DRM. Even if DRM were an effective tool for enforcing copyright (and if copyright were not already extremely excessive), it is unethical to place such onerous control over users.



So what does the US Food and Drug Administration (FDA), or the US Federal Aviation Administration (FAA) for that matter, care about enforcing copyright? The reality is that they don't, but they realize the nefarious power of DRM to lock down and control users for any purpose, using copyright as an excuse. Like the EPA, the FDA and the FAA are also trying to use DRM to enforce the laws and regulations they are tasked with upholding.



The cause the FDA and FAA have chosen to champion is the ability to force users to buy particular feedstock for 3D printers. These printers take simple materials and transform them into virtually anything a user can imagine, but you still need that base material (known as feedstock) in order to print anything. Companies want to use DRM on their 3D printers so they can lock users into only using their feedstock, believing that they thereby will reap a large financial benefit. The FDA apparently worries about users using non-approved feedstock to create 3D-printed medical devices. The FAA has the same concern for aviation parts.



Do any of these purposes have anything to do with copyright? No, none whatsoever, except for the fact that the DMCA exists. Because the DMCA's anti-circumvention provisions prop up the use of DRM, these companies and agencies want to use it for all their non-copyright related purposes. DRM is a tool of control, and instead of just doing their job, the FDA and the FAA want copyright law to do it for them.



Their laziness is harmful to users, as the current exemption for 3D printers has a qualification that it does not apply to any software or device "which is subject to legal or regulatory oversight or a related certification process."



A lawyer for Shapeways Inc. submitted the new exemption, pointing out that as currently written, it renders the exemption as a whole useless, as virtually any use could be subject to some other non-copyright regulation. The Free Software Foundation (FSF) submitted the sole comment in support of the updated exemption. We are fighting to end DRM and the DMCA anti-circumvention exemptions process, but until we achieve that goal, we support every single exemption that is proposed. The FDA and FAA should join us in this goal, stop trying to use the DMCA for their own purposes, and start supporting the rights of
users.



Next up is the National Association of Secretaries of State (NASS), representing 40 different US state governments. NASS are apparently unfamiliar with the fact that security through obscurity is a recipe for disaster. They've submitted opposition comments trying to stop an exemption for security researchers. Being able to circumvent DRM's obstruction in order to test the security of a device or piece of software is one of the most important reasons why DRM is so damaging. How can anyone trust a device or piece of software if they can't pull it apart and study its
internals?



NASS thinks that letting security researchers test the security of voting machines would somehow make those machines less secure. But as everyone else knows by now, you can't make a system secure by pretending it can never be cracked. The only way to verify its security is to test it, and to have lots of people test it. As in the case of the FDA and the FAA, there are other legal tools already available for punishing anyone who tries to damage or interfere with elections. So why try to rope copyright law into this entirely unrelated matter? Again, the only reason these government officials are getting involved is because they want the control that DRM provides, a level of control they have no ethical right to exert.



During the last exemption round, we were afraid that the EPA meddling in the DMCA anti-circumvention process was only the beginning. We worried that more and more, the government would seek to turn the DMCA anti-circumvention penalties and the DRM controls it supports into a further tool of oppression. This latest round of exemptions does nothing to dispel that fear. It's getting worse and worse. If we don't act now, government will begin to use DRM to control every aspect of our lives. If you thought having corporations controlling the keys to your digital life was a nightmare, it is about to get infinitely worse.



The time to fight back is now. Here is what you need to do:



If you microblog, please share the following messages (or your own) with the hashtag #DRMshame:



-at-US_FDA You should be ashamed of yourself for trying to use Digital Restrictions Management to do your job #DRMshame https://u.fsf.org/2k1



-at-FAANEWS You should be ashamed of yourself for trying to use Digital Restrictions Management to do your job #DRMshame https://u.fsf.org/2k1



-at-NASSorg Security through obscurity does not work, say no to Digital Restrictions Management #DRMshame https://u.fsf.org/2k1



We strongly suggest that if you use Twitter, you do it in a way that avoids using proprietary software.



Here's what else you can do:





Sincerely,



Donald Robertson, III

Licensing & Compliance Manager







--=_b7ba445a6ab2d6ba73689644f71c8d05--

--===============0575501776==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout

--===============0575501776==--

  1. 2018-04-02 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] Free Software Supporter Issue 120, April 2018
  2. 2018-04-02 From: "New York City Council" <Correspondence-at-council.nyc.ny.us> Subject: [Hangout - NYLXS] Take Part in this Year's Participatory Budgeting
  3. 2018-04-02 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #349 - Conference season is upon us!
  4. 2018-04-04 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Facebook leveraging MLB for more tracking power
  5. 2018-04-04 From: "[RSS/Feed] nixCraft: Linux Tips, Hacks, Tutorials, Subject: [Hangout - NYLXS] nixCraft Linux / UNIX Newsletter
  6. 2018-04-04 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Home Sweat home
  7. 2018-04-05 ISOC-NY announcements <announce-at-lists.isoc-ny.org> Subject: [Hangout - NYLXS] [isoc-ny] VIDEO: Facebook After Cambridge
  8. 2018-04-09 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #350 - eBook: Programming the
  9. 2018-04-10 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] anyone now interested in a hacking meeting
  10. 2018-04-10 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Lets Go Mets
  11. 2018-04-12 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] SBS 82 Bus Proposal is a non-starter
  12. 2018-04-12 From: "IEEE Spectrum Tech Alert" <reply-at-media.ieee.org> Subject: [Hangout - NYLXS] Military Ray Guns, Self-Powered Image Sensors,
  13. 2018-04-12 From: "Office of Admissions, Graduate Center CUNY" <admissions-at-gc.cuny.edu> Subject: [Hangout - NYLXS] Upcoming CUNY Ph.D. Program in Mathematics
  14. 2018-04-13 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] Citywide Business Pitch Contest This Sunday,
  15. 2018-04-13 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] your world just got a little bit smaller
  16. 2018-04-17 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Tandem Buses coming to Kings Highway with Bus
  17. 2018-04-18 From: "Donald Robertson, III, DBD" <info-at-defectivebydesign.org> Subject: [Hangout - NYLXS] Meet the latest DRM Drones
  18. 2018-04-19 Rick Moen <rick-at-linuxmafia.com> Subject: [Hangout - NYLXS] (forw) How Bees Revealed a Pot Farm Beneath the
  19. 2018-04-16 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #351 - What would you like to read
  20. 2018-04-19 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] I always wondered what the damn spleen was for
  21. 2018-04-23 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Keep the trains moveing
  22. 2018-04-24 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Fwd: Last chance! Subscribe now and save! $10 off
  23. 2018-04-25 From: "[RSS/Feed] nixCraft: Linux Tips, Hacks, Tutorials, Subject: [Hangout - NYLXS] nixCraft Linux / UNIX Newsletter
  24. 2018-04-27 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Piaco - not my favorite - but nice treatment by NG
  25. 2018-04-27 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Must See NYC Photographic Narative
  26. 2018-04-26 From: "Canarsie Courier" <emailsentby-at-icontactmail.com> Subject: [Hangout - NYLXS] Inside This Week's Edition of the Canarsie Courier
  27. 2018-04-23 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #352 - It's alive!
  28. 2018-04-29 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] One of the most interesting brooklyn historical
  29. 2018-04-29 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #353 - Working together at the PTS
  30. 2018-04-29 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #353 - Working together at the PTS
  31. 2018-04-27 From: "American Museum of Natural History" <email-at-amnh.org> Subject: [Hangout - NYLXS] Gilder Center Project Updates
  32. 2018-04-27 From: "Deep Medhi, IEEE ICC 2018 Executive Chair" <noreply-at-comsoc.org> Subject: [Hangout - NYLXS] IEEE ICC'18 Learn About Our Keynote Speakers

NYLXS are Do'ers and the first step of Doing is Joining! Join NYLXS and make a difference in your community today!