| /freebsd/sys/contrib/device-tree/Bindings/arm/ |
| H A D | secure.txt | 1 * ARM Secure world bindings
4 "Normal" and "Secure". Most devicetree consumers (including the Linux
6 world or the Secure world. However some devicetree consumers are
8 visible only in the Secure address space, only in the Normal address
10 virtual machine which boots Secure firmware and wants to tell the
13 The general principle of the naming scheme for Secure world bindings
14 is that any property that needs a different value in the Secure world
15 can be supported by prefixing the property name with "secure-". So for
16 instance "secure-foo" would override "foo". For property names with
17 a vendor prefix, the Secure variant of "vendor,foo" would be
[all …]
|
| /freebsd/targets/pseudo/userland/secure/ |
| H A D | Makefile.depend | 4 secure/lib/libcrypto \
5 secure/lib/libcrypto/engines/lib4758cca \
6 secure/lib/libcrypto/engines/libaep \
7 secure/lib/libcrypto/engines/libatalla \
8 secure/lib/libcrypto/engines/libcapi \
9 secure/lib/libcrypto/engines/libchil \
10 secure/lib/libcrypto/engines/libcswift \
11 secure/lib/libcrypto/engines/libgost \
12 secure/lib/libcrypto/engines/libnuron \
13 secure/lib/libcrypto/engines/libsureware \
[all …]
|
| /freebsd/sbin/init/ |
| H A D | ttys | 19 # the specified port. If the word "secure" appears, this tty
26 console none unknown off secure
28 ttyv0 "/usr/libexec/getty Pc" xterm onifexists secure
30 ttyv1 "/usr/libexec/getty Pc" xterm onifexists secure
31 ttyv2 "/usr/libexec/getty Pc" xterm onifexists secure
32 ttyv3 "/usr/libexec/getty Pc" xterm onifexists secure
33 ttyv4 "/usr/libexec/getty Pc" xterm onifexists secure
34 ttyv5 "/usr/libexec/getty Pc" xterm onifexists secure
35 ttyv6 "/usr/libexec/getty Pc" xterm onifexists secure
36 ttyv7 "/usr/libexec/getty Pc" xterm onifexists secure
[all …]
|
| /freebsd/tools/tools/nanobsd/pcengines/Files/etc/ |
| H A D | ttys | 22 # the specified port. If the word "secure" appears, this tty
29 console none unknown off secure
31 ttyv0 "/usr/libexec/getty Pc" xterm off secure
33 ttyv1 "/usr/libexec/getty Pc" xterm off secure
34 ttyv2 "/usr/libexec/getty Pc" xterm off secure
35 ttyv3 "/usr/libexec/getty Pc" xterm off secure
36 ttyv4 "/usr/libexec/getty Pc" xterm off secure
37 ttyv5 "/usr/libexec/getty Pc" xterm off secure
38 ttyv6 "/usr/libexec/getty Pc" xterm off secure
39 ttyv7 "/usr/libexec/getty Pc" xterm off secure
[all …]
|
| /freebsd/tools/tools/nanobsd/rescue/Files/etc/ |
| H A D | ttys | 22 # the specified port. If the word "secure" appears, this tty
29 console none unknown off secure
31 ttyv0 "/usr/libexec/getty Pc" xterm on secure
33 ttyv1 "/usr/libexec/getty Pc" xterm on secure
34 ttyv2 "/usr/libexec/getty Pc" xterm on secure
35 ttyv3 "/usr/libexec/getty Pc" xterm off secure
36 ttyv4 "/usr/libexec/getty Pc" xterm off secure
37 ttyv5 "/usr/libexec/getty Pc" xterm off secure
38 ttyv6 "/usr/libexec/getty Pc" xterm off secure
39 ttyv7 "/usr/libexec/getty Pc" xterm off secure
[all …]
|
| /freebsd/crypto/openssl/test/ |
| H A D | secmemtest.c | 21 TEST_info("Secure memory is implemented."); in test_sec_mem()
24 /* s = non-secure 20 */ in test_sec_mem()
29 /* r = non-secure 20, s = non-secure 20 */ in test_sec_mem()
36 /* r = non-secure 20, p = secure 20, s = non-secure 20 */ in test_sec_mem()
38 /* 20 secure -> 32-byte minimum allocation unit */ in test_sec_mem()
44 /* r = non-secure 20, p = secure 20, q = non-secure 20, s = non-secure 20 */ in test_sec_mem()
50 /* r = non-secure 20, p = secure 20, q = non-secure 20, s = secure 20 */ in test_sec_mem()
52 /* 2 * 20 secure -> 64 bytes allocated */ in test_sec_mem()
57 /* 20 secure -> 32 bytes allocated */ in test_sec_mem()
62 /* should not complete, as secure memory is still allocated */ in test_sec_mem()
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/amlogic/ |
| H A D | amlogic,meson-gx-ao-secure.yaml | 5 $id: http://devicetree.org/schemas/arm/amlogic/amlogic,meson-gx-ao-secure.yaml#
15 secure firmware.
22 const: amlogic,meson-gx-ao-secure
30 - const: amlogic,meson-gx-ao-secure
34 - amlogic,a4-ao-secure
35 - amlogic,c3-ao-secure
36 - amlogic,s4-ao-secure
37 - amlogic,t7-ao-secure
38 - const: amlogic,meson-gx-ao-secure
58 ao-secure@140 {
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/crypto/ |
| H A D | inside-secure-safexcel.txt | 1 Inside Secure SafeXcel cryptographic engine
4 - compatible: Should be "inside-secure,safexcel-eip197b",
5 "inside-secure,safexcel-eip197d" or
6 "inside-secure,safexcel-eip97ies".
21 - "inside-secure,safexcel-eip197" is equivalent to
22 "inside-secure,safexcel-eip197b".
23 - "inside-secure,safexcel-eip97" is equivalent to
24 "inside-secure,safexcel-eip97ies".
29 compatible = "inside-secure,safexcel-eip197b";
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | OPENSSL_secure_malloc.pod | 11 CRYPTO_secure_used - secure heap storage
45 information might be stored, OpenSSL supports the concept of a "secure heap."
50 If a secure heap is used, then private key B<BIGNUM> values are stored there.
54 CRYPTO_secure_malloc_init() creates the secure heap, with the specified
61 CRYPTO_secure_malloc_initialized() indicates whether or not the secure
65 to the process if all secure memory has been freed.
90 the memory if it was not allocated from the secure heap.
97 requested, in order to "round up" and reduce secure heap fragmentation.
99 OPENSSL_secure_allocated() tells if a pointer is allocated in the secure heap.
102 secure heap.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/iommu/ |
| H A D | qcom,iommu.txt | 6 to non-secure vs secure interrupt line.
32 - qcom,iommu-secure-id : secure-id.
38 - "qcom,msm-iommu-v1-ns" : non-secure context bank
39 - "qcom,msm-iommu-v1-sec" : secure context bank
47 for routing of context bank irq's to secure vs non-
48 secure lines. (Ie. if the iommu contains secure
64 qcom,iommu-secure-id = <17>;
90 qcom,iommu-secure-id = <18>;
|
| /freebsd/usr.sbin/bsdconfig/security/include/ |
| H A D | messages.subr | 33 msg_highly_secure="Highly Secure"
34 msg_highly_secure_mode="Highly secure mode"
36 msg_network_secure="Network Secure"
37 msg_network_secure_mode="Network secure mode"
41 msg_secure="Secure"
42 msg_secure_mode="Secure mode"
45 …secure mode system flags may not be overridden by the root user,\naccess to direct kernel memory i…
|
| H A D | securelevel.hlp | 15 1 Secure mode - the system immutable and system append-only
21 2 Highly secure mode - same as secure mode, plus disks may not
32 3 Network secure mode - same as highly secure mode, plus IP
|
| /freebsd/crypto/openssl/crypto/ |
| H A D | param_build.c | 27 int secure; member
53 int secure) in param_push() argument
65 if ((pd->secure = secure) != 0) in param_push()
203 int n, secure = 0; in OSSL_PARAM_BLD_push_BN_pad() local
223 secure = 1; in OSSL_PARAM_BLD_push_BN_pad()
229 pd = param_push(bld, key, sz, sz, OSSL_PARAM_UNSIGNED_INTEGER, secure); in OSSL_PARAM_BLD_push_BN_pad()
240 int secure; in OSSL_PARAM_BLD_push_utf8_string() local
248 secure = CRYPTO_secure_allocated(buf); in OSSL_PARAM_BLD_push_utf8_string()
249 pd = param_push(bld, key, bsize, bsize + 1, OSSL_PARAM_UTF8_STRING, secure); in OSSL_PARAM_BLD_push_utf8_string()
278 int secure; in OSSL_PARAM_BLD_push_octet_string() local
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mailbox/ |
| H A D | ti,secure-proxy.yaml | 4 $id: http://devicetree.org/schemas/mailbox/ti,secure-proxy.yaml#
7 title: Texas Instruments' Secure Proxy
13 The Texas Instruments' secure proxy is a mailbox controller that has
25 const: ti,am654-secure-proxy
30 Contains the secure proxy thread ID used for the specific transfer path.
48 secure proxy thread in the form 'rx_<PID>'.
54 Contains the interrupt information for the Rx interrupt path for secure
71 compatible = "ti,am654-secure-proxy";
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | OPENSSL_secure_malloc.3 | 146 CRYPTO_secure_used \- secure heap storage
180 information might be stored, OpenSSL supports the concept of a \*(L"secure heap.\*(R"
185 If a secure heap is used, then private key \fB\s-1BIGNUM\s0\fR values are stored there.
189 \&\fBCRYPTO_secure_malloc_init()\fR creates the secure heap, with the specified
196 \&\fBCRYPTO_secure_malloc_initialized()\fR indicates whether or not the secure
200 to the process if all secure memory has been freed.
224 the memory if it was not allocated from the secure heap.
230 requested, in order to \*(L"round up\*(R" and reduce secure heap fragmentation.
232 \&\fBOPENSSL_secure_allocated()\fR tells if a pointer is allocated in the secure heap.
235 secure heap.
[all …]
|
| /freebsd/crypto/heimdal/lib/krb5/ |
| H A D | verify_user.c | 41 krb5_boolean secure, in verify_common() argument
56 krb5_verify_init_creds_opt_set_ap_req_nofail(&vopt, secure); in verify_common()
86 * If `secure', also verify against local service key for `service'.
95 opt->secure = TRUE; in krb5_verify_opt_init()
131 krb5_verify_opt_set_secure(krb5_verify_opt *opt, krb5_boolean secure) in krb5_verify_opt_set_secure() argument
133 opt->secure = secure; in krb5_verify_opt_set_secure()
179 OPT(keytab, NULL), vopt ? vopt->secure : TRUE, in verify_user_opt_int()
223 krb5_boolean secure, in krb5_verify_user() argument
231 krb5_verify_opt_set_secure(&opt, secure); in krb5_verify_user()
247 krb5_boolean secure, in krb5_verify_user_lrealm() argument
[all …]
|
| /freebsd/contrib/unbound/contrib/ |
| H A D | update-anchor.sh | 75 if grep '(secure)$' $tmpfile >/dev/null 2>&1; then
80 echo "Cause: result of lookup was not secure"
90 grep '(secure)$' $tmpfile | \
92 sed -e 's/ (secure)$/";/' | \
97 grep '(secure)$' $tmpfile | \
98 sed -e 's/ (secure)$/";/' | \
107 grep '(secure)$' $tmpfile | \
109 sed -e 's/ (secure)$//' | \
114 grep '(secure)$' $tmpfile | \
115 sed -e 's/ (secure)$//' | \
|
| /freebsd/crypto/openssl/include/crypto/ |
| H A D | rand_pool.h | 46 * There is a distinction between the secure and normal allocation minimums.
47 * Ideally, the secure allocation size should be a power of two. The normal
50 * The secure value is based on 128 bits of secure material, which is 16 bytes.
60 # define RAND_POOL_MIN_ALLOCATION(secure) ((secure) ? 16 : 48) argument
76 int secure; /* 1: allocated on the secure heap, 0: otherwise */ member
85 RAND_POOL *ossl_rand_pool_new(int entropy_requested, int secure,
|
| /freebsd/crypto/openssl/ |
| H A D | FREEBSD-upgrade | 71 secure/lib/libcrypto/Makefile.inc and
82 $ cd secure/lib/libcrypto
103 $ find openssl-X.Y.Z/doc/man/man1 -name '*.1' -exec cp {} secure/usr.bin/openssl/man/ \;
104 $ find openssl-X.Y.Z/doc/man/man3 -name '*.3' -exec cp {} secure/lib/libcrypto/man/man3/ \;
105 $ find openssl-X.Y.Z/doc/man/man5 -name '*.5' -exec cp {} secure/lib/libcrypto/man/man5/ \;
106 $ find openssl-X.Y.Z/doc/man/man7 -name '*.7' -exec cp {} secure/lib/libcrypto/man/man7/ \;
107 $ grep -nrF usr/local secure/lib/libcrypto/man secure/usr.bin/openssl/man
109 $ git commit --amend secure/lib/libcrypto/man secure/usr.bin/openssl/man
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/samsung/ |
| H A D | samsung-secure-firmware.yaml | 4 $id: http://devicetree.org/schemas/arm/samsung/samsung-secure-firmware.yaml#
7 title: Samsung Exynos Secure Firmware
15 - const: samsung,secure-firmware
19 Address of non-secure SYSRAM used for communication with firmware.
31 compatible = "samsung,secure-firmware";
|
| /freebsd/sys/contrib/device-tree/Bindings/rng/ |
| H A D | omap_rng.txt | 1 OMAP SoC and Inside-Secure HWRNG Module
9 - "inside-secure,safexcel-eip76" for SoCs with EIP76 IP block
14 Used for "ti,omap4-rng" and "inside-secure,safexcel-eip76"
16 "inside-secure,safexcel-eip76" compatible, the second clock is
34 compatible = "inside-secure,safexcel-eip76";
|
| /freebsd/sys/contrib/device-tree/Bindings/firmware/meson/ |
| H A D | meson_sm.txt | 1 * Amlogic Secure Monitor
3 In the Amlogic SoCs the Secure Monitor code is used to provide access to the
6 Required properties for the secure monitor node:
12 sm: secure-monitor {
|
| /freebsd/sys/contrib/device-tree/Bindings/nvmem/ |
| H A D | st,stm32-romem.yaml | 40 st,non-secure-otp:
42 This property explicits a factory programmed area that both secure
43 and non-secure worlds can access. It is needed when, by default, the
44 related area can only be reached by the secure world.
69 st,non-secure-otp;
|
| /freebsd/include/rpcsvc/ |
| H A D | crypt.x | 38 * Secure RPC work. The normal way around this is to break the DES
40 * in the base OS and provide the real lib in the secure dist, which
41 * the user can install later. But we need Secure RPC for NIS+, and
44 * in the secure dist, but there are a lot, and this is a pain. The
51 * Secure NFS one day this will be worth it, but for now we should keep
56 * it to make Secure RPC work anyway) and we use this protocol to ship
|
| /freebsd/sys/contrib/device-tree/Bindings/firmware/ |
| H A D | intel,stratix10-svc.txt | 4 processor system (HPS) and Secure Device Manager (SDM). When the FPGA is
10 communication with SDM, only the secure world of software (EL3, Exception
18 driver also manages secure monitor call (SMC) to communicate with secure monitor
28 smc - Secure Monitor Call
|