Searched refs:succeed (Results 1 – 25 of 104) sorted by relevance
12345
12 .MAKEFLAGS: fail1 fail2 succeed17 succeed: .PHONY
5 true succeed
1 Make install targets succeed for non-root users by installing
112 #succeed but fallback to P-256172 #negotiation to succeed because we fall back to some other
109 # should succeed.
63 /* Must succeed */
70 /* Must succeed */
76 /* Must succeed */
64 /* Must succeed */
25 # AX_HAVE_POLL would succeed if AX_HAVE_PPOLL has, but not the other way
90 written to the BIO so the next read will succeed: this is most useful114 TLS/SSL handshake for example. BIO_write_ex() will succeed and place data in the117 transport before flushing the write buffer it will never succeed because the
40 For the transparent negotiation to succeed, the B<ssl> must have been58 can succeed.
25 given by B<ctx>. This check will always succeed for key types that do not have
46 to succeed. This makes the handshake suspend and return control to the
90 all circumstances because this will allow verification to succeed no matter
62 PKCS #1 v1.5 RSA padding) all recipients are tried whether they succeed or
53 It is also possible for the callback to succeed but not supply a PSK. In this
7 Otherwise it is expected to succeed, and the third field is the string to
32 linker command line can result in different outcomes. A link may succeed with33 LLD that will fail with GNU ld, or even worse both links succeed but they have
158 bool succeed = in ParseImportedModules() local160 if (succeed) in ParseImportedModules()
61 -- read-only properties should never succeed
158 # Continue prompting until they either Cancel, succeed298 # Continue prompting until they either Cancel, succeed or exceed the
116 seen the tests succeed!):
592 # Did that succeed?616 # Did that succeed?641 # Did that succeed?668 # Did that succeed?
265 AP_REQ validation must succeed. This is basically a paranoid bit, and273 Initial ticket verification will succeed if and only if: