CVSROOT: /cvsroot/www-bg
Module name: www-bg
Changes by: Ivaylo Kabakov <se7en> 07/01/31 20:18:42
Added files:
philosophy : can-you-trust.html
Log message:
Ðов пÑевод, за ÑеÑÑване.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/www-bg/philosophy/can-you-trust.html?cvsroot=www-bg&rev=1.1
Patches:
Index: can-you-trust.html
===================================================================
RCS file: can-you-trust.html
diff -N can-you-trust.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ can-you-trust.html 31 Jan 2007 20:18:42 -0000 1.1
@@ -0,0 +1,321 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
+
+<head>
+<title>Can you trust your computer? - GNU Project - Free Software Foundation
(FSF)</title>
+<meta http-equiv="content-type" content='text/html; charset=utf-8' />
+<link rel="stylesheet" type="text/css" href="/gnu.css" />
+<link rev="made" href="mailto:[EMAIL PROTECTED]" />
+</head>
+
+<!-- This document is in XML, and xhtml 1.0 -->
+<!-- Please make sure to properly nest your tags -->
+<!-- and ensure that your final document validates -->
+<!-- consistent with W3C xhtml 1.0 and CSS standards -->
+<!-- See validator.w3.org -->
+
+<body>
+
+<p><a href="#translations">Translations</a> of this page</p>
+
+<h3>Can you trust your computer?</h3>
+
+<p>
+by <a href="http://www.stallman.org/";><strong>Richard Stallman</strong></a></p>
+
+<p>
+<a href="/graphics/philosophicalgnu.html"><img
src="/graphics/philosophical-gnu-sm.jpg"
+ alt=" [image of a Philosophical Gnu] "
+ width="160" height="200" /></a>
+</p>
+
+<p>
+Who should your computer take its orders from? Most people think
+their computers should obey them, not obey someone else. With a plan
+they call "trusted computing", large media corporations (including the
+movie companies and record companies), together with computer
+companies such as Microsoft and Intel, are planning to make your
+computer obey them instead of you. (Microsoft's version of this
+scheme is called "Palladium".) Proprietary programs have included
+malicious features before, but this plan would make it universal.</p>
+<p>
+Proprietary software means, fundamentally, that you don't control what
+it does; you can't study the source code, or change it. It's not
+surprising that clever businessmen find ways to use their control to
+put you at a disadvantage. Microsoft has done this several times: one
+version of Windows was designed to report to Microsoft all the
+software on your hard disk; a recent "security" upgrade in Windows
+Media Player required users to agree to new restrictions. But
+Microsoft is not alone: the KaZaa music-sharing software is designed
+so that KaZaa's business partner can rent out the use of your computer
+to their clients. These malicious features are often secret, but even
+once you know about them it is hard to remove them, since you don't
+have the source code.</p>
+<p>
+In the past, these were isolated incidents. "Trusted computing" would
+make it pervasive. "Treacherous computing" is a more appropriate
+name, because the plan is designed to make sure your computer will
+systematically disobey you. In fact, it is designed to stop your
+computer from functioning as a general-purpose computer. Every
+operation may require explicit permission.</p>
+<p>
+The technical idea underlying treacherous computing is that the
+computer includes a digital encryption and signature device, and the
+keys are kept secret from you. Proprietary programs will use this
+device to control which other programs you can run, which documents or
+data you can access, and what programs you can pass them to. These
+programs will continually download new authorization rules through the
+Internet, and impose those rules automatically on your work. If you
+don't allow your computer to obtain the new rules periodically from
+the Internet, some capabilities will automatically cease to function.</p>
+<p>
+Of course, Hollywood and the record companies plan to use treacherous
+computing for "DRM" (Digital Restrictions Management), so that
+downloaded videos and music can be played only on one specified
+computer. Sharing will be entirely impossible, at least using the
+authorized files that you would get from those companies. You, the
+public, ought to have both the freedom and the ability to share these
+things. (I expect that someone will find a way to produce unencrypted
+versions, and to upload and share them, so DRM will not entirely
+succeed, but that is no excuse for the system.)</p>
+<p>
+Making sharing impossible is bad enough, but it gets worse. There are
+plans to use the same facility for email and documents--resulting in
+email that disappears in two weeks, or documents that can only be read
+on the computers in one company.</p>
+<p>
+Imagine if you get an email from your boss telling you to do something
+that you think is risky; a month later, when it backfires, you can't
+use the email to show that the decision was not yours. "Getting it in
+writing" doesn't protect you when the order is written in disappearing
+ink.</p>
+<p>
+Imagine if you get an email from your boss stating a policy that is
+illegal or morally outrageous, such as to shred your company's audit
+documents, or to allow a dangerous threat to your country to move
+forward unchecked. Today you can send this to a reporter and expose
+the activity. With treacherous computing, the reporter won't be able
+to read the document; her computer will refuse to obey her.
+Treacherous computing becomes a paradise for corruption.</p>
+<p>
+Word processors such as Microsoft Word could use treacherous computing
+when they save your documents, to make sure no competing word
+processors can read them. Today we must figure out the secrets of
+Word format by laborious experiments in order to make free word
+processors read Word documents. If Word encrypts documents using
+treacherous computing when saving them, the free software community
+won't have a chance of developing software to read them--and if we
+could, such programs might even be forbidden by the Digital Millennium
+Copyright Act.</p>
+<p>
+Programs that use treacherous computing will continually download new
+authorization rules through the Internet, and impose those rules
+automatically on your work. If Microsoft, or the US government, does
+not like what you said in a document you wrote, they could post new
+instructions telling all computers to refuse to let anyone read that
+document. Each computer would obey when it downloads the new
+instructions. Your writing would be subject to 1984-style retroactive
+erasure. You might be unable to read it yourself.</p>
+<p>
+You might think you can find out what nasty things a treacherous
+computing application does, study how painful they are, and decide
+whether to accept them. It would be short-sighted and foolish to
+accept, but the point is that the deal you think you are making won't
+stand still. Once you come to depend on using the program, you are
+hooked and they know it; then they can change the deal. Some
+applications will automatically download upgrades that will do
+something different--and they won't give you a choice about whether to
+upgrade.</p>
+<p>
+Today you can avoid being restricted by proprietary software by not
+using it. If you run GNU/Linux or another free operating system, and
+if you avoid installing proprietary applications on it, then you are
+in charge of what your computer does. If a free program has a
+malicious feature, other developers in the community will take it out,
+and you can use the corrected version. You can also run free
+application programs and tools on non-free operating systems; this
+falls short of fully giving you freedom, but many users do it.</p>
+<p>
+Treacherous computing puts the existence of free operating systems and
+free applications at risk, because you may not be able to run them at
+all. Some versions of treacherous computing would require the
+operating system to be specifically authorized by a particular
+company. Free operating systems could not be installed. Some
+versions of treacherous computing would require every program to be
+specifically authorized by the operating system developer. You could
+not run free applications on such a system. If you did figure out
+how, and told someone, that could be a crime.</p>
+<p>
+There are proposals already for US laws that would require all computers to
+support treacherous computing, and to prohibit connecting old computers to
+the Internet. The CBDTPA (we call it the Consume But Don't Try Programming
+Act) is one of them. But even if they don't legally force you to switch to
+treacherous computing, the pressure to accept it may be enormous. Today
+people often use Word format for communication, although this causes
+several sorts of problems (see
+<a href="/philosophy/no-word-attachments.html">"We Can Put an End to Word
+Attachments"</a>). If only a treacherous computing machine can read the
+latest Word documents, many people will switch to it, if they view the
+situation only in terms of individual action (take it or leave it). To
+oppose treacherous computing, we must join together and confront the
+situation as a collective choice.</p>
+<p>
+For further information about treacherous computing, see
+<a
href="http://www.cl.cam.ac.uk/users/rja14/tcpa-faq.html";><http://www.cl.cam.ac.uk/users/rja14/tcpa-faq.html></a>.</p>
+<p>
+To block treacherous computing will require large numbers of citizens to
+organize. We need your help! The <a href="http://www.eff.org";>Electronic
+Frontier Foundation</a> and <a href="http://www.publicknowledge.org";>Public
+Knowledge</a> are campaigning against treacherous computing, and so is the
+FSF-sponsored Digital Speech Project. Please visit these Web sites so
+you can sign up to support their work.</p>
+<p>
+You can also help by writing to the public affairs offices of Intel,
+IBM, HP/Compaq, or anyone you have bought a computer from, explaining
+that you don't want to be pressured to buy "trusted" computing systems
+so you don't want them to produce any. This can bring consumer power
+to bear. If you do this on your own, please send copies of your
+letters to the organizations above.</p>
+
+<h3>Postscripts</h3>
+
+<ol>
+<li>The GNU Project distributes the GNU Privacy Guard, a program that
+implements public-key encryption and digital signatures, which you can
+use to send secure and private email. It is useful to explore how GPG
+differs from treacherous computing, and see what makes one helpful and
+the other so dangerous.
+<p>
+When someone uses GPG to send you an encrypted document, and you use
+GPG to decode it, the result is an unencrypted document that you can
+read, forward, copy, and even re-encrypt to send it securely to
+someone else. A treacherous computing application would let you read
+the words on the screen, but would not let you produce an unencrypted
+document that you could use in other ways. GPG, a free software
+package, makes security features available to the users; they use it.
+Treacherous computing is designed to impose restrictions on the users;
+it uses them.</p></li>
+
+<li>Microsoft presents palladium as a security measure, and claims that
+it will protect against viruses, but this claim is evidently false. A
+presentation by Microsoft Research in October 2002 stated that one of
+the specifications of palladium is that existing operating systems and
+applications will continue to run; therefore, viruses will continue to
+be able to do all the things that they can do today.
+<p>
+When Microsoft speaks of "security" in connection with palladium, they
+do not mean what we normally mean by that word: protecting your
+machine from things you do not want. They mean protecting your copies
+of data on your machine from access by you in ways others do not want.
+A slide in the presentation listed several types of secrets palladium
+could be used to keep, including "third party secrets" and "user
+secrets"--but it put "user secrets" in quotation marks, recognizing
+that this somewhat of an absurdity in the context of palladium.</p>
+<p>
+The presentation made frequent use of other terms that we frequently
+associate with the context of security, such as "attack", "malicious
+code", "spoofing", as well as "trusted". None of them means what it
+normally means. "Attack" doesn't mean someone trying to hurt you, it
+means you trying to copy music. "Malicious code" means code installed
+by you to do what someone else doesn't want your machine to do.
+"Spoofing" doesn't mean someone fooling you, it means you fooling
+palladium. And so on.</p></li>
+
+<li>A previous statement by the palladium developers stated the basic
+premise that whoever developed or collected information should have
+total control of how you use it. This would represent a revolutionary
+overturn of past ideas of ethics and of the legal system, and create
+an unprecedented system of control. The specific problems of these
+systems are no accident; they result from the basic goal. It is the
+goal we must reject.</li>
+</ol>
+
+
+<hr />
+<h4>This essay is published in <a href="/doc/book13.html"><cite>Free Software,
+Free Society: The Selected Essays of Richard M. Stallman</cite></a></h4>
+
+<h4><a href="/philosophy/philosophy.html">Other Texts to Read</a></h4>
+<hr />
+
+<!-- All pages on the GNU web server should have the section about -->
+<!-- verbatim copying. Please do NOT remove this without talking -->
+<!-- with the webmasters first. -->
+<!-- Please make sure the copyright date is consistent with the document -->
+<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
+
+<div class="translations">
+<p><a id="translations"></a>
+<b>Translations of this page</b>:<br />
+
+<!-- Please keep this list alphabetical, and in the original -->
+<!-- language if possible, otherwise default to English -->
+<!-- If you do not have it English, please comment what the -->
+<!-- English is. If you add a new language here, please -->
+<!-- advise [EMAIL PROTECTED] and add it to -->
+<!-- - in /home/www/bin/nightly-vars either TAGSLANG or WEBLANG -->
+<!-- - in /home/www/html/server/standards/README.translations.html -->
+<!-- one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the 2 letter language code right versus -->
+<!-- http://www.w3.org/WAI/ER/IG/ert/iso639.htm -->
+
+[
+ <a
href="/philosophy/can-you-trust.bg.html">български</a>
<!-- Bulgarian -->
+| <a
href="/philosophy/can-you-trust.cn.html">简体中文</a>
<!-- Chinese(Simplified) -->
+| <a
href="/philosophy/can-you-trust.zh.html">繁體中文</a>
<!-- Chinese(Traditional) -->
+| <a href="/philosophy/can-you-trust.de.html">Deutsch</a> <!-- German -->
+| <a href="/philosophy/can-you-trust.html">English</a>
+| <a href="/philosophy/can-you-trust.es.html">Español</a> <!--
Spanish -->
+| <a href="/philosophy/can-you-trust.fr.html">Français</a> <!--
French -->
+| <a href="/philosophy/can-you-trust.it.html">Italiano</a> <!-- Italian -->
+| <a href="/philosophy/can-you-trust.ko.html">한국어</a>
<!-- Korean -->
+| <a href="/philosophy/can-you-trust.pl.html">Polski</a> <!-- Polish -->
+| <a href="/philosophy/can-you-trust.tr.html">Türkçe</a> <!--
Turkish -->
+]
+</p>
+</div>
+
+<div class="copyright">
+<p>
+Return to the <a href="/home.html">GNU Project home page</a>.
+</p>
+
+<p>
+Please send FSF & GNU inquiries to
+<a href="mailto:[EMAIL PROTECTED]"><em>[EMAIL PROTECTED]</em></a>.
+There are also <a href="/home.html#ContactInfo">other ways to contact</a>
+the FSF.
+<br />schools
+Please send broken links and other corrections (or suggestions) to
+<a href="mailto:[EMAIL PROTECTED]"><em>[EMAIL PROTECTED]</em></a>.
+</p>
+
+<p>
+Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.
+</p>
+
+<p>
+Copyright © 2002 Richard Stallman.
+<br />
+Verbatim copying and distribution of this entire article is
+permitted in any medium without royalty provided this notice is
+preserved.
+</p>
+
+<p>
+Updated:
+<!-- timestamp start -->
+$Date: 2007/01/31 20:18:42 $ $Author: se7en $
+<!-- timestamp end -->
+</p>
+</div>
+
+</body>
+</html>
_______________________________________________
Dict-notifications mailing list
[email protected]
http://zver.fsa-bg.org/cgi-bin/mailman/listinfo/dict-notifications
