Home
last modified time | relevance | path

Searched refs:in (Results 1 – 25 of 430) sorted by relevance

12345678910>>...18

/systemd-251/src/test/
Dtest-siphash24.c9 static void test_alignment_one(const uint8_t *in, size_t len, const uint8_t *key) { in test_alignment_one() argument
14 out = siphash24(in, len, key); in test_alignment_one()
23 siphash24_compress(in, len, &state); in test_alignment_one()
40 siphash24_compress(in, i, &state); in test_alignment_one()
41 siphash24_compress(&in[i], j - i, &state); in test_alignment_one()
42 siphash24_compress(&in[j], len - j, &state); in test_alignment_one()
50 const uint8_t in[15] = { 0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, in TEST() local
57 memcpy(in_buf, in, sizeof(in)); in TEST()
58 test_alignment_one(in_buf, sizeof(in), key); in TEST()
59 memcpy(in_buf + 1, in, sizeof(in)); in TEST()
[all …]
/systemd-251/src/basic/
Dsiphash24.h23 void siphash24_compress(const void *in, size_t inlen, struct siphash *state);
26 static inline void siphash24_compress_boolean(bool in, struct siphash *state) { in siphash24_compress_boolean() argument
27 uint8_t i = in; in siphash24_compress_boolean()
32 static inline void siphash24_compress_usec_t(usec_t in, struct siphash *state) { in siphash24_compress_usec_t() argument
33 siphash24_compress(&in, sizeof in, state); in siphash24_compress_usec_t()
36 static inline void siphash24_compress_safe(const void *in, size_t inlen, struct siphash *state) { in siphash24_compress_safe() argument
40 siphash24_compress(in, inlen, state); in siphash24_compress_safe()
43 static inline void siphash24_compress_string(const char *in, struct siphash *state) { in siphash24_compress_string() argument
44 siphash24_compress_safe(in, strlen_ptr(in), state); in siphash24_compress_string()
49 uint64_t siphash24(const void *in, size_t inlen, const uint8_t k[static 16]);
Dsiphash24.c75 const uint8_t *in = _in; in siphash24_compress() local
76 const uint8_t *end = in + inlen; in siphash24_compress()
80 assert(in); in siphash24_compress()
88 for ( ; in < end && left < 8; in ++, left ++) in siphash24_compress()
89 state->padding |= ((uint64_t) *in) << (left * 8); in siphash24_compress()
91 if (in == end && left < 8) in siphash24_compress()
113 for ( ; in < end; in += 8) { in siphash24_compress()
114 m = unaligned_read_le64(in); in siphash24_compress()
131 state->padding |= ((uint64_t) in[6]) << 48; in siphash24_compress()
134 state->padding |= ((uint64_t) in[5]) << 40; in siphash24_compress()
[all …]
/systemd-251/docs/
DUSER_RECORD.md12 and consume records in a more extensible format of a dictionary of key/value
17 directly in the home directory images
21 processes these JSON records for users that log in, and applies various
26 processes these JSON records of users that log in, and applies various
36 effect of `DynamicUser=` in service unit files) as these advanced JSON
45 JSON user records may contain various fields that are not available in `struct
77 JSON User Records may be transferred or written to disk in various protocols
80 also be dropped in number of drop-in directories as files. See
88 popular in the web communities, which hopefully should make it easy to link
103 user in all contexts, are portable and not security sensitive.
[all …]
DGROUP_RECORD.md17 ## Fields in the `regular` section
24 field of user records. A string in DNS domain name syntax.
34 (this field is typically in reverse domain name syntax.)
36 `lastChangeUSec` → An unsigned 64bit integer, a timestamp (in µs since the UNIX
40 `gid` → An unsigned integer in the range 0…4294967295: the numeric UNIX group
45 group. Note that JSON user records also contain a `memberOf` field, or in other
46 words a group membership can either be denoted in the JSON user record or in
47 the JSON group record, or in both. The list of memberships should be determined
61 ## Fields in the `privileged` section
67 `sg_passwd` field of `struct sgrp` (and `gr_passwd` of `struct group` in a
[all …]
DARCHITECTURE.md17 Directories in `src/` provide the implementation of all daemons, libraries and
24 You might wonder what kind of common code belongs in `src/shared/` and what
25 belongs in `src/basic/`. The split is like this: anything that is used to
28 `pam_systemd`), must be located in `src/basic` (those objects are not allowed
30 between multiple components and does not need to be in `src/basic/`, should be
31 in `src/shared/`.
36 - may be used by all code in the tree
40 - may be used by all code in the tree, except for code in `src/basic/`
44 - may be used by all code in the tree, except for code in `src/basic/`,
46 `src/journal/` that end up in `libjournal-client.a` convenience library.
[all …]
DHACKING.md18 (in `src/basic/` and `src/shared/`) unit tests should be sufficient. The general
19 policy is to keep tests in matching files underneath `src/test/`,
20 e.g. `src/test/test-path-util.c` contains tests for any functions in
22 test executable. For features at a higher level, tests in `src/test/` are very
23 strongly recommended. If that is not possible, integration tests in `test/` are
27 have setup for systemd, to ensure our codebase stays in good shape.
35 a set of `mkosi` build files directly in the source tree.
37 from an upstream distribution in combination with a fresh build of the project
38 in the local working directory. To make use of this, please install the
41 image for the host distro by default. It is sufficient to type `mkosi` in the
[all …]
DBOOT_LOADER_INTERFACE.md12 systems. Data is transferred between the boot loader and systemd in EFI
16 * The EFI Variable `LoaderTimeInitUSec` contains the timestamp in microseconds
17 when the loader was initialized. This value is the time spent in the firmware
19 string, in UTF-16.
21 * The EFI Variable `LoaderTimeExecUSec` contains the timestamp in microseconds
23 time spent in the loader is the difference between `LoaderTimeExecUSec` and
28 ESP the boot loader was run from formatted as NUL-terminated UTF16 string, in
32 currently in use. It may be modified both by the boot loader and by the
34 string, in UTF-16. The time is specified in µs.
37 timeout for a single following boot. It is set by the OS in order to request
[all …]
DUSERDB_AND_DESKTOPS.md2 title: systemd-homed and JSON User/Group Record Support in Desktop Environments
8 # `systemd-homed` and JSON User/Group Record Support in Desktop Environments
15 structures. Both additions are added in a fully backwards compatible way,
17 usual, meaning that for basic support no changes in the upper layers of the
18 stack (in particular desktop environments, such as GNOME or KDE) have to be
34 important in a world where most laptop users seldom shut down their computers
36 for the home directories remained in memory during system suspend, so that
41 Supporting this mechanism requires support in the desktop environment, since
43 system resume, from a lock screen or similar. This lock screen must run in
44 system context, and cannot run in the user's own context, since otherwise it
[all …]
DUSER_GROUP_API.md10 JSON User/Group Records (as described in the [JSON User Records](USER_RECORD.md)
18 expose. Or in other words, it both allows applications to efficiently query
23 records may be dropped in number of drop-in directories as files where they are
24 picked up in addition to the users/groups defined by this IPC logic. See
33 The API described in this document is based on a simple subset of the
35 preferring Varlink over D-Bus and other IPCs in this context was made for three
50 flooding in D-Bus' logic, and thus possibly result in termination of
51 communication. Since the APIs defined in this document need to support
61 group record, it contacts all sockets bound in this directory in parallel, and
71 defined in which queries are issued to the various services. Instead, all
[all …]
DJOURNAL_FILE_FORMAT.md14 The systemd journal stores log data in a binary format with several features:
17 * Can store binary data, up to 2^64-1 in size
20 * Support for in-line compression
21 * Support for in-line Forward Secure Sealing
25 that the actual implementation in the [systemd
38 If you need access to the raw journal data in serialized stream form without C
45 _Or, to put this in other words: this low-level document is probably not what
58 in particular realize that they may include binary non-text data (though
63 format is compatible with the format used in the first versions of the journal,
66 If you are wondering why the journal file format has been created in the first
[all …]
DENVIRONMENT.md13 document them in the man pages and we make no stability guarantees for
19 documented in the proper man pages.
31 * `$SYSTEMD_IGNORE_CHROOT=1` — if set, don't check whether being invoked in a
34 refrains from talking to PID 1 in such a case; turning most operations such
42 line instead of the actual one in `/proc/cmdline`. This is useful for
43 debugging, in order to test generators and other code against specific kernel
66 * `$SYSTEMD_EFI_OPTIONS` — if set, used instead of the string in the
69 * `$SYSTEMD_DEFAULT_HOSTNAME` — override the compiled-in fallback hostname
70 (relevant in particular for the system manager and `systemd-hostnamed`).
76 on `/`. If both conditions meet, then it's in initrd.
[all …]
DPASSWORD_AGENTS.md10 …IX`/`SOCK_DGRAM` socket. Multiple agents might be running at the same time in which case they all …
13 * A console agent used in similar situations if Plymouth is not available
14 …phrase from the user. This is useful and necessary in case an encrypted system hard-disk is plugge…
22 * Ignore all events on files in that directory that do not start with "`ask.`"
24 * Make sure to ignore unknown `.ini` file keys in those files, so that we can easily extend the for…
25 …'ll find the question to ask the user in the `Message=` field in the `[Ask]` section. It is a sing…
26 …(following the XDG icon naming spec) to show next to the message in the `Icon=` field in the `[Ask…
27 * You'll find the PID of the client asking the question in the `PID=` field in the `[Ask]` section …
29 …the response to is configured via `Socket=` in the `[Ask]` section. It is a `AF_UNIX`/`SOCK_DGRAM`…
30 … files where the time specified in the `NotAfter=` field in the `[Ask]` section is in the past. Th…
[all …]
DCGROUP_DELEGATION.md21 comprehensive up-to-date information about all this, particular in light of the
28 This document then adds in the higher-level view from systemd.
37 with cgroups and systemd, in particular as they shine more light on the various
47 1. The **no-processes-in-inner-nodes** rule: this means that it's not permitted
53 both processes and children — which is used in particular to maintain kernel
64 your container manager creates and manages cgroups in the system's root cgroup
72 either cgroup v1 nor cgroup v2 (this is UNIX after all, in the general case
74 be in constant pain as various pieces of software will fight over cgroup
78 it's semantically broken in many ways, and in many cases doesn't actually do
80 kernel features in this area are only added to cgroup v2, and not cgroup v1
[all …]
DCODING_STYLE.md12 - 8ch indent, no tabs, except for files in `man/` which are 2ch indent, and
15 - We prefer `/* comments */` over `// comments` in code you commit,
24 `.dir-locals.el` files contained in the repository will set this limit up for
57 - Single-line `if` blocks should not be enclosed in `{}`. Write this:
115 - If you define an enum in a public API, be extra careful, as the size of the
119 `_SD_ENUM_FORCE_S64()` macro in the enum definition, which forces the size of
129 mode. (This discrepancy in particular means one thing: internally we use C99
131 have different size in memory and slightly different semantics, also see
134 fallback #ifdeffery in place to ensure compatibility is retained with older
137 - Please name structures in `PascalCase` (with exceptions, such as public API
[all …]
DHOME_DIRECTORY.md15 the format used by these home directories, in the context of the storage
21 user record of the user. It follows the format defined in
29 `secret` sections, i.e. only with the sections included in the signature plus
39 the user record in the `~/.identity` file.
44 is logged in, the directory is generally mounted to `/home/$USER` (in our
47 way in `/home/*.homedir` and synthesize NSS user records for them as they show
59 second field the encrypted volume key. The latter is encrypted using AES256 in
72 the CIFS service. The directory share needs to contain the user record in
95 record, in the same serialization as in `~/.identity`, though encrypted. The
106 contains a second copy of the user record in the `~/.identity` file, like in
[all …]
DUSER_NAMES.md16 itself, following the principle of "Be conservative in what you send, be
17 liberal in what you accept". Also in the interest of interoperability systemd
31 user name. Interestingly no size limit is declared, i.e. in neither
33 string is a valid user name as well as a string of gigabytes in length.
60 Other operating systems enforce different rules; in this documentation we'll
79 to register a user or group in the system, for example a system user/group
90 this cannot correctly appear in `utmp`/`wtmp` and create ambiguity with login
92 appear in directory names, i.e. the home directory), thus MIN(256, 31, 255) =
106 components of the system, for example in
109 Relaxed syntax is also enforced by the `User=` setting in service unit files,
[all …]
DUIDS-GIDS.md13 Note that while in theory UIDs and GIDs are orthogonal concepts they really
14 aren't IRL. With that in mind, when we discuss UIDs below it should be assumed
15 that whatever we say about UIDs applies to GIDs in mostly the same way, and all
39 assignment to users in the user database.
52 Distributions generally split the available UID range in two:
74 means regular users may be stored in remote LDAP or NIS databases, but system
76 available during earliest boot, including in the initial RAM disk).
83 currently defined groups is found in this `sysusers.d` snippet:
84 [basic.conf](https://raw.githubusercontent.com/systemd/systemd/main/sysusers.d/basic.conf.in)
86 It's strongly recommended that downstream distributions include these groups in
[all …]
DTEMPORARY_DIRECTORIES.md19 2. Data that shall survive a boot cycle shouldn't be placed in `/tmp/`.
36 untrusted files. Hence: do not use guessable names in `/tmp/` or `/var/tmp/` —
64 view `/tmp/` and `/var/tmp/` look and behave like they normally do, but in
70 not available in environments where file system namespaces are prohibited, for
71 example in certain container environments. This option is hence an extra line
72 of defense, but should not be used as an excuse to rely on guessable names in
75 temporary files stored in it is substantially different from the case where
84 and directories stored in `/tmp/` and `/var/tmp/`. This means that files that
86 automatically removed in regular intervals. (This concept is not new to
88 `tmpwatch`.) By default files in `/tmp/` are cleaned up after 10 days, and
[all …]
/systemd-251/src/boot/efi/
Dsplash.c168 const UINT8 *in; in bmp_to_blt() local
176 in = pixmap; in bmp_to_blt()
182 for (UINTN x = 0; x < dib->x; x++, in++, out++) { in bmp_to_blt()
186 out->Red = map[((*in) >> (7 - i)) & 1].red; in bmp_to_blt()
187 out->Green = map[((*in) >> (7 - i)) & 1].green; in bmp_to_blt()
188 out->Blue = map[((*in) >> (7 - i)) & 1].blue; in bmp_to_blt()
200 i = (*in) >> 4; in bmp_to_blt()
207 i = (*in) & 0x0f; in bmp_to_blt()
216 out->Red = map[*in].red; in bmp_to_blt()
217 out->Green = map[*in].green; in bmp_to_blt()
[all …]
/systemd-251/po/
Dtr.po23 #: src/core/org.freedesktop.systemd1.policy.in:22
27 #: src/core/org.freedesktop.systemd1.policy.in:23
32 #: src/core/org.freedesktop.systemd1.policy.in:33
36 #: src/core/org.freedesktop.systemd1.policy.in:34
42 #: src/core/org.freedesktop.systemd1.policy.in:43
46 #: src/core/org.freedesktop.systemd1.policy.in:44
52 #: src/core/org.freedesktop.systemd1.policy.in:54
56 #: src/core/org.freedesktop.systemd1.policy.in:55
64 #: src/core/org.freedesktop.systemd1.policy.in:64
68 #: src/core/org.freedesktop.systemd1.policy.in:65
[all …]
Dnl.po20 #: src/core/org.freedesktop.systemd1.policy.in:22
24 #: src/core/org.freedesktop.systemd1.policy.in:23
31 #: src/core/org.freedesktop.systemd1.policy.in:33
35 #: src/core/org.freedesktop.systemd1.policy.in:34
41 #: src/core/org.freedesktop.systemd1.policy.in:43
45 #: src/core/org.freedesktop.systemd1.policy.in:44
51 #: src/core/org.freedesktop.systemd1.policy.in:54
53 msgstr "Stel omgevingsvariabelen in voor systeem en dienstenbeheerder"
55 #: src/core/org.freedesktop.systemd1.policy.in:55
63 #: src/core/org.freedesktop.systemd1.policy.in:64
[all …]
/systemd-251/
DTODO13 * Fedora: add an rpmlint check that verifies that all unit files in the RPM are listed in %systemd_…
17 - teach dbus to activate all services it finds in /etc/systemd/services/org-*.service
83 can safely put privileged stuff in. Would not be writable by the user, but
84 still conceptually belong to the user. Would be included in user's quota if
96 * given that /etc/ssh/ssh_config.d/ is a thing now, ship a drop-in for that
99 * allow embedding a signature blob for PCR hashes into separate section in
101 passed in a file to the booted kernel (via initrd cpio, as usual). Usecase:
111 are stored in PE sections of their own too. Building a unified kernel would
127 * maybe add support for binding and connecting AF_UNIX sockets in the file
130 to target dir in /tmp, and bind through it.
[all …]
DREADME30 LGPL-2.1-or-later for all code, exceptions noted in LICENSES/README.md
35 ≥ 4.5 for pids controller in cgroup v2
37 ≥ 4.9 for RENAME_NOREPLACE support in vfat
39 ≥ 4.15 for cgroup-bpf device hook and cpu controller in cgroup v2
42 ≥ 5.3 for bounded loops in BPF program
46 Kernel versions below 4.15 have significant gaps in functionality and
58 CONFIG_UNIX (it requires CONFIG_NET, but every other flag in it is not necessary)
74 Userspace firmware loading is not supported and should be disabled in
82 additional symlinks in /dev/disk/ and /dev/tape:
85 Required for PrivateNetwork= in service units:
[all …]
DNEWS14 routes to addresses specified in AllowedIPs= was added and enabled by
15 default. However, this causes network connectivity issues in many
18 configuring RouteTable= setting in .netdev files.
56 to PCR 12 for this purpose in the long run, as we intend to remove
57 this compatibility feature in two year's time.
59 * busctl capture now writes output in the newer pcapng format instead
63 lowercase hexadecimal vendor/product ID digits was added in systemd
70 * arch_prctl(2) has been moved to the @default set in the syscall filters
71 (as exposed via the SystemCallFilter= setting in service unit files).
85 Changes in the Boot Loader Specification, kernel-install and sd-boot:
[all …]

12345678910>>...18