From: Gregor Zattler <telegraph@gmx.net>
To: emacs-orgmode@gnu.org
Subject: do not ignore mdc errors on a permanent basis (was: org-crypt broken on Ubuntu 18.04)
Date: Fri, 27 Jul 2018 00:12:23 +0200 [thread overview]
Message-ID: <87pnz9pry0.fsf@len.workgroup> (raw)
In-Reply-To: <878t5ytdiw.fsf@telefonica.net>
Hi Óscar,
* Óscar Fuentes <ofv@wanadoo.es> [2018-07-26; 13:57]:
> For the record: executing gpg2 from the command line is revealing:
>
> gpg: WARNING: message was not integrity protected
> gpg: Hint: If this message was created before the year 2003 it is
> likely that this message is legitimate. This is because back
> then integrity protection was not widely used.
> gpg: Use the option '--ignore-mdc-error' to decrypt anyway.
> gpg: decryption forced to fail!
>
> The solution is to add `ignore-mdc-error' to ~/.gnupg/gpg.conf.
I hope you'll do this only as a temporary meassure. Your could
decrypt and re-encrypt the org-crypt parts in question iff you
are sure, they were encrypted years ago and their contents is ok.
But having this option in ~/.gnupg/gpg.conf otherwise weakens
the security of GnuPG usage considerably.
From the gpg man page:
--ignore-mdc-error
This option changes a MDC integrity protection failure
into a warning. This can be useful if a message is
partially corrupt, but it is necessary to get as much
data as possible out of the corrupt message. However,
be aware that a MDC protection failure may also mean
that the message was tampered with intentionally by an
attacker.
The usage scenario described in the first sentence is clearly a
one time thing. Putting this option in gpg.conf ignores these
kind of errors for all future usage, for risks and side effects
see the second sentence.
Ciao; Gregor
prev parent reply other threads:[~2018-07-26 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 17:24 org-crypt broken on Ubuntu 18.04 Óscar Fuentes
2018-06-13 19:22 ` Nicolas Goaziou
2018-06-13 20:11 ` Óscar Fuentes
2018-06-13 20:20 ` Thibault Polge
2018-06-13 23:12 ` Óscar Fuentes
2018-06-14 5:31 ` Jens Lechtenboerger
2018-06-14 11:57 ` hymie!
2018-06-20 2:05 ` Óscar Fuentes
2018-07-26 11:57 ` Óscar Fuentes
2018-07-26 22:12 ` Gregor Zattler [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnz9pry0.fsf@len.workgroup \
--to=telegraph@gmx.net \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).