From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#18513: 24.3; message-mode sends unencrypted on error Date: Mon, 23 Sep 2019 13:46:20 +0200 Message-ID: <87muev8cc3.fsf@gnus.org> References: <878ulebz1x.fsf@maritornes.cs.unb.ca> <87zjdid6ny.fsf-ueno@gnu.org> <87k34mei9j.fsf@maritornes.cs.unb.ca> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="78683"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 18513@debbugs.gnu.org, Daiki Ueno To: David Bremner Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Sep 23 13:51:29 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iCMsG-000KDL-V8 for geb-bug-gnu-emacs@m.gmane.org; Mon, 23 Sep 2019 13:51:25 +0200 Original-Received: from localhost ([::1]:55140 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iCMsF-00081P-Ih for geb-bug-gnu-emacs@m.gmane.org; Mon, 23 Sep 2019 07:51:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43851) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iCMo3-0004uu-AL for bug-gnu-emacs@gnu.org; Mon, 23 Sep 2019 07:47:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iCMo2-0005gU-6l for bug-gnu-emacs@gnu.org; Mon, 23 Sep 2019 07:47:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54659) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iCMo2-0005gQ-3p for bug-gnu-emacs@gnu.org; Mon, 23 Sep 2019 07:47:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iCMo2-0003iZ-0J for bug-gnu-emacs@gnu.org; Mon, 23 Sep 2019 07:47:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 23 Sep 2019 11:47:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 18513 X-GNU-PR-Package: emacs Original-Received: via spool by 18513-submit@debbugs.gnu.org id=B18513.156923918612535 (code B ref 18513); Mon, 23 Sep 2019 11:47:01 +0000 Original-Received: (at 18513) by debbugs.gnu.org; 23 Sep 2019 11:46:26 +0000 Original-Received: from localhost ([127.0.0.1]:35244 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iCMnS-0003Fp-1K for submit@debbugs.gnu.org; Mon, 23 Sep 2019 07:46:26 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:33982) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iCMnQ-0003EG-L9 for 18513@debbugs.gnu.org; Mon, 23 Sep 2019 07:46:25 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=marnie) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iCMnN-0006DH-0G; Mon, 23 Sep 2019 13:46:23 +0200 In-Reply-To: <87k34mei9j.fsf@maritornes.cs.unb.ca> (David Bremner's message of "Mon, 29 Sep 2014 14:14:00 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:166986 Archived-At: David Bremner writes: > It's definitely an improvement, and it fixes the scenario I reported. On > the other hand, if the use corrupts the #secure tag then essentially the > same behaviour results. Would it be possible to have a strict mode where > any unknown mml tag causes an error? I don't think it's possible to do that in general -- for instance, if the user removes the first three characters from the MML tag (leaving a line with just "ecure ..."), then Message can't know that it's supposed to be secure... So I don't see any way to do this in general, and I'm closing this bug report. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no