... The PLAIN SASL Mechanism <draft-ietf-sasl-plain-09.txt> Status of Memo This document is intended to be, after appropriate review and revision, submitted to ...
... the PLAIN SASL mechanism ([PLAIN]). The LOGIN mechanism is documented here only for the purpose of backwards compatibility with legacy software. Clients ...
... the PLAIN SASL mechanism, defined in [RFC4616]. A server implementation MUST implement a configuration in which it does NOT permit any plaintext password ...
(Editor), "The Plain SASL Mechanism", draft-ietf-sasl-plain-xx.txt, a work in progress. [PR29] "Public Review Issue #29: Normalization Issue", <http://www ...
[PLAIN] Zeilenga, K., "The PLAIN SASL Mechanism", draft-ietf-sasl- plain-*, Work in Progress. [SMTP] Klensin, J., "Simple Mail Transport Protocol", RFC 2821 ...
... the [PLAIN] SASL mechanism. Implementations MUST support a configuration where SASL mechanisms that are vulnerable to passive eavesdropping attacks are not ...
The following is an example authentication using the [PLAIN] SASL mechanism (under a [TLS] protection layer) and an initial client response: ... client ...
... the PLAIN SASL mechanism [RFC4616]. Similarly, implementations MUST provide the EXTERNAL SASL mechanism if both parties are authenticated during the TLS ...
This defines the "PLAIN" SASL mechanism for use with ACAP and other protocols with no clear-text login command. The PLAIN SASL mechanism MUST NOT be ...
EPP uses a variant of the PLAIN SASL mechanism described in [RFC2595] to provide a simple application-layer authentication service. Where the PLAIN SASL ...
In order to show you the most relevant results, we have omitted some entries very similar to the 10 already displayed.
If you like, you can repeat the search with the omitted results included. |