From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Duncan <1i5t5.duncan@cox.net>
Subject: Re: [gentoo-dev] Re: Profile 23.0 testing with stages and binhost (part 2 of 2)
Date: Sat, 16 Mar 2024 17:16:47 +0100 [thread overview]
Message-ID: <4288192.1IzOArtZ34@noumea> (raw)
In-Reply-To: <pan$e3c8e$32291c79$922a2a59$16fb20b0@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Am Samstag, 16. März 2024, 13:12:04 CET schrieb Duncan:
> Andreas K. Huettel posted on Fri, 15 Mar 2024 19:12:54 +0100 as excerpted:
>
> > Note 3: amd64 now has CET turned on by default.
> > https://docs.kernel.org/next/x86/shstk.html If you have already used the
> > unannounced 23.0 profiles, you should wipe your package cache and emerge
> > -ev world now.
>
> There's not much about CET in any of the links. While the kernel.org link
> describes what it does (in a line, "yese": yet another security
> enhancement) a bit, it doesn't say how to actually find whether your
> hardware supports it, and the gentoo wiki and bug links say even less --
> in particular, unless I missed it, the changes and update instructions
> links don't appear to mention CET or shadow-stacks AT ALL.
That's because it was a last-minute addition, and not particularly well
thought through. :|
Ignore Note 3. The part about emerge -ev world is just plain wrong for now.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, comrel, toolchain, base-system, perl, libreoffice)
https://wiki.gentoo.org/wiki/User:Dilfridge
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-16 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 18:12 [gentoo-dev] Profile 23.0 testing with stages and binhost (part 2 of 2) Andreas K. Huettel
2024-03-15 23:23 ` Sam James
2024-03-16 9:34 ` Andreas K. Huettel
2024-03-16 12:12 ` [gentoo-dev] " Duncan
2024-03-16 16:16 ` Andreas K. Huettel [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=4288192.1IzOArtZ34@noumea \
--to=dilfridge@gentoo.org \
--cc=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox