From: David Bremner <david@tethera.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 18513@debbugs.gnu.org,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Daiki Ueno <ueno@gnu.org>
Subject: bug#18513: 24.3; message-mode sends unencrypted on error
Date: Mon, 23 Sep 2019 09:18:50 -0300 [thread overview]
Message-ID: <877e5zjjdh.fsf@tethera.net> (raw)
In-Reply-To: <87muev8cc3.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> David Bremner <david@tethera.net> 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
next prev parent reply other threads:[~2019-09-23 12:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 6:12 bug#18513: 24.3; message-mode sends unencrypted on error David Bremner
2014-09-29 11:09 ` Daiki Ueno
2014-09-29 12:14 ` David Bremner
2014-09-30 1:36 ` Daiki Ueno
2019-09-23 11:46 ` Lars Ingebrigtsen
2019-09-23 12:18 ` David Bremner [this message]
2019-09-23 13:53 ` Lars Ingebrigtsen
2019-09-24 10:49 ` Daniel Kahn Gillmor
2019-09-25 13:05 ` Lars Ingebrigtsen
2014-10-01 1:28 ` Glenn Morris
2014-10-01 2:32 ` Daiki Ueno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e5zjjdh.fsf@tethera.net \
--to=david@tethera.net \
--cc=18513@debbugs.gnu.org \
--cc=dkg@fifthhorseman.net \
--cc=larsi@gnus.org \
--cc=ueno@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.