core: restrict ImportCredential= globbing
Let's restrict how we apply credential globbing in ImportCredential=, so that we have some flexibility in automatically extending the glob expression with per-instance data eventually without getting into conflict with the globbing parts. In our current uses we only allow globbing at the end of the expression, and this is a new, unreleased feature hence let's be restrictive on this initially. We can still relax this later if we feel the need to after all. Fixes: #28022
This commit is contained in:
@@ -3320,6 +3320,12 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX
|
||||
<filename>/usr/lib/credstore.encrypted/</filename> in that order. When multiple credentials of the
|
||||
same name are found, the first one found is used.</para>
|
||||
|
||||
<para>The globbing expression implements a restrictive subset of <citerefentry
|
||||
project='man-pages'><refentrytitle>glob</refentrytitle><manvolnum>7</manvolnum></citerefentry>: only
|
||||
a single trailing <literal>*</literal> wildcard may be specified. Both <literal>?</literal> and
|
||||
<literal>[]</literal> wildcards are not permitted, nor are <literal>*</literal> wildcards anywhere
|
||||
except at the end of the glob expression.</para>
|
||||
|
||||
<para>When multiple credentials of the same name are found, credentials found by
|
||||
<varname>LoadCredential=</varname> and <varname>LoadCredentialEncrypted=</varname> take priority over
|
||||
credentials found by <varname>ImportCredential=</varname>.</para></listitem>
|
||||
|
||||
Reference in New Issue
Block a user