From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: GnuTLS for W32 Date: Thu, 05 Jan 2012 01:44:24 -0500 Message-ID: References: <87ipktag2e.fsf@lifelogs.com> <87fwfxtxuz.fsf@wanadoo.es> <87aa64ubg9.fsf@wanadoo.es> <83boqkr9bp.fsf@gnu.org> <874nwcu17i.fsf@wanadoo.es> <834nwcr6un.fsf@gnu.org> <87vcosskhc.fsf@wanadoo.es> <831urgr2yr.fsf@gnu.org> <87r4zgsh2w.fsf@wanadoo.es> <87ipks3zbo.fsf@uwakimon.sk.tsukuba.ac.jp> <87boqk3q69.fsf@uwakimon.sk.tsukuba.ac.jp> <87aa634st8.fsf@uwakimon.sk.tsukuba.ac.jp> <87fwfvsgfv.fsf@wanadoo.es> <83r4zfpcfv.fsf@gnu.org> <87y5tnqmts.fsf@wanadoo.es> <83ipkrp34o.fsf@gnu.org> <87hb0bqcod.fsf@wanadoo.es> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1325745874 23511 80.91.229.12 (5 Jan 2012 06:44:34 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 5 Jan 2012 06:44:34 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?=C3=93scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 05 07:44:31 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Rih3u-0004yG-2P for ged-emacs-devel@m.gmane.org; Thu, 05 Jan 2012 07:44:30 +0100 Original-Received: from localhost ([::1]:33619 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rih3t-0005ca-4N for ged-emacs-devel@m.gmane.org; Thu, 05 Jan 2012 01:44:29 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:38834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rih3p-0005cJ-TU for emacs-devel@gnu.org; Thu, 05 Jan 2012 01:44:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rih3o-0006rv-TX for emacs-devel@gnu.org; Thu, 05 Jan 2012 01:44:25 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:41582) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rih3o-0006rq-Qk for emacs-devel@gnu.org; Thu, 05 Jan 2012 01:44:24 -0500 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1Rih3o-0001YA-Jj; Thu, 05 Jan 2012 01:44:24 -0500 In-reply-to: <87hb0bqcod.fsf@wanadoo.es> (message from =?utf-8?Q?=C3=93sca?= =?utf-8?Q?r?= Fuentes on Thu, 05 Jan 2012 00:18:42 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.10 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:147321 Archived-At: > From: Óscar Fuentes > Date: Thu, 05 Jan 2012 00:18:42 +0100 > > Eli Zaretskii writes: > > [snip] > > >> Depending on how Emacs was installed, that would require elevated > >> privileges, something ELPA can not ask for, AFAIK. > > > > FUD. Emacs is not installed by corporate policies on Windows, so this > > won't happen except in very rare cases. > > Have you used MS Windows Vista or Seven lately? If you install Emacs on > "Program Files" Emacs itself does not have write rights to its own > directory (actually, sometimes the OS can fool the app into believing > that it is creating or changing files there, but in reality it is > diverting the operation to somewhere else. Look for "File and Registry > Virtualization" for further info). You must fidle with directory > permissions (that is, shutting down a security measure) for Emacs, or > the user in front of the computer, to alter its contents without > escalating privileges. Irrelevant: we are talking about the same user who already installed Emacs on that system, so that user will have already solved this "problem" using one of the few available solutions, be it privilege elevation, disabling UAC altogether, installing Emacs not in "Program Files", or something else.