Lines Matching full:sasl
25 * RFC4422 Simple Authentication and Security Layer (SASL)
27 * RFC4752 The Kerberos V5 ("GSSAPI") SASL Mechanism
28 * RFC4959 IMAP Extension for SASL Initial Client Response
31 * Draft LOGIN SASL Mechanism <draft-murchison-sasl-login-00.txt>
215 /* SASL parameters for the imap protocol */
223 imap_get_message /* Get SASL response message */
463 imapc->sasl.authmechs = SASL_AUTH_NONE; /* No known auth. mechanisms yet */
464 imapc->sasl.authused = SASL_AUTH_NONE; /* Clear the auth. mechanism used */
564 * SASL authentication mechanism.
588 * Sends SASL continuation data or cancellation.
602 * Initiates the authentication sequence, with the appropriate SASL
614 if(!Curl_sasl_can_authenticate(&imapc->sasl, conn)) {
619 /* Calculate the SASL login details */
620 result = Curl_sasl_start(&imapc->sasl, conn, imapc->ir_supported, &progress);
896 /* Does the server support the SASL-IR capability? */
897 else if(wordlen == 7 && !memcmp(line, "SASL-IR", 7))
900 /* Do we have a SASL based authentication mechanism? */
911 imapc->sasl.authmechs |= mechbit;
964 /* For SASL authentication responses */
976 result = Curl_sasl_continue(&imapc->sasl, conn, imapcode, &progress);
1445 Curl_sasl_init(&imapc->sasl, &saslimap);
1657 /* Cleanup the SASL module */
1658 Curl_sasl_cleanup(conn, imapc->sasl.authused);
1934 imapc->sasl.resetprefs = TRUE;
1949 result = Curl_sasl_parse_url_auth_option(&imapc->sasl,
1958 switch(imapc->sasl.prefmech) {
