www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/server/staging on-privacy-at-school.html


From: Dora Scilipoti
Subject: www/server/staging on-privacy-at-school.html
Date: Sun, 27 Nov 2022 04:50:36 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     Dora Scilipoti <dora>   22/11/27 04:50:36

Added files:
        server/staging : on-privacy-at-school.html 

Log message:
        RMS's new article draft.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/staging/on-privacy-at-school.html?cvsroot=www&rev=1.1

Patches:
Index: on-privacy-at-school.html
===================================================================
RCS file: on-privacy-at-school.html
diff -N on-privacy-at-school.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ on-privacy-at-school.html   27 Nov 2022 09:50:36 -0000      1.1
@@ -0,0 +1,183 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.97 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
+
+<title>On Privacy at School
+- GNU Project - Free Software Foundation</title>
+
+<link rel="stylesheet" type="text/css" href="/side-menu.css" media="screen" />
+<!--#include virtual="/server/gnun/initial-translations-list.html" -->
+<!--#include virtual="/server/banner.html" -->
+
+<div class="nav">
+<a id="side-menu-button" class="switch" href="#navlinks">
+ <img id="side-menu-icon" height="32"
+      src="/graphics/icons/side-menu.png"
+      title="Education Contents"
+      alt="&nbsp;[Education Contents]&nbsp;" />
+</a>
+
+<p class="breadcrumb">
+ <a href="/"><img src="/graphics/icons/home.png" height="24"
+    alt="GNU Home" title="GNU Home" /></a>&nbsp;/
+ <a href="/education/education.html">Education</a>&nbsp;/
+ <a 
href="/education/bigtech-threats-to-education-and-society.html">Big&nbsp;Tech&nbsp;Threats</a>&nbsp;/</p>
+</div>
+
+<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#include virtual="/server/top-addendum.html" -->
+
+<div style="clear: both"></div>
+<div id="last-div" class="reduced-width">
+
+<div class="announcement comment" role="complementary">
+<p>
+Examples of 
+<a href="/proprietary/malware-edtech.html#content">malware in
+educational proprietary technologies</a>.
+</p>
+</div>
+
+<h2>On Privacy at School</h2>
+
+<address class="byline">by Richard Stallman</address>
+<hr class="thin" />
+<div class="article">
+
+<p>Wired published an article of advice for students about <a 
+href="https://www.wired.com/story/how-to-protect-yourself-school-surveillance-tech-privacy/";>
+how to resist surveillance by their schools</a>.</p>
+
+<p>The advice it gives is valid as far as it goes, but it falls far
+short of what students need to know to resist all the threats.</p>
+
+<p>The article poses the question:</p>
+
+<blockquote>
+<p>How is student data secured?</p>
+<blockquote>
+
+<p>This question invites confusion. If someone claims to keep data about 
+you &ldquo;secure,&rdquo; what does that mean? Secure <em>from whom</em>? 
+The school's computers are unlikely to keep anyone secure from <a 
+href="/education/governments-let-companies-snoop-on-students.html">
+snooping EdTech companies</a> that operate with the school's cooperation.</p>
+
+<p>&ldquo;Using your own personal device&rdquo; usually means using a <a 
+href="/proprietary/malware-mobiles.html">snoop-phone</a>. It may protect 
+you from snooping by the school and by <a 
+href="/proprietary/malware-edtech.html">EdTech companies</a>, provided 
+you never use it to visit a site that has anything to do with the school 
+or an EdTech company and never do unencrypted 
+communication&#8239;<a href="#Note1" id="Note1-rev">[1]</a>.
+But the device was made by a computer company&mdash;usually <a 
+href="/proprietary/malware-apple.html">Apple</a> or <a 
+href="/proprietary/malware-google.html">Google</a>&mdash;that also made 
+the operating system in it. That system always contains nonfree  software that 
+snoops on you plenty. Most <a 
+href="/proprietary/proprietary-surveillance.html#SpywareInApplications">
+apps</a> for that snoop phone are nonfree, and they snoop for various 
companies, often behind the back of the 
+organization that commissioned development of the app itself. Encryption 
+features or apps, if they are part of that nonfree operating system or 
+nonfree, are likely to snoop on users too.</p>
+
+<p>The only way to protect yourself against this is to <a 
+href="/education/bigtech-threats-to-education-and-society.html">reject 
+nonfree programs</a> (programs that are not free/libre) in your device. 
+(Alas, iPhones entirely prohibit free software.) And even then, the 
+hardware may have a back door, such as Microsoft's Pluton chip or the 
+<a href="/proprietary/proprietary-insecurity.html#M201706050">Intel 
+Management Engine</a>.</p>
+
+<p>Connecting a phone or computer to USB, even &ldquo;for charging,&rdquo; 
+makes it vulnerable. Some <a 
+href="https://www.wallofsheep.com/pages/juice";>security conferences</a>, 
+with the purpose of educating the public about security issues, have 
+installed a place full of USB sockets which were set up also to snoop on 
+any computer (including a snoop-phone) plugged in there. The participants 
+saw a USB jack and thought, &ldquo;This is where we should charge our 
+devices,&rdquo; and assumed it was safe to use. When the conference 
+organizers revealed the snooping, they taught these users a lesson about 
+security.</p>
+
+<p>Privacy is not only for children and teenagers. We need to demand
+privacy for adults, too. This means that schools, stores, clinics,
+transportation companies, and other organizations people deal with
+must not demand you tell them who you are, and must not try to find
+out.</p>
+
+<p><a href="#Note1-rev" id="Note1">[1]</a>To be secure for you, 
+encryption has to be done with a free program that you have installed 
+into your computer. If a <a 
+href="/proprietary/proprietary-insecurity.html#M201309054">nonfree
+program running in your computer does the encryption</a>, including <a 
+href="/philosophy/javascript-trap.html">JavaScript</a> sent to the
+browser by an online &ldquo;service,&rdquo; or if it is done in the <a 
+href="/philosophy/who-does-that-server-really-serve.html">online
+&ldquo;service&rdquo; server</a> itself, it is not secure.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer" role="contentinfo">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:gnu@gnu.org";>&lt;gnu@gnu.org&gt;</a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:webmasters@gnu.org";>&lt;webmasters@gnu.org&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:web-translators@gnu.org";>
+        &lt;web-translators@gnu.org&gt;</a>.</p>
+
+        <p>For information on coordinating and contributing translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and contributing translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2022 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2022/11/27 09:50:36 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]