GNU bug report logs -
#74627
.dir-locals.el warning messages are confusing
Previous Next
To reply to this bug, email your comments to 74627 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#74627
; Package
emacs
.
(Sat, 30 Nov 2024 17:21:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Björn Lindqvist <bjourne <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sat, 30 Nov 2024 17:21:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Warnings about potential security issues should be easy to understand,
but the warnings produced by .dir-locals.el are not. When I open a
file in the Emacs source code it shows:
The local variables list in /home/bjourne/p/emacs/
or .dir-locals.el contains values that may not be safe (*).
Why does it say "or"? What does the asterisk (*) mean? Could the
descriptions for "!" and "i" be clearer so it is more obvious what is
applied and what is ignored?
--
mvh/best regards Björn Lindqvist
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#74627
; Package
emacs
.
(Thu, 05 Dec 2024 09:40:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 74627 <at> debbugs.gnu.org (full text, mbox):
> From: Björn Lindqvist <bjourne <at> gmail.com>
> Date: Sat, 30 Nov 2024 18:20:35 +0100
>
> Warnings about potential security issues should be easy to understand,
> but the warnings produced by .dir-locals.el are not. When I open a
> file in the Emacs source code it shows:
>
> The local variables list in /home/bjourne/p/emacs/
> or .dir-locals.el contains values that may not be safe (*).
>
> Why does it say "or"?
Because that function is called with a single flag argument which
could be set non-nil either due to unsafe file-local variables or due
to .dir-locals.el.
> What does the asterisk (*) mean?
It means the variables marked with the asterisk in the list of
below this text could be unsafe.
> Could the descriptions for "!" and "i" be clearer so it is more
> obvious what is applied and what is ignored?
Please tell what is unclear there. The current text is
! -- to apply the local variables list, and permanently mark these
values (*) as safe (in the future, they will be set automatically.)
i -- to ignore the local variables list, and permanently mark these
values (*) as ignored"
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#74627
; Package
emacs
.
(Wed, 11 Dec 2024 08:20:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 74627 <at> debbugs.gnu.org (full text, mbox):
Hello Eli,
Den tors 5 dec. 2024 kl 10:38 skrev Eli Zaretskii <eliz <at> gnu.org>:
> > Warnings about potential security issues should be easy to understand,
> > but the warnings produced by .dir-locals.el are not. When I open a
> > file in the Emacs source code it shows:
> >
> > The local variables list in /home/bjourne/p/emacs/
> > or .dir-locals.el contains values that may not be safe (*).
> >
> > Why does it say "or"?
>
> Because that function is called with a single flag argument which
> could be set non-nil either due to unsafe file-local variables or due
> to .dir-locals.el.
So there are multiple sources of unsafe variables, but the function
responsible for formulating the error message doesn't know what the
source is? Regardless of whether my guess is correct, the text should
not refer to the local variables in "/home/bjourne/p/emacs/" because
there can be no unsafe variables in directories (only files).
> > What does the asterisk (*) mean?
>
> It means the variables marked with the asterisk in the list of
> below this text could be unsafe.
Aha. Emacs lists both safe and unsafe variables. Why does it list the
safe ones? The warning would be much clearer if the safe variables
were omitted since they don't matter. That would make it clear what
variables "!" and "i" choices apply or mark as safe/ignored.
--
mvh/best regards Björn Lindqvist
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#74627
; Package
emacs
.
(Wed, 11 Dec 2024 11:18:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 74627 <at> debbugs.gnu.org (full text, mbox):
Björn Lindqvist <bjourne <at> gmail.com> writes:
> Aha. Emacs lists both safe and unsafe variables. Why does it list the
> safe ones? The warning would be much clearer if the safe variables
> were omitted since they don't matter. That would make it clear what
> variables "!" and "i" choices apply or mark as safe/ignored.
You have to see all of them to make an informed decision, I think.
Otherwise, an unsafe variable might be referring to a safe one, which is
the one containing the malicious bits.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#74627
; Package
emacs
.
(Wed, 11 Dec 2024 15:01:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 74627 <at> debbugs.gnu.org (full text, mbox):
> From: Björn Lindqvist <bjourne <at> gmail.com>
> Date: Wed, 11 Dec 2024 09:18:33 +0100
> Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>, 74627 <at> debbugs.gnu.org
>
> Den tors 5 dec. 2024 kl 10:38 skrev Eli Zaretskii <eliz <at> gnu.org>:
>
> > > Warnings about potential security issues should be easy to understand,
> > > but the warnings produced by .dir-locals.el are not. When I open a
> > > file in the Emacs source code it shows:
> > >
> > > The local variables list in /home/bjourne/p/emacs/
> > > or .dir-locals.el contains values that may not be safe (*).
> > >
> > > Why does it say "or"?
> >
> > Because that function is called with a single flag argument which
> > could be set non-nil either due to unsafe file-local variables or due
> > to .dir-locals.el.
>
> So there are multiple sources of unsafe variables, but the function
> responsible for formulating the error message doesn't know what the
> source is?
Yes, that's my reading of the code.
> Regardless of whether my guess is correct, the text should
> not refer to the local variables in "/home/bjourne/p/emacs/" because
> there can be no unsafe variables in directories (only files).
Well, we consider variables in .dir-locals.el as belonging to the
directory in which it lives.
> > > What does the asterisk (*) mean?
> >
> > It means the variables marked with the asterisk in the list of
> > below this text could be unsafe.
>
> Aha. Emacs lists both safe and unsafe variables. Why does it list the
> safe ones? The warning would be much clearer if the safe variables
> were omitted since they don't matter. That would make it clear what
> variables "!" and "i" choices apply or mark as safe/ignored.
I can only guess: showing all of them lets you see the problematic one
in context.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#74627
; Package
emacs
.
(Wed, 11 Dec 2024 15:32:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 74627 <at> debbugs.gnu.org (full text, mbox):
>> Regardless of whether my guess is correct, the text should
>> not refer to the local variables in "/home/bjourne/p/emacs/" because
>> there can be no unsafe variables in directories (only files).
> Well, we consider variables in .dir-locals.el as belonging to the
> directory in which it lives.
I think it would be easier to understand for the reader if we can point
more precisely to the source (especially since now it can also come
from `.editorconfig`).
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#74627
; Package
emacs
.
(Wed, 11 Dec 2024 16:56:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 74627 <at> debbugs.gnu.org (full text, mbox):
> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: Björn Lindqvist <bjourne <at> gmail.com>,
> 74627 <at> debbugs.gnu.org
> Date: Wed, 11 Dec 2024 10:31:03 -0500
>
> >> Regardless of whether my guess is correct, the text should
> >> not refer to the local variables in "/home/bjourne/p/emacs/" because
> >> there can be no unsafe variables in directories (only files).
> > Well, we consider variables in .dir-locals.el as belonging to the
> > directory in which it lives.
>
> I think it would be easier to understand for the reader if we can point
> more precisely to the source (especially since now it can also come
> from `.editorconfig`).
Sure, but that's not what I meant to explain.
Severity set to 'wishlist' from 'normal'
Request was from
Stefan Kangas <stefankangas <at> gmail.com>
to
control <at> debbugs.gnu.org
.
(Thu, 02 Jan 2025 01:57:02 GMT)
Full text and
rfc822 format available.
This bug report was last modified 167 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.