From: Eli Zaretskii <eliz@gnu.org>
To: "Michalis V." <mvar.40k@gmail.com>
Cc: mvar.40k@gmail.com, larsi@gnus.org, mcenturion@fing.edu.uy,
arthur.miller@live.com, 47058@debbugs.gnu.org
Subject: bug#47058: 28.0.50; Dired Z: insert-directory: Reading directory: No such file or directory, CrossLine_linux_x86
Date: Tue, 21 Sep 2021 12:32:15 +0300 [thread overview]
Message-ID: <83fstyz334.fsf@gnu.org> (raw)
In-Reply-To: <87a6k6qoat.fsf@cnu407c2zx.nsn-intra.net> (mvar.40k@gmail.com)
> From: "Michalis V." <mvar.40k@gmail.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, mvar.40k@gmail.com,
> mcenturion@fing.edu.uy, 47058@debbugs.gnu.org, arthur.miller@live.com
> Date: Tue, 21 Sep 2021 12:18:50 +0300
>
> Btw one of the reasons i went with this approach and included -C
> parameter for tars were some security concerns expressed in #25611.
That's a separate issue. And I don't see how is it a security issue
for Emacs, when unpacking an archive manually with 'tar' etc. would
produce the same results. If the user wants to overwrite his/her
sensitive files, we should let them do it, in the same way as other
utilities do. But that's MO, and it is a separate concern anyway.
> There's also a suggestion in the discussion there that Z should just
> decompress and not untar the archive and the un-tarring should be a
> separate action/procedure. That would be a drastic solution to this
> problem but on the other hand it would make sense semantically
> (extract != decompress). What is your opinion on this?
I'm okay with having a separate command for unpacking, yes. We'd need
to provide a backward-compatibility option if we do that, since 'Z'
unpacks for some time now.
> in any case i'll try to assemble another patch based on your suggestion.
Thanks.
next prev parent reply other threads:[~2021-09-21 9:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 20:26 bug#47058: 28.0.50; Dired Z: insert-directory: Reading directory: No such file or directory, CrossLine_linux_x86 Jean Louis
2021-08-31 21:33 ` Marco Centurion
2021-08-31 22:12 ` Arthur Miller
2021-09-01 13:59 ` Marco Centurion - URI
2021-09-01 16:06 ` Arthur Miller
2021-09-20 22:12 ` Michalis V.
2021-09-21 4:32 ` Lars Ingebrigtsen
2021-09-21 8:24 ` Eli Zaretskii
2021-09-21 9:18 ` Michalis V.
2021-09-21 9:32 ` Eli Zaretskii [this message]
2021-09-21 17:10 ` Lars Ingebrigtsen
[not found] ` <83a6k5yfrb.fsf@gnu.org>
2021-09-21 17:58 ` Lars Ingebrigtsen
2021-09-21 18:38 ` Gregory Heytings
2021-09-21 18:43 ` Eli Zaretskii
2021-09-21 19:19 ` Gregory Heytings
2021-09-21 20:11 ` Michalis V.
2021-09-21 20:48 ` Gregory Heytings
2021-09-22 5:40 ` Eli Zaretskii
2021-09-22 7:15 ` Gregory Heytings
2021-09-22 7:54 ` Eli Zaretskii
2021-09-22 8:07 ` Gregory Heytings
2021-09-21 17:07 ` Lars Ingebrigtsen
2021-09-21 20:43 ` Michalis V.
2021-09-22 6:00 ` Eli Zaretskii
2021-09-21 8:25 ` Michael Albinus
2021-09-21 9:24 ` Michalis V.
2021-09-21 12:06 ` Michael Albinus
2022-03-11 8:29 ` Michael Albinus
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fstyz334.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47058@debbugs.gnu.org \
--cc=arthur.miller@live.com \
--cc=larsi@gnus.org \
--cc=mcenturion@fing.edu.uy \
--cc=mvar.40k@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).