From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: theme and a question about creating them Date: Wed, 05 Jan 2011 19:49:56 -0500 Message-ID: <87wrmi26vf.fsf@stupidchicken.com> References: <20101231155214.DE05339C1EA@djcbsoftware.nl> <87ipy7z8zd.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1294275034 23824 80.91.229.12 (6 Jan 2011 00:50:34 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 6 Jan 2011 00:50:34 +0000 (UTC) Cc: djcb@djcbsoftware.nl, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 06 01:50:29 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Pae3h-0002tm-5n for ged-emacs-devel@m.gmane.org; Thu, 06 Jan 2011 01:50:29 +0100 Original-Received: from localhost ([127.0.0.1]:41533 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pae3g-0002bQ-LM for ged-emacs-devel@m.gmane.org; Wed, 05 Jan 2011 19:50:28 -0500 Original-Received: from [140.186.70.92] (port=44997 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pae3b-0002b8-Po for emacs-devel@gnu.org; Wed, 05 Jan 2011 19:50:24 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pae3a-0006b4-MR for emacs-devel@gnu.org; Wed, 05 Jan 2011 19:50:23 -0500 Original-Received: from vm-emlprdomr-06.its.yale.edu ([130.132.50.147]:51590) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pae3a-0006ai-J6 for emacs-devel@gnu.org; Wed, 05 Jan 2011 19:50:22 -0500 Original-Received: from furball (72-254-57-233.client.stsn.net [72.254.57.233]) (authenticated bits=0) by vm-emlprdomr-06.its.yale.edu (8.14.4/8.14.4) with ESMTP id p060oB9h024368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 5 Jan 2011 19:50:18 -0500 Original-Received: by furball (Postfix, from userid 1000) id 82822161E9D; Wed, 5 Jan 2011 19:49:56 -0500 (EST) In-Reply-To: (Stefan Monnier's message of "Wed, 05 Jan 2011 16:05:09 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-Scanned-By: MIMEDefang 2.71 on 130.132.50.147 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:134317 Archived-At: Stefan Monnier writes: >> Maybe we should just go back to unconditionally loading theme files, >> since it's unlikely we can make evaluating Elisp code truly safe. >> Any objections or alternative ideas? > > IIUC the problem is that users tend to expect themes to be "just data", > without any possible risks, so they may try themes they download from > random places on the web. > > So, I think it's OK to use unsafep to weed out the "safe" themes, and > prompt users for the remaining themes. But the prompt should make it > clear that we have no determined the theme to be dangerous, just that > Emacs did not recognize it as obviously safe and is unable to assess > whether it's dangerous or not. Sounds reasonable.