/freebsd/tests/sys/mac/bsdextended/ |
H A D | ugidfw_test.c | 78 /* Variations on subject and object uids. */ 79 "subject uid root object uid root mode n", 80 "subject uid root object uid daemon mode n", 81 "subject uid daemon object uid root mode n", 82 "subject uid daemon object uid daemon mode n", 84 "subject uid root object uid root mode a", 85 "subject uid root object uid root mode r", 86 "subject uid root object uid root mode s", 87 "subject uid root object uid root mode w", 88 "subject uid root object uid root mode x", [all …]
|
H A D | matches_test.sh | 112 atf_check -s exit:0 ugidfw set 1 subject uid $uidrange object mode rasx 113 # subject uid in range 117 # subject uid out range 135 atf_check -s exit:0 ugidfw set 1 subject gid $gidrange object mode rasx 137 # subject gid in range 141 # subject gid out range 160 # subject matching jailid 162 atf_check -s exit:0 ugidfw set 1 subject jailid $jailid object mode rasx 170 # subject nonmatching jailid 191 atf_check -s exit:0 ugidfw set 1 subject object uid $uidrange mode rasx [all …]
|
/freebsd/libexec/rc/ |
H A D | rc.bsdextended | 62 #${CMD} add subject uid 80 object not uid 80 mode rxws; 63 #${CMD} add subject gid 80 object not gid 80 mode rxws; 67 #${CMD} add subject uid 54 object not uid 54 mode rxws; 68 #${CMD} add subject gid 26 object gid 54 mode rxws; 72 ${CMD} add subject uid 0 object not uid 0 mode arxws; 73 ${CMD} add subject gid 0 object not gid 0 mode arxws; 77 #${CMD} add subject uid 54 object not uid 54 mode rxws; 78 #${CMD} add subject gid 54 object not gid 54 mode rxws; 82 ${CMD} add subject uid 3 object not uid 3 mode rxws; 83 ${CMD} add subject gid 7 object not gid 7 mode rxws; [all …]
|
/freebsd/crypto/openssl/test/ |
H A D | danetest.in | 22 # subject= CN = example.com 30 # subject= CN = Issuer CA 38 # subject= CN = Root CA 54 subject= 69 subject= 84 subject= 99 subject= 114 subject= 129 subject= 144 subject= [all …]
|
/freebsd/sys/contrib/openzfs/cmd/zed/zed.d/ |
H A D | zed-functions.sh | 172 # zed_notify (subject, pathname) 177 # subject: notification subject 187 local subject="$1" 192 zed_notify_email "${subject}" "${pathname}"; rv=$? 196 zed_notify_pushbullet "${subject}" "${pathname}"; rv=$? 200 zed_notify_slack_webhook "${subject}" "${pathname}"; rv=$? 204 zed_notify_pushover "${subject}" "${pathname}"; rv=$? 208 zed_notify_ntfy "${subject}" "${pathname}"; rv=$? 212 zed_notify_gotify "${subject}" "${pathname}"; rv=$? 222 # zed_notify_email (subject, pathname) [all …]
|
/freebsd/crypto/openssl/doc/man3/ |
H A D | X509V3_set_ctx.pod | 12 void X509V3_set_ctx(X509V3_CTX *ctx, X509 *issuer, X509 *subject, 21 Any of I<subject>, I<req>, or I<crl> may be provided, pointing to a certificate, 23 When constructing the subject key identifier of a certificate by computing a 24 hash value of its public key, the public key is taken from I<subject> or I<req>. 25 Similarly, when constructing subject alternative names from any email addresses 26 contained in a subject DN, the subject DN is taken from I<subject> or I<req>. 27 If I<subject> or I<crl> is provided, I<issuer> should point to its issuer, 29 Note that if I<subject> is provided, I<issuer> may be the same as I<subject>, 30 which means that I<subject> is self-issued (or even self-signed).
|
H A D | X509_check_host.pod | 26 X509_check_host() checks if the certificate Subject Alternative 27 Name (SAN) or Subject CommonName (CN) matches the specified hostname, 91 to consider the subject DN even if the certificate contains at least 92 one subject alternative name of the right type (DNS name or email 93 address as appropriate); the default is to ignore the subject DN 94 when at least one corresponding subject alternative names is present. 97 consider the subject DN even if the certificate contains no subject alternative 99 is to use the subject DN when no corresponding subject alternative names are 103 precedence and the subject DN is not checked for matching names.
|
H A D | X509_check_issued.pod | 12 int X509_check_issued(X509 *issuer, X509 *subject); 17 X509_check_issued() checks if certificate I<subject> was apparently issued 19 matching of the issuer field of I<subject> with the subject field of I<issuer>, 21 I<subject>, as far as present, with the respective B<subjectKeyIdentifier>, 25 if the I<issuer> or the I<subject> are incomplete certificates.
|
/freebsd/usr.bin/rctl/ |
H A D | rctl.c | 113 const char *subject, *subject_id, *resource, *action, *amount, *per; in expand_amount() local 123 subject = strsep(©, ":"); in expand_amount() 143 assert(subject != NULL); in expand_amount() 157 subject, subject_id, resource, action, (uintmax_t)num); in expand_amount() 160 subject, subject_id, resource, action, (uintmax_t)num, per); in expand_amount() 178 const char *subject, *textid, *rest; in expand_rule() local 188 subject = strsep(©, ":"); in expand_rule() 191 warnx("malformed rule '%s': missing subject", rule); in expand_rule() 199 if (strcasecmp(subject, "u") == 0) in expand_rule() 200 subject = "user"; in expand_rule() [all …]
|
/freebsd/crypto/krb5/src/tests/proxy-certs/ |
H A D | make-certs.sh | 14 distinguished_name = \$ENV::SUBJECT 85 SUBJECT=signer openssl req -config openssl.cnf -new -x509 -extensions exts_ca \ 89 SUBJECT=proxy openssl req -config openssl.cnf -new -key privkey.pem \ 91 SUBJECT=localhost openssl req -config openssl.cnf -new -key privkey.pem \ 97 SUBJECT=proxy openssl ca -config openssl.cnf -extensions exts_proxy \ 101 # Issue a certificate that only has the name in the subject field 102 SUBJECT=proxy openssl ca -config openssl.cnf -extensions exts_proxy_no_san \ 104 cat privkey.pem tmp.pem > proxy-subject.pem 107 SUBJECT=proxy openssl ca -config openssl.cnf -extensions exts_proxy_no_san \ 112 SUBJECT=proxy openssl ca -config openssl.cnf -extensions exts_proxy \ [all …]
|
/freebsd/crypto/heimdal/lib/hx509/ |
H A D | test_ca.in | 53 --subject="CN=Love,DC=it,DC=su,DC=se" \ 60 --subject="cn=foo" \ 108 --subject="cn=foo" \ 116 --subject="cn=foo" \ 125 --subject="cn=foo" \ 134 --subject="cn=foo" \ 143 --subject="cn=foo" \ 171 --subject="cn=www.test.h5l.se" \ 191 --subject="cn=foo" \ 197 echo "issue certificate (email, null subject DN)" [all …]
|
H A D | ca.c | 44 hx509_name subject; member 111 hx509_name_free(&(*tbs)->subject); in hx509_ca_tbs_free() 188 { "subject", HX509_CA_TEMPLATE_SUBJECT }, 230 if (tbs->subject) in hx509_ca_tbs_set_template() 231 hx509_name_free(&tbs->subject); in hx509_ca_tbs_set_template() 232 ret = hx509_cert_get_subject(cert, &tbs->subject); in hx509_ca_tbs_set_template() 235 "Failed to get subject from template"); in hx509_ca_tbs_set_template() 354 * Set the subject public key info (SPKI) in the to-be-signed certificate 360 * @param spki subject public key info to use for the to-be-signed certificate object. 553 * Add Subject Alternative Name otherName to the to-be-signed [all …]
|
/freebsd/share/man/man4/ |
H A D | mac_lomac.4 | 61 an information flow policy coupled with the subject demotion 88 may be used to indicate that a particular subject or object is exempt from 92 might be used on a subject which is to be used to administratively relabel 100 directory or the alternate label assumed by the subject upon execution of 114 Subject labels consist of three label elements: a single (active) label, 120 In general, subject labels are represented in the following form: 128 .D1 Ar subject Ns :: Ns Ar higrade No \[>=] Ar target-object Ns :: Ns Ar grade 130 Modification of subjects is the same, as the target subject's single grade 133 Demotion of a subject occurs when the following comparison is true: 135 .D1 Ar subject Ns :: Ns Ar singlegrade No > Ar object Ns :: Ns Ar grade [all …]
|
H A D | mac_biba.4 | 88 may be used to indicate that a particular subject or object is exempt from 103 A subject at the same integrity level as an object may both read from 106 A subject at a higher integrity level than an object may write to the object, 109 A subject at a lower integrity level than an object may read the object, 112 If the subject and object labels may not be compared in the partial order, 128 with the exception that LOMAC permits access by a higher integrity subject 129 to a lower integrity object, but downgrades the integrity level of the subject 131 Biba is a fixed label policy in that all subject and object label changes are 157 Subject labels consist of three label elements: an effective (active) label, 163 In general, subject labels are represented in the following form: [all …]
|
/freebsd/usr.bin/posixmqcontrol/ |
H A D | posixmqcontroltest8x64.sh | 4 subject='posixmqcontrol' 7 ${subject} info -q "$topic" 2>/dev/null 14 ${subject} create -q "$topic" -s 64 -d 8 19 info=$(${subject} info -q "$topic") 48 ${subject} send -q "$topic" -c "message $i" -p "$i" 54 info=$(${subject} info -q "$topic") 70 actual=$(${subject} recv -q "$topic") 81 info=$(${subject} info -q "$topic") 93 ${subject} rm -q "$topic"
|
H A D | posixmqcontroltest8qs.sh | 4 subject='posixmqcontrol' 11 ${subject} info -q "${topic}" 2>/dev/null 19 ${subject} create -d 2 -s 64 ${list} 24 ignore=$( ${subject} info ${list} ) 29 ${subject} send -c 'this message sent to all listed queues.' ${list} 38 ignore=$( ${subject} recv -q "${topic}" ) 44 ${subject} rm ${list}
|
/freebsd/secure/lib/libcrypto/man/man3/ |
H A D | X509V3_set_ctx.3 | 147 \& void X509V3_set_ctx(X509V3_CTX *ctx, X509 *issuer, X509 *subject, 156 Any of \fIsubject\fR, \fIreq\fR, or \fIcrl\fR may be provided, pointing to a certificate, 158 When constructing the subject key identifier of a certificate by computing a 159 hash value of its public key, the public key is taken from \fIsubject\fR or \fIreq\fR. 160 Similarly, when constructing subject alternative names from any email addresses 161 contained in a subject \s-1DN,\s0 the subject \s-1DN\s0 is taken from \fIsubject\fR or \fIreq\fR. 162 If \fIsubject\fR or \fIcrl\fR is provided, \fIissuer\fR should point to its issuer, 164 Note that if \fIsubject\fR is provided, \fIissuer\fR may be the same as \fIsubject\fR, 165 which means that \fIsubject\fR is self-issued (or even self-signed).
|
H A D | OSSL_CMP_MSG_get0_header.3 | 185 The subject \s-1DN\s0 included in the certificate template is 187 …any subject name in \fIctx\fR set via \fBOSSL_CMP_CTX_set1_subjectName\fR\|(3) \- if it is the NUL… 188 …IX Item "any subject name in ctx set via OSSL_CMP_CTX_set1_subjectName - if it is the NULL-DN (i.e… 190 .IP "the subject field of any PKCS#10 \s-1CSR\s0 set in \fIctx\fR via \fBOSSL_CMP_CTX_set1_p10CSR\f… 191 .IX Item "the subject field of any PKCS#10 CSR set in ctx via OSSL_CMP_CTX_set1_p10CSR," 192 …subject field of any reference certificate given in \fIctx\fR (see \fBOSSL_CMP_CTX_set1_oldCert\fR… 193 …subject field of any reference certificate given in ctx (see OSSL_CMP_CTX_set1_oldCert), but only … 211 If there is a reference certificate in \fIctx\fR and contains Subject Alternative
|
/freebsd/sys/dev/isci/scil/ |
H A D | sci_base_subject.h | 61 * common to all subjects object definitions. A subject is a 62 * participant in the observer pattern. A subject represents the 90 * @brief This method acts as the basic constructor for the subject. 92 * @param[in] this_subject This fields specifies the subject being 103 * observers attached to this subject. 105 * @param[in] this_subject This parameter specifies the subject for 115 * @brief This method will add an observer to the subject. 117 * @param[in] this_subject This parameter specifies the subject for which 120 * it listen for notifications for the supplied subject. 130 * @brief This method will remove the observer from the subject.
|
/freebsd/crypto/heimdal/doc/doxyout/hx509/man/man3/ |
H A D | hx509_ca.3 | 70 … "int \fBhx509_ca_tbs_set_subject\fP (hx509_context context, hx509_ca_tbs tbs, hx509_name subject)" 189 Add a Subject Alternative Name hostname to to-be-signed certificate object. A domain match starts w… 210 Add a Jabber/XMPP jid Subject Alternative Name to the to-be-signed certificate object. The jid is a… 229 Add Microsoft UPN Subject Alternative Name to the to-be-signed certificate object. The principal st… 248 Add Subject Alternative Name otherName to the to-be-signed certificate object. 269 Add Kerberos Subject Alternative Name to the to-be-signed certificate object. The principal string … 288 Add a Subject Alternative Name rfc822 (email address) to to-be-signed certificate object. 465 Set the subject public key info (SPKI) in the to-be-signed certificate object. SPKI is the public k… 473 \fIspki\fP subject public key info to use for the to-be-signed certificate object. 482 .SS "int hx509_ca_tbs_set_subject (hx509_context context, hx509_ca_tbs tbs, hx509_name subject)" [all …]
|
/freebsd/sys/contrib/openzfs/scripts/ |
H A D | commitcheck.sh | 37 # subject is not longer than 72 characters 40 echo "error: commit subject over 72 characters" 59 # subject starts with Fix coverity defects means it's a coverity fix 60 …subject=$(git log --no-show-signature -n 1 --pretty=%s "$REF" | grep -E -m 1 '^Fix coverity defect… 61 if [ -n "$subject" ]; then 72 # subject starts with Fix coverity defects: CID dddd, dddd... 73 subject=$(git log --no-show-signature -n 1 --pretty=%s "$REF" | 75 if [ -z "$subject" ]; then 76 …echo "error: Coverity defect fixes must have a subject line that starts with \"Fix coverity defect…
|
/freebsd/crypto/krb5/src/tests/ |
H A D | t_proxy.py | 14 proxysubjectpem = os.path.join(proxycerts, 'proxy-subject.pem') 70 # Fail: untrusted issuer, host name matches subject. 71 mark('untrusted issuer, hostname subject match') 72 output("running pass 2: subject matches, issuer not trusted\n") 92 output("running pass 4: subject matches, issuer not trusted\n") 110 # Succeed: trusted issuer and host name matches subject. 111 mark('trusted issuer, hostname subject match') 112 output("running pass 6: issuer trusted, subject matches\n") 155 # Fail: trusted issuer, but subject does not match. 156 mark('trusted issuer, IP mismatch (hostname in subject)') [all …]
|
/freebsd/contrib/openbsm/libbsm/ |
H A D | bsm_wrappers.c | 119 * subject token generation. in audit_submit() 151 "audit: unable to build subject token"); in audit_submit() 297 audit_write(short event_code, token_t *subject, token_t *misctok, char retval, in audit_write() argument 305 au_free_token(subject); in audit_write() 311 /* Save subject. */ in audit_write() 312 if (subject && au_write(aufd, subject) == -1) { in audit_write() 313 au_free_token(subject); in audit_write() 316 syslog(LOG_ERR, "%s: write of subject failed", func); in audit_write() 364 token_t *subject = NULL; in audit_write_success() local 366 /* Tokenize and save subject. */ in audit_write_success() [all …]
|
/freebsd/crypto/openssl/crypto/x509/ |
H A D | x509_txt.c | 83 return "subject issuer mismatch"; in X509_verify_cert_error_string() 85 return "authority and subject key identifier mismatch"; in X509_verify_cert_error_string() 170 return "proxy subject name violation"; in X509_verify_cert_error_string() 180 return "subject signature algorithm and issuer public key algorithm mismatch"; in X509_verify_cert_error_string() 194 return "Subject name empty"; in X509_verify_cert_error_string() 198 return "Missing Subject Key Identifier"; in X509_verify_cert_error_string() 200 return "Empty Subject Alternative Name extension"; in X509_verify_cert_error_string() 204 return "Subject empty and Subject Alt Name extension not critical"; in X509_verify_cert_error_string() 208 return "Subject Key Identifier marked critical"; in X509_verify_cert_error_string()
|
/freebsd/usr.sbin/ugidfw/ |
H A D | ugidfw.8 | 40 .Cm subject 95 .Cm subject 163 .Cm subject 180 .Cm subject 198 .Cm subject 216 means that the subject should not match the remainder of the specification. 219 to indicate that particular condition must not match the subject. 220 The subject can be required to have a particular 225 The subject can be required to be in a particular jail with the
|