/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: 93 Supplying an unrecognised protection profile name will result in an error. 97 protection profiles that it is willing to negotiate. 99 The currently configured list of protection profiles for either a client or a 104 After a handshake has been completed the negotiated SRTP protection profile (if 107 protection profile was negotiated. The memory returned from this function should 110 If an SRTP protection profile has been successfully negotiated then the SRTP 115 master key length and the salt length as defined for the protection profile in 129 success or NULL on error or if no protection profiles have been configured.
|
/freebsd/crypto/openssl/crypto/cmp/ |
H A D | cmp_protect.c | 25 * Calculate protection for |msg| according to |msg->header->protectionAlg| 31 * returns ASN1_BIT_STRING representing the protection on success, else NULL 60 unsigned char *protection = NULL; in ossl_cmp_calc_protection() local 92 &protection, &sig_len)) in ossl_cmp_calc_protection() 99 if (!ASN1_BIT_STRING_set(prot, protection, sig_len)) { in ossl_cmp_calc_protection() 105 OPENSSL_free(protection); in ossl_cmp_calc_protection() 158 /* Add first ctx->cert and its chain if using signature-based protection */ in ossl_cmp_msg_add_extraCerts() 190 * Create an X509_ALGOR structure for PasswordBasedMAC protection based on 239 * For the case of re-protection remove pre-existing protection. in ossl_cmp_msg_protect() 244 ASN1_BIT_STRING_free(msg->protection); in ossl_cmp_msg_protect() [all …]
|
H A D | cmp_vfy.c | 56 msg->header->protectionAlg, msg->protection, in verify_signature() 80 ASN1_BIT_STRING *protection = NULL; in verify_PBMAC() local 83 /* generate expected protection for the message */ in verify_PBMAC() 84 if ((protection = ossl_cmp_calc_protection(ctx, msg)) == NULL) in verify_PBMAC() 85 return 0; /* failed to generate protection string! */ in verify_PBMAC() 87 valid = msg->protection != NULL && msg->protection->length >= 0 in verify_PBMAC() 88 && msg->protection->type == protection->type in verify_PBMAC() 89 && msg->protection->length == protection->length in verify_PBMAC() 90 && CRYPTO_memcmp(msg->protection->data, protection->data, in verify_PBMAC() 91 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/secure/lib/libcrypto/man/man3/ |
H A D | SSL_CTX_set_tlsext_use_srtp.3 | 96 SRTP protection profile names. 98 The currently supported protection profile names are: 136 Supplying an unrecognised protection profile name will result in an error. 140 protection profiles that it is willing to negotiate. 142 The currently configured list of protection profiles for either a client or a 147 After a handshake has been completed the negotiated SRTP protection profile (if 150 protection profile was negotiated. The memory returned from this function should 153 If an SRTP protection profile has been successfully negotiated then the SRTP 158 master key length and the salt length as defined for the protection profile in 171 success or NULL on error or if no protection profiles have been configured.
|
H A D | SSL_read_early_data.3 | 128 additional considerations around replay attacks (see "REPLAY PROTECTION" 258 early data setting for a server is nonzero then replay protection is 259 automatically enabled (see "REPLAY PROTECTION" below). 283 is accepted or not, for example to mitigate replay risks (see "REPLAY PROTECTION" 292 protection feature will still be used even if a callback is present unless it 294 "REPLAY PROTECTION" below. 339 .SH "REPLAY PROTECTION" 340 .IX Header "REPLAY PROTECTION" 343 mitigation for this issue OpenSSL automatically enables replay protection if the 345 protection enabled sessions are forced to be single use only. If a client [all …]
|
H A D | OSSL_CMP_CTX_new.3 | 339 for signature-based message protection and Proof-of-Possession (POPO). 341 …t algorithm to be used as one-way function (OWF) for MAC-based message protection with password-ba… 342 …t algorithm to be used as one-way function (OWF) for MAC-based message protection with password-ba… 344 .IP "\fBOSSL_CMP_OPT_MAC_ALGNID\fR The NID of the MAC algorithm to be used for message protection w… 345 .IX Item "OSSL_CMP_OPT_MAC_ALGNID The NID of the MAC algorithm to be used for message protection wi… 366 Send request or response messages without CMP-level protection. 370 unprotected or where protection verification failed. Applies to regular 379 validating signature-based protection in received CMP messages. 531 CMP protection certificates, and when verifying newly enrolled certificates. 540 also called \fIprotection certificate\fR, [all …]
|
/freebsd/share/mk/ |
H A D | bsd.suffixes-extra.mk | 21 … ${SHARED_CFLAGS:C/^-fstack-protector.*$//:C/^-fstack-clash-protection.*$//:C/^-fsanitize.*$//} \ 22 ${CFLAGS:C/^-fstack-protector.*$//:C/^-fstack-clash-protection.*$//:C/^-fsanitize.*$//} \ 39 … ${SHARED_CXXFLAGS:C/^-fstack-protector.*$//:C/^-fstack-clash-protection.*$//:C/^-fsanitize.*$//} \ 40 ${CXXFLAGS:C/^-fstack-protector.*$//:C/^-fstack-clash-protection.*$//:C/^-fsanitize.*$//} \ 53 ${FFLAGS:C/^-fstack-protector.*$//:C/^-fstack-clash-protection.*$//} \ 69 ${SHARED_CFLAGS:C/^-fstack-protector.*$//:C/^-fstack-clash-protection.*$//} \ 70 ${CFLAGS:C/^-fstack-protector.*$//:C/^-fstack-clash-protection.*$//} \ 89 ${SHARED_CFLAGS:C/^-fstack-protector.*$//:C/^-fstack-clash-protection.*$//} \ 90 ${CFLAGS:C/^-fstack-protector.*$//:C/^-fstack-clash-protection.*$//} \
|
/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/share/man/man4/ |
H A D | sa.4 | 289 .It protection.protection_supported 291 protection information. 292 .It protection.prot_method 293 If protection is supported, set this to the desired protection method 295 As of SSC-5r03 (available at t10.org), the protection method values are: 298 No protection. 304 .It protection.pi_length 305 Length of the protection information, see above for lengths. 306 .It protection.lbp_w 307 If set to 1, enable logical block protection on writes. [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/test/ |
H A D | cmp_protect_test.c | 22 /* for protection tests */ 82 ASN1_BIT_STRING *protection = in execute_calc_protection_fails_test() local 84 int res = TEST_ptr_null(protection); in execute_calc_protection_fails_test() 86 ASN1_BIT_STRING_free(protection); in execute_calc_protection_fails_test() 92 ASN1_BIT_STRING *protection = in execute_calc_protection_pbmac_test() local 94 int res = TEST_ptr(protection) in execute_calc_protection_pbmac_test() 95 && TEST_true(ASN1_STRING_cmp(protection, in execute_calc_protection_pbmac_test() 96 fixture->msg->protection) == 0); in execute_calc_protection_pbmac_test() 98 ASN1_BIT_STRING_free(protection); in execute_calc_protection_pbmac_test() 107 ASN1_BIT_STRING *protection, in verify_signature() argument [all …]
|
/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/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> 30 If there is a secretValue it selects PBMAC, else if there is a protection cert 35 If signature-based message protection is used it adds first the CMP signer cert 52 ossl_cmp_calc_protection() returns the protection on success, else NULL.
|
/freebsd/crypto/openssl/include/internal/ |
H A D | quic_wire_pkt.h | 150 * QUIC Packet Header Protection 153 * Functions to apply and remove QUIC packet header protection. A header 173 * The header protection cipher method to use. One of 203 * Removes header protection from a packet. The packet payload must currently be 204 * encrypted (i.e., you must remove header protection before decrypting packets 218 * Applies header protection to a packet. The packet payload must already have 219 * been encrypted (i.e., you must apply header protection after encrypting 231 * Removes header protection from a packet. The packet payload must currently 237 * protection mask. It is permissible to set sample_len to the size of the 258 * protection instead of removing it. [all …]
|