Home
last modified time | relevance | path

Searched refs:trust (Results 1 – 16 of 16) sorted by relevance

/systemd-251/src/journal-remote/
Djournal-remote-main.c370 const char *trust) { in setup_microhttpd_server() argument
422 if (trust) in setup_microhttpd_server()
424 {MHD_OPTION_HTTPS_MEM_TRUST, 0, (char*) trust}; in setup_microhttpd_server()
513 const char *trust) { in setup_microhttpd_socket() argument
520 return setup_microhttpd_server(s, fd, key, cert, trust); in setup_microhttpd_socket()
596 const char* trust) { in create_remoteserver() argument
630 r = setup_microhttpd_server(s, fd, key, cert, trust); in create_remoteserver()
703 r = setup_microhttpd_socket(s, arg_listen_https, key, cert, trust); in create_remoteserver()
1064 static int load_certificates(char **key, char **cert, char **trust) { in load_certificates() argument
1092 trust, NULL); in load_certificates()
[all …]
/systemd-251/src/shared/
Dnetif-sriov.c25 .trust = -1, in sr_iov_new()
150 if (sr_iov->trust >= 0) { in sr_iov_set_netlink_message()
153 .setting = sr_iov->trust, in sr_iov_set_netlink_message()
539 sr_iov->trust = -1; in config_parse_sr_iov_boolean()
558 sr_iov->trust = r; in config_parse_sr_iov_boolean()
Dnetif-sriov.h30 int trust; member
/systemd-251/src/resolve/
Dresolv.conf18 options edns0 trust-ad
Dmeson.build46 'resolved-dns-trust-anchor.c',
47 'resolved-dns-trust-anchor.h',
/systemd-251/catalog/
Dsystemd.ru.catalog.in357 # Subject: A DNSSEC trust anchor has been revoked
364 Открытый ключ (trust ahcnor) DNSSEC был отозван. Необходимо настроить новый
Dsystemd.it.catalog.in345 # Subject: A DNSSEC trust anchor has been revoked
347 Subject: Un trust anchor DNSSEC è stato revocato
352 Un trust anchor DNSSEC è stato revocato. Un nuovo punto di fiducia è stato
Dsystemd.catalog.in341 Subject: A DNSSEC trust anchor has been revoked
346 A DNSSEC trust anchor has been revoked. A new trust anchor has to be
348 DNSSEC trust anchor.
/systemd-251/docs/
DHOME_DIRECTORY.md134 establishing a minimal level of trust. Since the user record data is
136 key are not accepted, a minimal level of trust between the system and the home
DUSER_RECORD.md916 which ones shall not. A minimal level of trust must be established between
919 encapsulated file system it is essential this trust is established before the
928 usage and not allow them to use more. The requirement of being able to trust
933 Note that other mechanisms for establishing sufficient trust exist too, and are
937 exist outside of the local trusted system, hence transfer and trust in the
/systemd-251/shell-completion/bash/
Dresolvectl39 --trust-anchor=no --network=no --service-address=no
/systemd-251/man/rules/
Dmeson.build15 ['dnssec-trust-anchors.d',
/systemd-251/
DTODO117 * a new tool "systemd-trust" or so, that can calculate PCR hashes offline, and
124 The systemd-trust tool should then be able to resolve any "underspecifed"
705 - p11-kit-trust (always)
DNEWS805 trust as SHA256 banks.
2303 --trust-anchor=, --validate= that take booleans and may be used to
2306 through the network, the local mDNS/LLMNR zone, the DNSSEC trust
7372 implement a complete UEFI SecureBoot trust chain, involving a signed
/systemd-251/hwdb.d/
Dpci.ids21425 c070 u.trust Anchor Hardware Security Module cs7.2 Series
21426 c071 u.trust Anchor Hardware Security Module cs7.3 Series
21427 c072 u.trust Anchor Hardware Security Module cs7.3 Series Virtual Function
D20-pci-vendor-model.hwdb63339 ID_MODEL_FROM_DATABASE=u.trust Anchor Hardware Security Module cs7.2 Series
63342 ID_MODEL_FROM_DATABASE=u.trust Anchor Hardware Security Module cs7.3 Series
63345 ID_MODEL_FROM_DATABASE=u.trust Anchor Hardware Security Module cs7.3 Series Virtual Function