Lines Matching refs:not
95 Most of the Mbed TLS SSL/TLS related options are not supported or not
142 exchange mode enabled, the TLS 1.3 implementation does not contain any code
147 mode enabled, the TLS 1.3 implementation does not contain any code related
156 exchange mode enabled, the TLS 1.3 implementation does not contain any code
241 check that we do not write or read past the end of a data buffer. The
265 - We prefer grouping "related statement lines" by not adding blank lines
291 the pointer name not appended to the pointer type:
299 - string literals can extend beyond 80 characters as we do not want to
351 The implementation does not go systematically through all states as this would
352 result in too many checks of whether something needs to be done or not in a
355 bypassed if the handshake is based on a pre-shared key and thus does not
369 between the calls to the handlers and as a consequence handlers do not have to
371 data are flushed before to call the next handler. That way, handlers do not
380 message. The latter occurs when it is not known what the next handshake message
382 CertificateRequest message or not. The intent is, apart from the next record
383 reading to not modify the SSL context as this stage may be repeated if the
384 next handshake message has not been received yet.
387 message we must receive next and we try to fetch it. If we did not go through
389 handshake message may not have been received yet, the handler returns with