From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Daiki Ueno" Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: encrypt.el in No Gnus 0.7 Date: Sat, 3 Nov 2007 11:49:50 +0900 Message-ID: <54a15d860711021949q14e59f94g68bc23c603e2923a@mail.gmail.com> References: <87zly3y4ru.fsf@catnip.gol.com> <87odejy30k.fsf@catnip.gol.com> <54a15d860710311830s4fa203e3y53fbd6f51496f007@mail.gmail.com> <54a15d860711010824w6888aafdgb0a0e5d48f6fdebb@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1194058209 10730 80.91.229.12 (3 Nov 2007 02:50:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 3 Nov 2007 02:50:09 +0000 (UTC) To: "Daiki Ueno" , emacs-devel@gnu.org, ding@gnus.org, "Miles Bader" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 03 03:50:12 2007 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.50) id 1Io95P-0005YO-IX for ged-emacs-devel@m.gmane.org; Sat, 03 Nov 2007 03:50:11 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Io95F-0005sM-6u for ged-emacs-devel@m.gmane.org; Fri, 02 Nov 2007 22:50:01 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Io95B-0005q3-Gn for emacs-devel@gnu.org; Fri, 02 Nov 2007 22:49:57 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Io958-0005ns-Ur for emacs-devel@gnu.org; Fri, 02 Nov 2007 22:49:56 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Io958-0005no-SH for emacs-devel@gnu.org; Fri, 02 Nov 2007 22:49:54 -0400 Original-Received: from nz-out-0506.google.com ([64.233.162.225]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Io957-0000Ln-OW for emacs-devel@gnu.org; Fri, 02 Nov 2007 22:49:53 -0400 Original-Received: by nz-out-0506.google.com with SMTP id f1so769357nzc for ; Fri, 02 Nov 2007 19:49:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=5gph7mvZ5b4dAascFyqC5pk7dN0kw2lP92F+bJG63bo=; b=TsEmwghxDqPtWrUgZ4+OcAAmvxbGDkDHl/LQTag1nsjT9j4WFe2H+tiNHkd1KEt/P30NNuBbC5B4+M4NBCmRWK3pnhX9fCUhLksIcLDdN2lp0u6BzqnNCbhcKGI8S9mk4Q3ObeyLm+kPg9DcLWyYV+RKlVBQnzWMHAdno0irpUs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=DIkFYrVV5R+JIAmlCmPeQErcR/dyXp6SSMlcBgyJhSz13npHriIQFA+XLUZ7O4apOzi7Bx+RiNl0akizL3scQkBcepj+ITZsdIrqRqSSNmSnnCAWohpyV9mhgFdi+qGaHSXKgqu5zMrf0faetoHhSnuPK8eIhfjoz5LWDxWhASs= Original-Received: by 10.142.213.9 with SMTP id l9mr720091wfg.1194058190965; Fri, 02 Nov 2007 19:49:50 -0700 (PDT) Original-Received: by 10.142.213.14 with HTTP; Fri, 2 Nov 2007 19:49:50 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-Google-Sender-Auth: e7b3160573da82f7 X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) 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:82394 gmane.emacs.gnus.general:65538 Archived-At: 2007/11/2, Ted Zlatanov : > DU> I think encrypt-file-alist is too much custamisable since GnuPG > DU> records what cipher is used to encrypt in the PGP message. See > DU> RFC2440. > > Again, you're tightly bound to GnuPG. Does EasyPG support arbitrary, > user-supplied ciphers? I didn't see that ability. I doubt that the ability is worth considering. Who wants to use user-supplied ciphers which are appearantly weaker than ones GnuPG supports? Regards, -- Daiki Ueno