| /freebsd/share/man/man9/ |
| H A D | vm_map_protect.9 | 36 .Nd apply protection bits to a virtual memory region
53 function sets the protection bits and maximum protection bits of the address
65 bit set, then the effective protection is set to
72 bit set, then the maximum protection is set to
74 Protection bits not included into
82 are not allowed to include any protection bits that are not set in existing
102 The specified protection bits were set successfully.
127 Both new protection and new maximum protection updates were requested,
|
| /freebsd/lib/libsys/x86/ |
| H A D | pkru.3 | 32 .Nm Protection Key Rights for User pages
52 The protection keys feature provides an additional mechanism, besides the
65 has an associated 4-bit protection key.
66 A new per-thread PKRU hardware register determines, for each protection
67 key, whether user-mode addresses with that protection key may be
71 The default protection key index is zero, it is used even if no key
74 The protection prevents the system from accessing user addresses as well
77 protection, it returns the
82 Protection keys require that the system uses 4-level paging
85 Both 64-bit and 32-bit applications can use protection keys.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/regulator/ |
| H A D | regulator.yaml | 122 regulator-over-current-protection:
123 description: Enable over current protection.
126 regulator-oc-protection-microamp:
127 description: Set over current protection limit. This is a limit where
129 protection and value '1' indicates that protection should be enabled but
145 regulator-ov-protection-microvolt:
146 description: Set over voltage protection limit. This is a limit where
148 protection and value '1' indicates that protection shoul
[all...] |
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_CTX_set_tlsext_use_srtp.pod | 37 SRTP protection profile names.
39 The currently supported protection profile names are:
61 Supplying an unrecognised protection profile name will result in an error.
65 protection profiles that it is willing to negotiate.
67 The currently configured list of protection profiles for either a client or a
72 After a handshake has been completed the negotiated SRTP protection profile (if
75 protection profile was negotiated. The memory returned from this function should
78 If an SRTP protection profile has been successfully negotiated then the SRTP
83 master key length and the salt length as defined for the protection profile in
93 success or NULL on error or if no protection profiles have been configured.
|
| H A D | SSL_read_early_data.pod | 69 additional considerations around replay attacks (see L</REPLAY PROTECTION>
206 early data setting for a server is nonzero then replay protection is
207 automatically enabled (see L</REPLAY PROTECTION> below).
231 is accepted or not, for example to mitigate replay risks (see L</REPLAY PROTECTION>
240 protection feature will still be used even if a callback is present unless it
242 L</REPLAY PROTECTION> below.
284 =head1 REPLAY PROTECTION
288 mitigation for this issue OpenSSL automatically enables replay protection if the
290 protection enabled sessions are forced to be single use only. If a client
296 The replay protection mechanism relies on the internal OpenSSL server session
[all …]
|
| /freebsd/crypto/openssl/crypto/cmp/ |
| H A D | cmp_protect.c | 24 * Calculate protection for given PKImessage according to
28 * returns ASN1_BIT_STRING representing the protection on success, else NULL
57 unsigned char *protection = NULL; in ossl_cmp_calc_protection() local
89 &protection, &sig_len)) in ossl_cmp_calc_protection()
97 if (!ASN1_BIT_STRING_set(prot, protection, sig_len)) { in ossl_cmp_calc_protection()
103 OPENSSL_free(protection); in ossl_cmp_calc_protection()
138 /* Add first ctx->cert and its chain if using signature-based protection */ in ossl_cmp_msg_add_extraCerts()
185 * Create an X509_ALGOR structure for PasswordBasedMAC protection based on
262 * For the case of re-protection remove pre-existing protection. in ossl_cmp_msg_protect()
266 ASN1_BIT_STRING_free(msg->protection); in ossl_cmp_msg_protect()
[all …]
|
| H A D | cmp_vfy.c | 55 msg->header->protectionAlg, msg->protection, in verify_signature()
79 ASN1_BIT_STRING *protection = NULL; in verify_PBMAC() local
82 /* generate expected protection for the message */ in verify_PBMAC()
83 if ((protection = ossl_cmp_calc_protection(ctx, msg)) == NULL) in verify_PBMAC()
84 return 0; /* failed to generate protection string! */ in verify_PBMAC()
86 valid = msg->protection != NULL && msg->protection->length >= 0 in verify_PBMAC()
87 && msg->protection->type == protection->type in verify_PBMAC()
88 && msg->protection->length == protection->length in verify_PBMAC()
89 && CRYPTO_memcmp(msg->protection->data, protection->data, in verify_PBMAC()
90 protection->length) == 0; in verify_PBMAC()
[all …]
|
| /freebsd/contrib/netbsd-tests/lib/libc/common/ |
| H A D | exec_prot.h | 47 * MD callback to verify whether host offers executable space protection.
48 * Returns execute protection level.
52 /* execute protection level */
55 NO_XP, /* no execute protection */
56 PERPAGE_XP, /* per-page execute protection */
57 PARTIAL_XP /* partial execute protection. Depending on where the
59 protection may be enforced or not. */
|
| /freebsd/share/man/man7/ |
| H A D | mitigations.7 | 54 Write XOR Execute page protection policy
62 Stack Overflow Protection
64 Supervisor Mode Memory Protection
161 .Ss Write XOR Execute page protection policy
193 provides the ability to set the maximum protection of a region allocated by
243 .Ss Stack Overflow Protection
245 supports stack overflow protection using the Stack Smashing Protector
248 Stack clash protection is also enabled,
273 .Fl fstack-clash-protection
324 This effectively provides finer-grained protection tha
[all...] |
| /freebsd/sys/sys/ |
| H A D | cfictl.h | 47 /* Intel StrataFlash Protection Register support */
48 #define CFIOCGFACTORYPR _IOR('q', 1, uint64_t) /* get factory protection reg */
49 #define CFIOCGOEMPR _IOR('q', 2, uint64_t) /* get oem protection reg */
50 #define CFIOCSOEMPR _IOW('q', 3, uint64_t) /* set oem protection reg */
51 #define CFIOCGPLR _IOR('q', 4, uint32_t) /* get protection lock reg */
52 #define CFIOCSPLR _IO('q', 5) /* set protection log reg */
|
| /freebsd/sys/contrib/device-tree/Bindings/soc/qcom/ |
| H A D | qcom,apr.txt | 48 - qcom,protection-domain
51 Definition: Must list the protection domain service name and path
99 The following example represents a QDSP based sound card with protection domain
101 running on protection domain hosted on ADSP/SLPI remote processors while others
117 qcom,protection-domain = "avs/audio", "msm/adsp/audio_pd";
124 qcom,protection-domain = "tms/servreg", "msm/slpi/sensor_pd";
131 qcom,protection-domain = "avs/audio", "msm/adsp/audio_pd";
|
| /freebsd/crypto/openssl/test/ |
| H A D | cmp_protect_test.c | 21 /* for protection tests */
78 ASN1_BIT_STRING *protection = in execute_calc_protection_fails_test() local
80 int res = TEST_ptr_null(protection); in execute_calc_protection_fails_test()
82 ASN1_BIT_STRING_free(protection); in execute_calc_protection_fails_test()
88 ASN1_BIT_STRING *protection = in execute_calc_protection_pbmac_test() local
90 int res = TEST_ptr(protection) in execute_calc_protection_pbmac_test()
91 && TEST_true(ASN1_STRING_cmp(protection, in execute_calc_protection_pbmac_test()
92 fixture->msg->protection) == 0); in execute_calc_protection_pbmac_test()
94 ASN1_BIT_STRING_free(protection); in execute_calc_protection_pbmac_test()
103 ASN1_BIT_STRING *protection, in verify_signature() argument
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | sa.4 | 291 .It protection.protection_supported
293 protection information.
294 .It protection.prot_method
295 If protection is supported, set this to the desired protection method
297 As of SSC-5r03 (available at t10.org), the protection method values are:
300 No protection.
306 .It protection.pi_length
307 Length of the protection information, see above for lengths.
308 .It protection.lbp_w
309 If set to 1, enable logical block protection on writes.
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_CTX_set_tlsext_use_srtp.3 | 172 \&\s-1SRTP\s0 protection profile names.
174 The currently supported protection profile names are:
188 Supplying an unrecognised protection profile name will result in an error.
192 protection profiles that it is willing to negotiate.
194 The currently configured list of protection profiles for either a client or a
199 After a handshake has been completed the negotiated \s-1SRTP\s0 protection profile (if
202 protection profile was negotiated. The memory returned from this function should
205 If an \s-1SRTP\s0 protection profile has been successfully negotiated then the \s-1SRTP\s0
210 master key length and the salt length as defined for the protection profile in
219 success or \s-1NULL\s0 on error or if no protection profiles have been configured.
|
| H A D | SSL_read_early_data.3 | 204 additional considerations around replay attacks (see \*(L"\s-1REPLAY PROTECTION\*(R"\s0
334 early data setting for a server is nonzero then replay protection is
335 automatically enabled (see \*(L"\s-1REPLAY PROTECTION\*(R"\s0 below).
359 is accepted or not, for example to mitigate replay risks (see \*(L"\s-1REPLAY PROTECTION\*(R"\s0
368 protection feature will still be used even if a callback is present unless it
370 \&\*(L"\s-1REPLAY PROTECTION\*(R"\s0 below.
410 .SH "REPLAY PROTECTION"
411 .IX Header "REPLAY PROTECTION"
414 mitigation for this issue OpenSSL automatically enables replay protection if the
416 protection enabled sessions are forced to be single use only. If a client
[all …]
|
| /freebsd/contrib/ofed/librdmacm/man/ |
| H A D | rdma_create_srq.3 | 16 Optional protection domain for the SRQ.
26 function, and the protection domain, if provided, must be for that same device.
29 If a protection domain is not given - pd parameter is NULL - then
30 the rdma_cm_id will be created using a default protection domain. One
31 default protection domain is allocated per RDMA device.
|
| H A D | rdma_create_qp.3 | 16 Optional protection domain for the QP.
27 function, and the protection domain must be for that same device.
33 If a protection domain is not given - pd parameter is NULL - then
34 the rdma_cm_id will be created using a default protection domain. One
35 default protection domain is allocated per RDMA device.
|
| /freebsd/sys/contrib/dev/iwlwifi/fw/api/ |
| H A D | time-event.h | 398 * enum iwl_mvm_session_prot_conf_id - session protection's configurations
399 * @SESSION_PROTECT_CONF_ASSOC: Start a session protection for association.
415 * Only the duration is configurable for this protection.
436 * struct iwl_mvm_session_prot_cmd - configure a session protection
438 * for which this session protection is sent
442 * @duration_tu: the duration of the whole protection in TUs.
446 * Note: the session protection will always be scheduled to start as
448 * The firmware supports only one concurrent session protection per vif.
449 * Adding a new session protection will remove any currently running session.
465 * struct iwl_mvm_session_prot_notif - session protection starte
[all...] |
| /freebsd/crypto/openssl/doc/internal/man3/ |
| H A D | ossl_cmp_msg_protect.pod | 8 - functions for producing CMP message protection
21 ossl_cmp_calc_protection() calculates the protection for the given I<msg>
27 If there is a secretValue it selects PBMAC, else if there is a protection cert
32 If signature-based message protection is used it adds first the CMP signer cert
49 ossl_cmp_calc_protection() returns the protection on success, else NULL.
|
| H A D | ossl_cmp_msg_check_update.pod | 33 =item its protection is present and valid (or a callback function B<cb>
34 is present and indicates that a missing or invalid protection is acceptable),
46 In case no protection is present and B<cb> is not NULL then this callback
48 case an invalid protection is present the B<invalid_protection> parameter is 1.
67 Moreover, according to RFC 4210 section 5.3.2, if the message protection is
|
| /freebsd/lib/libsys/ |
| H A D | mprotect.2 | 33 .Nd control the protection of pages
44 changes the specified pages to have protection
65 In addition to these standard protection flags,
70 provides the ability to set the maximum protection of a region
92 the protection to the value specified by
|
| /freebsd/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | rohm,bd96801-pmic.yaml | 102 regulator-temp-protection-kelvin = <1>;
113 regulator-temp-protection-kelvin = <1>;
124 regulator-temp-protection-kelvin = <1>;
135 regulator-temp-protection-kelvin = <1>;
146 regulator-temp-protection-kelvin = <1>;
157 regulator-temp-protection-kelvin = <1>;
168 regulator-temp-protection-kelvin = <1>;
|
| H A D | as3711.txt | 30 and one of these to select the over-voltage protection pin
31 - su2-fbprot-lx-sd4 : LX_SD4 is used for over-voltage protection
32 - su2-fbprot-gpio2 : GPIO2 is used for over-voltage protection
33 - su2-fbprot-gpio3 : GPIO3 is used for over-voltage protection
34 - su2-fbprot-gpio4 : GPIO4 is used for over-voltage protection
|
| /freebsd/contrib/llvm-project/compiler-rt/lib/sanitizer_common/ |
| H A D | sanitizer_procmaps.h | 31 // Memory protection masks.
45 bool IsReadable() const { return protection & kProtectionRead; } in IsReadable()
46 bool IsWritable() const { return protection & kProtectionWrite; } in IsWritable()
47 bool IsExecutable() const { return protection & kProtectionExecute; } in IsExecutable()
48 bool IsShared() const { return protection & kProtectionShared; } in IsShared()
57 uptr protection; variable
|
| /freebsd/sys/contrib/dev/iwlwifi/mvm/ |
| H A D | time-event.h | 62 * iwl_mvm_protect_session - start / extend the session protection.
72 * This function can be used to start a session protection which means that the
85 * iwl_mvm_stop_session_protection - cancel the session protection.
89 * This functions cancels the session protection which is an act of good
203 * iwl_mvm_schedule_session_protection - schedule a session protection
205 * @vif: the virtual interface for which the protection issued
206 * @duration: the requested duration of the protection
207 * @min_duration: the minimum duration of the protection
208 * @wait_for_notif: if true, will block until the start of the protection
209 * @link_id: The link to schedule a session protection fo
[all...] |