On 12/22/22 15:39, Lennart Poettering wrote:
Well, the thing is: a chain of trust is a*chain*, hence you must
ultimately hook validation to what the firmware provides you with as
root. And that ultimately is the SecureBoot db on commodity hardware.
Well, the thing with a chain of trust is the
OLD: Fedora-Rawhide-20221223.n.0
NEW: Fedora-Rawhide-20221224.n.0
= SUMMARY =
Added images:0
Dropped images: 1
Added packages: 0
Dropped packages:2
Upgraded packages: 39
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:26.30 MiB
> On 12/22/22 15:39, Lennart Poettering wrote:
>
>
>
> Well, the thing with a chain of trust is the fact that the only chain
> the user can trust is the one that he himself or the host device he owns
> and operates generated that trust of chain, from link 0 in that chain. (
> And we all know
On Tue, 2022-02-08 at 15:12 -0500, Adam Jackson wrote:
> xorg-x11-xdm
X Display Manager with support for XDMCP, host chooser
what are the alternatives of "Display Manager" ? and "with support for
XDMCP" ? only gdm ?
And xdm is not abandoned https://gitlab.freedesktop.org/xorg/app/xdm ,
maybe I
> On Tue, 2022-02-08 at 15:12 -0500, Adam Jackson wrote:
>
> X Display Manager with support for XDMCP, host chooser
>
> what are the alternatives of "Display Manager" ? and "with support for
> XDMCP" ? only gdm ?
>
> And xdm is not abandoned https://gitlab.freedesktop.org/xorg/app/xdm ,
> mayb
* Vít Ondruch:
> Working with upstream on one issue [1], it seems that the culprit is in
> the Fedora compiler options. Is there some convenient way to set them
> up? Of course I can copy them from log, or somehow put together from the
> RPM macros, but I'd appreciate if there was some easier w
