Searched refs:sufficient (Results 1 – 25 of 133) sorted by relevance
123456
| /src/lib/libpam/pam.d/ |
| H A D | sshd | 7 #auth sufficient pam_krb5.so no_warn try_first_pass 8 #auth sufficient pam_ssh.so no_warn try_first_pass 22 #password sufficient pam_krb5.so no_warn try_first_pass
|
| H A D | system | 7 #auth sufficient pam_krb5.so no_warn try_first_pass 8 #auth sufficient pam_ssh.so no_warn try_first_pass 22 #password sufficient pam_krb5.so no_warn try_first_pass
|
| H A D | pop3 | 7 #auth sufficient pam_krb5.so no_warn try_first_pass 8 #auth sufficient pam_ssh.so no_warn try_first_pass
|
| H A D | imap | 7 #auth sufficient pam_krb5.so no_warn try_first_pass 8 #auth sufficient pam_ssh.so no_warn try_first_pass
|
| H A D | su | 7 auth sufficient pam_rootok.so no_warn 8 auth sufficient pam_self.so no_warn
|
| H A D | ftpd | 7 #auth sufficient pam_krb5.so no_warn 8 #auth sufficient pam_ssh.so no_warn try_first_pass
|
| H A D | other | 7 #auth sufficient pam_krb5.so no_warn try_first_pass 8 #auth sufficient pam_ssh.so no_warn try_first_pass
|
| H A D | xdm | 7 #auth sufficient pam_krb5.so no_warn try_first_pass 8 #auth sufficient pam_ssh.so no_warn try_first_pass
|
| H A D | README | 37 sufficient: success is sufficient, and if no previous required 39 binding: success is sufficient; on failure all remaining 57 Note that having a "sufficient" module as the last entry for a
|
| H A D | login | 7 auth sufficient pam_self.so no_warn
|
| /src/sys/contrib/device-tree/Bindings/sound/ |
| H A D | max98357a.txt | 16 It's observed that 5ms is sufficient.
|
| H A D | max98373.txt | 25 for the I/V sense data is not sufficient, the device can also be configured
|
| /src/contrib/llvm-project/llvm/lib/Target/Hexagon/ |
| H A D | HexagonIICHVX.td | 23 // used, which should be sufficient.
|
| /src/crypto/openssl/doc/man3/ |
| H A D | SSL_get_all_async_fds.pod | 40 responsibility to ensure sufficient memory is allocated at I<*fds> so typically 49 sufficient memory allocated, although they may be NULL. The number of added fds
|
| H A D | BN_CTX_start.pod | 40 as well, so it is sufficient to check the return value of the last
|
| H A D | ASYNC_WAIT_CTX_new.pod | 68 sufficient memory has been allocated in I<*fd> to receive all the file 72 the number of fds, and then again when sufficient memory has been allocated. If 84 NULL then the caller is responsible for ensuring sufficient memory is allocated.
|
| H A D | SCT_validate.pod | 72 failure. At a minimum, only one valid SCT may provide sufficient confidence
|
| H A D | SSL_CTX_set_max_cert_list.pod | 42 on the 16-bit DOS platform). This should be sufficient for usual certificate
|
| /src/release/packages/ucl/ |
| H A D | at-all.ucl | 25 * batch(1) executes a command when sufficient system resources are available.
|
| /src/contrib/arm-optimized-routines/ |
| H A D | README.contributors | 24 to the build system, so it should be documented in sufficient detail and
|
| /src/sys/contrib/device-tree/Bindings/rtc/ |
| H A D | isil,isl12057.txt | 41 "interrupt-parent" and "interrupts" are usually sufficient):
|
| /src/sys/contrib/device-tree/Bindings/power/reset/ |
| H A D | gpio-restart.txt | 37 sufficient to restart the entire system
|
| /src/contrib/xz/ |
| H A D | COPYING | 50 a copyright notice is needed, the following is sufficient:
|
| /src/crypto/openssl/test/ssl-tests/ |
| H A D | 13-fragmentation.cnf.in | 194 # easily sufficient.
|
| /src/crypto/openssl/doc/internal/man3/ |
| H A D | ossl_cmp_print_log.pod | 48 log callback of the B<ctx> if present and the severity level is sufficient.
|
123456