all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Vivien Kraus <vivien@planete-kraus.eu>, 70278@debbugs.gnu.org
Subject: bug#70278: udevd[87]: specified group 'sgx' unknown
Date: Tue, 16 Apr 2024 19:23:09 +0200	[thread overview]
Message-ID: <875xwhkyrm.fsf@gnu.org> (raw)
In-Reply-To: <e8ea58a89cdc22d26c280041914bfe98ae1104bf.camel@gmail.com> (Liliana Marie Prikler's message of "Thu, 11 Apr 2024 19:08:58 +0200")

Hi,

Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:

> Am Donnerstag, dem 11.04.2024 um 09:58 +0200 schrieb Ludovic Courtès:
>> Ludovic Courtès <ludo@gnu.org> skribis:
>> 
>> > Since the recent ‘gnome-team’ merge, we get this message at boot
>> > time:
>> > 
>> >   udevd[87]: specified group 'sgx' unknown
>> > 
>> > Should we add ‘sgx’ to ‘%base-groups’?  (What is it for?)
>> 
>> Cc’ing Vivien & Liliana who might know more about this.
> This seems related to Intel's Software Guard eXtensions, or, as we in
> the free world like to call them Security paper Generator eXtensions. 

:-)

> As far as I'm aware, these ought to be disabled anyway, and we might
> want to drop the offending lines.  According to [1], there's only two
> of them anyway.

[...]

> [1] https://wiki.linuxfromscratch.org/lfs/ticket/5265

Sounds good.  (My intuition would have been to create the ‘sgx’ group to
placate udev, but removing those lines may be even better.)

Can you look into it?

Thanks,
Ludo’.




      reply	other threads:[~2024-04-16 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 14:16 bug#70278: udevd[87]: specified group 'sgx' unknown Ludovic Courtès
2024-04-11  7:58 ` Ludovic Courtès
2024-04-11 17:08   ` Liliana Marie Prikler
2024-04-16 17:23     ` Ludovic Courtès [this message]

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=875xwhkyrm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=70278@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=vivien@planete-kraus.eu \
    /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/guix.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.