From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andrea Cardaci <cyrus.and@gmail.com>
Cc: 37454@debbugs.gnu.org
Subject: bug#37454: EPA (The EasyPG Assistant) problems saving .tar.gpg files
Date: Mon, 03 Aug 2020 09:36:47 +0200 [thread overview]
Message-ID: <87sgd4w580.fsf@gnus.org> (raw)
In-Reply-To: <CACMsj9OhK+aaVaACxtNfqDWy4ADw1Gtof+K0MVEqWdtKhQ3htA@mail.gmail.com> (Andrea Cardaci's message of "Mon, 9 Dec 2019 13:47:36 +0100")
Andrea Cardaci <cyrus.and@gmail.com> writes:
> On Thu, 19 Sep 2019 at 01:31, Andrea Cardaci <cyrus.and@gmail.com> wrote:
>> Now a message says "Wrote /tmp/test.tar.gpg" but the `*Keys*` buffer
>> is still there (that doesn't happen for regular .gpg files) and a
>> recursive edit is in progress (there are square brackets around the
>> major modes).
>
> At least this has been fixed in Emacs 27:
I tried the recipe in Emacs 28.1, and I'm not able to reproduce the bugs
as described -- I get an encrypted file that's saved.
file /tmp/test4.tar.gpg
/tmp/test4.tar.gpg: GPG symmetrically encrypted data (AES256 cipher)
However, when loading the back again, after displaying the contents, I
get:
Parsing tar file...
File mode specification error: (error Malformed Tar header)
So there's still some bugs in this area, apparently...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-03 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 23:31 bug#37454: EPA (The EasyPG Assistant) problems saving .tar.gpg files Andrea Cardaci
2019-12-09 12:47 ` Andrea Cardaci
2020-08-03 7:36 ` Lars Ingebrigtsen [this message]
2020-08-03 7:39 ` Lars Ingebrigtsen
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=87sgd4w580.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37454@debbugs.gnu.org \
--cc=cyrus.and@gmail.com \
/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.