From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: CVE-2017-14482 - Red Hat Customer Portal Date: Tue, 26 Sep 2017 00:02:44 +0200 Message-ID: <86efqu308r.fsf@zoho.com> References: <2e991bb7-c570-49ce-be94-3654945bb4b5@mousecar.com> <87d16jxjz6.fsf@eps142.cdf.udc.es> <861smzcgx3.fsf@zoho.com> <1b3bec6e-d4d5-37a7-ba54-49bd2d8281bd@yandex.com> <87377dtw33.fsf@qcore> <83zi9la78x.fsf@gnu.org> <9uvak9ib98.fsf@fencepost.gnu.org> <83poah9v5c.fsf@gnu.org> <83fubcajtg.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1506377026 21518 195.159.176.226 (25 Sep 2017 22:03:46 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 25 Sep 2017 22:03:46 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Sep 26 00:03:37 2017 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dwbTO-0004jJ-K4 for geh-help-gnu-emacs@m.gmane.org; Tue, 26 Sep 2017 00:03:30 +0200 Original-Received: from localhost ([::1]:44471 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dwbTW-0002az-38 for geh-help-gnu-emacs@m.gmane.org; Mon, 25 Sep 2017 18:03:38 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51480) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dwbSz-0002aq-E0 for help-gnu-emacs@gnu.org; Mon, 25 Sep 2017 18:03:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dwbSv-0000Rg-5K for help-gnu-emacs@gnu.org; Mon, 25 Sep 2017 18:03:05 -0400 Original-Received: from [195.159.176.226] (port=58644 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dwbSu-0000RI-Tu for help-gnu-emacs@gnu.org; Mon, 25 Sep 2017 18:03:01 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dwbSe-0001rn-PL for help-gnu-emacs@gnu.org; Tue, 26 Sep 2017 00:02:44 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Original-Lines: 45 Original-X-Complaints-To: usenet@blaine.gmane.org Mail-Copies-To: never Cancel-Lock: sha1:n2Wy0osm8CuslnY6j213iez3C/w= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:114401 Archived-At: Glenn Morris wrote: > Wow. I find this an extraordinary statement. > For example, it means that "emacs [-Q] > somefile" could eg happily delete your home > directory. Please reconsider. On Unix systems we like to say everything is a file [1]. The first thing you do when you don't understand something is to have a glance under the hood which translates to reviewing one or more files. This is such everyday-behavior I never even considered it could cause the kind of damage you describe. If indeed it can, this should be the exception and the default behavior should not allow it. [1] "For example, let's say you want to find information about your CPU. The /proc directory contains a special file – /proc/cpuinfo – that contains this information. You don't need a special command that tells you your CPU info – you can just read the contents of this file using any standard command that works with plain-text files. For example, you could use the command cat /proc/cpuinfo to print this file's contents to the terminal – printing your CPU information to the terminal. You could even open /proc/cpuinfo in a text editor to view its contents." https://www.howtogeek.com/117939/htg-explains-what-everything-is-a-file-means-on-linux/ -- underground experts united http://user.it.uu.se/~embe8573