search for: passdb_result_internal_failur

...n PASSDB_RESULT_NEXT. When a SASL mechanism calls auth_request_lookup_credentials(...,callback) the passdb result is passed to the callback. But I can't really figure out when that result will ever be PASSDB_RESULT_NEXT. It seems the passdb fallthrough resolver will always replace it with PASSDB_RESULT_INTERNAL_FAILURE if it ends up being the last result. Can it ever leak into the callback or is it an internal intermediate value or the passdb resolver? /Peter

...->username_format, table); + + status = pam_start(service, str_c(username), &conv, &pamh); if (status != PAM_SUCCESS) { auth_request_log_error(request, "pam", "pam_start() failed: %s", pam_strerror(pamh, status)); + str_free(&username); return PASSDB_RESULT_INTERNAL_FAILURE; } @@ -277,6 +300,7 @@ if ((status2 = pam_end(pamh, status)) != PAM_SUCCESS) { auth_request_log_error(request, "pam", "pam_end() failed: %s", pam_strerror(pamh, status2)); + str_free(&username); return PASSDB_RESULT_INTERNAL_FAILURE; } @@ -300,6...

Help, new to dovecot... I want to get some output from my test sessions to confirm that SSL pop and imap are working. How does one get debug output from dovecot? How does one see that dovecot is using SSL in a transaction? I configured dovecot 0.99.13 with: CC=gcc CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot --with-ssl=openssl \

A little problem, which is bugging me: when using PAM authentication, Dovecot (0.99.5) does not set the PAM_RHOST item, so the PAM modules cannot know who the client is. We need this for some PAM module doing access control. Changing passdb-pam.c to pam_set_item it seems trivial, but I'm bugged as to how to get the client name from there. It seems not to be available in the auth_request

...80103cdf6eb90483" fields_count = 2 name = 0x0 #1 sql_query_callback (result=0x7fb891e82f60, sql_request=0x7fb891e82c08) at passdb-sql.c:87 auth_request = 0x7fb891e82a80 _module = <optimized out> module = <optimized out> passdb_result = PASSDB_RESULT_INTERNAL_FAILURE password = 0x0 scheme = <optimized out> ret = <optimized out> __FUNCTION__ = "sql_query_callback" #2 0x00007fb891c3c940 in driver_sqlpool_query_callback (result=0x7fb891e82f60, request=0x7fb891e82e50) at driver-sqlpool.c:635 db = 0...

...est); + break; + } + + request->server_first_message = p_strdup(request->pool, + get_scram_server_first(request, iter, salt)); + + auth_request_handler_reply_continue(auth_request, + request->server_first_message, + strlen(request->server_first_message)); break; case PASSDB_RESULT_INTERNAL_FAILURE: auth_request_internal_failure(auth_request); @@ -333,8 +323,6 @@ request->client_final_message_without_proof = p_strdup(request->pool, t_strarray_join(fields, ",")); - auth_request_lookup_credentials(&request->auth_request, "PLAIN", - credentials_cal...