SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

man: document unlocked as default IMDS network mode

Browse Source 
The default IMDS network mode was changed to unlocked, but the
systemd-imdsd@.service documentation still described locked as the
default.

Fixes #42687
This commit is contained in:
Guillaume Kehren
2026-07-21 11:43:52 +01:00
committed by Luca Boccassi
parent ab373b2cec
commit ac64b2dfa3
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/systemd-imdsd@.service.xml
+2 -2
View File
@@ -69,10 +69,10 @@
<para>Takes one of <literal>off</literal>, <literal>locked</literal>, <para>Takes one of <literal>off</literal>, <literal>locked</literal>,
<literal>unlocked</literal>. Controls whether and how to set up networking for IMDS endpoint <literal>unlocked</literal>. Controls whether and how to set up networking for IMDS endpoint
access. Unless set to <literal>off</literal> early boot networking is enabled, ensuring that the access. Unless set to <literal>off</literal> early boot networking is enabled, ensuring that the
IMDS endpoint can be reached. If set to <literal>locked</literal> (the default) direct access to IMDS endpoint can be reached. If set to <literal>locked</literal> direct access to
the IMDS endpoint by regular unprivileged processes is disabled via a "prohibit" route, so that any the IMDS endpoint by regular unprivileged processes is disabled via a "prohibit" route, so that any
access must be done through <filename>systemd-imdsd@.service</filename> or its associated tools. If access must be done through <filename>systemd-imdsd@.service</filename> or its associated tools. If
set to <literal>unlocked</literal> this "prohibit" route is not created, and regular unprivileged set to <literal>unlocked</literal> (the default) this "prohibit" route is not created, and regular unprivileged
processes can directly contact IMDS.</para> processes can directly contact IMDS.</para>
<xi:include href="version-info.xml" xpointer="v261"/> <xi:include href="version-info.xml" xpointer="v261"/>