From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: David Bremner Newsgroups: gmane.emacs.bugs Subject: bug#18513: 24.3; message-mode sends unencrypted on error Date: Mon, 23 Sep 2019 09:18:50 -0300 Message-ID: <877e5zjjdh.fsf@tethera.net> References: <878ulebz1x.fsf@maritornes.cs.unb.ca> <87zjdid6ny.fsf-ueno@gnu.org> <87k34mei9j.fsf@maritornes.cs.unb.ca> <87muev8cc3.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="240148"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 18513@debbugs.gnu.org, Daniel Kahn Gillmor , Daiki Ueno To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Sep 23 14:29:08 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 1iCNSl-0010LV-J5 for geb-bug-gnu-emacs@m.gmane.org; Mon, 23 Sep 2019 14:29:07 +0200 Original-Received: from localhost ([::1]:55922 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iCNSj-0007QO-PD for geb-bug-gnu-emacs@m.gmane.org; Mon, 23 Sep 2019 08:29:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48350) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iCNJ0-0007LZ-Ul for bug-gnu-emacs@gnu.org; Mon, 23 Sep 2019 08:19:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iCNIz-00024S-Tz for bug-gnu-emacs@gnu.org; Mon, 23 Sep 2019 08:19:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54703) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iCNIz-00024N-Qp for bug-gnu-emacs@gnu.org; Mon, 23 Sep 2019 08:19:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iCNIz-0000ah-L9 for bug-gnu-emacs@gnu.org; Mon, 23 Sep 2019 08:19:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: David Bremner Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 23 Sep 2019 12:19: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.15692411382258 (code B ref 18513); Mon, 23 Sep 2019 12:19:01 +0000 Original-Received: (at 18513) by debbugs.gnu.org; 23 Sep 2019 12:18:58 +0000 Original-Received: from localhost ([127.0.0.1]:35291 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iCNIv-0000aM-MQ for submit@debbugs.gnu.org; Mon, 23 Sep 2019 08:18:57 -0400 Original-Received: from fethera.tethera.net ([198.245.60.197]:41280) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iCNIv-0000aD-0H for 18513@debbugs.gnu.org; Mon, 23 Sep 2019 08:18:57 -0400 Original-Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1iCNIp-00054W-9B; Mon, 23 Sep 2019 08:18:51 -0400 Original-Received: (nullmailer pid 21760 invoked by uid 1000); Mon, 23 Sep 2019 12:18:50 -0000 In-Reply-To: <87muev8cc3.fsf@gnus.org> 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:166992 Archived-At: Lars Ingebrigtsen writes: > 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. > I don't think the fact that we can't do a perfect job is a reason not to improve the error checking. There are many errors that can be detected that currently are not. Is erroring on an unknown mml tag (which nonethless actually looks like a tag) actually difficult? d