From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-crypt broken on Ubuntu 18.04
Date: Thu, 14 Jun 2018 07:31:04 +0200 [thread overview]
Message-ID: <87d0wurl2f.fsf@wi.uni-muenster.de> (raw)
In-Reply-To: <87tvq6cmcp.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Thu, 14 Jun 2018 01:12:22 +0200")
On 2018-06-14, Óscar Fuentes wrote:
> While trying to create a demo file I noticed that decryption works fine
> as long as the content was relatively new, while it fails for content
> that was encrypted years ago.
>
> I tried setting epg-gpg-program to "gpg" (it is "gpg2" by default) for
> encrypting some tests but then decryption worked fine on those tests.
Probably you encrypted without integrity protection, which was
always a bad idea but in view of EFAIL attacks has recently gained
lots of attention as Bad Thing. Nowadays GnuPG returns a failure,
you can override that if you know what you are doing.
See there: https://dev.gnupg.org/T3714
Best wishes
Jens
next prev parent reply other threads:[~2018-06-14 5:31 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 [this message]
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 ` do not ignore mdc errors on a permanent basis (was: org-crypt broken on Ubuntu 18.04) Gregor Zattler
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=87d0wurl2f.fsf@wi.uni-muenster.de \
--to=lechten@wi.uni-muenster.de \
--cc=emacs-orgmode@gnu.org \
--cc=ofv@wanadoo.es \
/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).