All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ruben Safir <ruben@mrbrklyn.com>
Cc: "Bjørn Mork" <bjorn@mork.no>, kernelnewbies@kernelnewbies.org
Subject: Re: efivars
Date: Thu, 23 Sep 2021 10:57:29 +0200	[thread overview]
Message-ID: <YUxBecj4CHMP5d1O@kroah.com> (raw)
In-Reply-To: <20210923084128.GB24848@www2.mrbrklyn.com>

On Thu, Sep 23, 2021 at 04:41:28AM -0400, Ruben Safir wrote:
> On Thu, Sep 23, 2021 at 09:32:00AM +0200, Bjørn Mork wrote:
> > Ruben Safir <ruben@mrbrklyn.com> writes:
> > 
> > > I really just want to know what efi varriables exist and why we have a
> > > sys file for them
> > 
> > The "why" question is answered here:
> > https://www.kernel.org/doc/Documentation/filesystems/efivarfs.rst
> 
> 
> Thanks
> 
> I read that, but for my purposes it is circular.
> 
> They created another virtual fielsystem because the current
> /sys and /proc entries seemed to fail to do something consistently 
> as UEFI developed and was grafted on the current kernel.

Creating new filesystems is trivial in the kernel, and these didn't fall
into the rules allowed by sysfs, so a new one was created.  Just because
it is a new filesystem does not mean anything here.

> It doesn't explain why these new variables were needed in the 
> first place.

They are exposed by UEFI for the OS and userspace to use for various
things.  The filenames should show you the functionality to look up in
the UEFI spec if you are curious about anything specific in there.

> > The "what" question doesn't have a short answer.  If you don't want the
> > long one, then that's fine.  You don't need to worry about efi
> > variables.  Leave them alone and they will do you no harm.
> 
> They are a problem and present a securilty risk.

What security risk specifically?

And what problem specifically?

> I can't change
> anything and nobody asks me about OS design, but it does cause 
> real problems and I run into them repeatedly at installfests.

What specifc problems do they cause with installing a distro?

Details please.

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-09-23  8:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22  6:22 efivars Ruben Safir
2021-09-22  6:35 ` efivars Greg KH
2021-09-22 15:47   ` efivars Ruben Safir
2021-09-22 16:07     ` efivars Greg KH
2021-09-23  4:01       ` efivars Ruben Safir
2021-09-23  9:56       ` efivars Ruben Safir
2021-09-23 10:10         ` efivars Greg KH
2021-09-23 10:28         ` efivars FMDF
2021-09-23 12:34           ` efivars Ruben Safir
2021-09-23 12:40           ` efivars Ruben Safir
2021-09-23 12:44           ` efivars Ruben Safir
2021-09-22 15:58   ` efivars Ruben Safir
2021-09-22 16:11     ` efivars Greg KH
2021-09-22 17:04     ` efivars Valdis Klētnieks
2021-09-23  1:51       ` efivars Ruben Safir
2021-09-23  2:02       ` efivars Ruben Safir
2021-09-23  2:10         ` efivars Dave Stevens
2021-09-23  5:41         ` efivars Greg KH
2021-09-23  2:07       ` efivars Ruben Safir
2021-09-23  7:32         ` efivars Bjørn Mork
2021-09-23  8:41           ` efivars Ruben Safir
2021-09-23  8:57             ` Greg KH [this message]
2021-09-23  8:12         ` efivars Valdis Klētnieks
2021-09-23  8:32           ` efivars Ruben Safir
2021-09-23  7:13     ` efivars Bjørn Mork
2021-09-23  9:17       ` efivars Ruben Safir
2021-09-23  9:39         ` efivars Greg KH
     [not found] ` <CAPj211tgoRDDsZA_1ZM-kWRiHM9r2MQVi5b-mQenpP8pQmfvXg@mail.gmail.com>
2021-09-22 15:56   ` efivars Ruben Safir
2021-09-23  7:11 ` efivars FMDF
2021-09-23  7:22   ` efivars FMDF
2021-09-23  7:27     ` efivars FMDF
2021-09-23 12:24       ` efivars Ruben Safir
2021-09-23 12:36         ` efivars Greg KH
2021-09-23  9:38   ` efivars Ruben Safir
2021-09-23  9:56     ` efivars Greg KH

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=YUxBecj4CHMP5d1O@kroah.com \
    --to=greg@kroah.com \
    --cc=bjorn@mork.no \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=ruben@mrbrklyn.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. 
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.