search for: passdb_result_ok

...I tried replacing my passdb lookup with this: > > function auth_passdb_lookup(req) > passdb_table = {} > passdb_table[ 'password' ] = 'test' > passdb_table[ 'user' ] = 'test1 at test.com' > > return dovecot.auth.PASSDB_RESULT_OK, passdb_table > end > > and still get: > > Dec 22 01:17:17 auth-worker(9711): Info: > lua(test1 at test.com,10.20.103.32,<f2O5xOdgFoYKFGcg>): > No password returned (and no nopassword) > > Replacing that return statement with this: > > return dovecot.auth....

> On December 22, 2017 at 6:43 AM Mark Moseley <moseleymark at gmail.com> wrote: > > > > > > > > > > > > 2) Is there an appropriate way to return data with spaces in it (or > > presumably other non-alphanum chars. My quota name had a space in it, > > which > > somehow got interpreted as 'yes' , i.e.: > > > > imap:

...0xb77d230a in static_lookup_real (auth_request=auth_request at entry=0xb84b9218, callback=0xb77ba9b0 <auth_request_userdb_callback>) at userdb-static.c:32 _module = <optimized out> module = <optimized out> #5 0xb77d23ae in static_credentials_callback (result=PASSDB_RESULT_OK, credentials=0xb84b5bb7 "Mananozu", size=8, auth_request=0xb84b9218) at userdb-static.c:52 ctx = 0xb84bb860 #6 0xb77bc039 in auth_request_lookup_credentials_finish (result=PASSDB_RESULT_OK, credentials=credentials at entry=0xb84b5bb7 "Mananozu", size=size at ent...

...5e445c659f89 src/auth/auth-request.c --- a/src/auth/auth-request.c Tue May 05 13:35:52 2015 +0300 +++ b/src/auth/auth-request.c Tue May 05 14:16:31 2015 +0300 @@ -618,30 +627,28 @@ auth_request_want_skip_passdb(request, next_passdb)) next_passdb = next_passdb->next; + if (*result == PASSDB_RESULT_OK) { + /* this passdb lookup succeeded, preserve its extra fields */ + auth_fields_snapshot(request->extra_fields); + request->snapshot_have_userdb_prefetch_set = + request->userdb_prefetch_set; + if (request->userdb_reply != NULL) + auth_fields_snapshot(request->userdb_reply);...

....rc1 (12aba5948) For testing this, I tried replacing my passdb lookup with this: function auth_passdb_lookup(req) passdb_table = {} passdb_table[ 'password' ] = 'test' passdb_table[ 'user' ] = 'test1 at test.com' return dovecot.auth.PASSDB_RESULT_OK, passdb_table end and still get: Dec 22 01:17:17 auth-worker(9711): Info: lua(test1 at test.com,10.20.103.32,<f2O5xOdgFoYKFGcg>): No password returned (and no nopassword) Replacing that return statement with this: return dovecot.auth.PASSDB_RESULT_OK, 'password=test user=test1 at test...

...c > --- a/src/auth/auth-request.c Tue May 05 13:35:52 2015 +0300 > +++ b/src/auth/auth-request.c Tue May 05 14:16:31 2015 +0300 > @@ -618,30 +627,28 @@ > auth_request_want_skip_passdb(request, next_passdb)) > next_passdb = next_passdb->next; > > + if (*result == PASSDB_RESULT_OK) { > + /* this passdb lookup succeeded, preserve its extra fields */ > + auth_fields_snapshot(request->extra_fields); > + request->snapshot_have_userdb_prefetch_set = > + request->userdb_prefetch_set; > + if (request->userdb_reply != NULL) > + auth_fields_snaps...

...up with this: > > > > function auth_passdb_lookup(req) > > passdb_table = {} > > passdb_table[ 'password' ] = 'test' > > passdb_table[ 'user' ] = 'test1 at test.com' > > > > return dovecot.auth.PASSDB_RESULT_OK, passdb_table > > end > > > > and still get: > > > > Dec 22 01:17:17 auth-worker(9711): Info: > > lua(test1 at test.com,10.20.103.32,<f2O5xOdgFoYKFGcg>): > > No password returned (and no nopassword) > > > > Replacing that return statement...

...+ /* it is needed for open smtp relay */ + + ip_addr_fe = net_ip2addr(&request->client_ip); + if (ip_addr_fe == NULL) + ip_addr_fe = "??"; + + env_put(t_strconcat("TCPREMOTEIP=", ip_addr_fe, NULL)); + open_smtp_relay(); + callback(PASSDB_RESULT_OK, request); } diff -Naur dovecot-0.99.10.5/src/login-common/auth-connection.c dovecot-0.99.10.5-patched/src/login-common/auth-connection.c --- dovecot-0.99.10.5/src/login-common/auth-connection.c Mon May 26 19:27:13 2003 +++ dovecot-0.99.10.5-patched/src/login-common/auth-connection.c Mon...

...vpw->pw_clear_passwd); *cleartext = TRUE; } else if (!*cleartext) password = t_strdup_noconst(vpw->pw_passwd); else password = NULL; *result_r = password != NULL ? PASSDB_RESULT_OK : PASSDB_RESULT_SCHEME_NOT_AVAILABLE; } </snippet> Looking for an option to make dovecot use hashed password instead of clear text. Hope this makes sense. -EricB We seem to have lost quoting.. First - Why aren't you just deleting all the clea...

Quoting Aki Tuomi <aki.tuomi at open-xchange.com>: > On 03.10.2018 23:30, Eric Broch wrote: >> Hello list, >> >> I run Dovecot with the vpopmail driver and have found that it >> authenticates against the clear text password in the vpopmail >> database. Is there a configuration option either at compile time, link >> time, or a setting in one of the

Hi list, I have a question on auth caching in 2.2.18. I am using acl_groups for a master user, appended in a static userdb file # snip ############################### master at uma:{SHA}XXXX=::::::userdb_acl_groups=umareadmaster allow_nets=127.0.0.1 # snap ############################### and use this group in a global ACL file. I discovered this only works on first NOT-cached login

...*cleartext = TRUE; >> } else if (!*cleartext) >> password = t_strdup_noconst(vpw->pw_passwd); >> else >> password = NULL; >> *result_r = password != NULL ? PASSDB_RESULT_OK : >> PASSDB_RESULT_SCHEME_NOT_AVAILABLE; >> } >> </snippet> >> >> >> Looking for an option to make dovecot use hashed password instead >> of clear text. >> >> Hope this makes sense. >> >> -Eric...

Hi, We are trying to implement a highly secure mail server with user authentication restricted to SSL certificates only (not using passwords at all). Still, user information is stored in a LDAP directory. In this configuration LDAP is used to check whether the user is registered (and probably supply quota and other info), and actual authentication is done by SSL layer. According to wiki, a

...nst(vpw->pw_clear_passwd); *cleartext = TRUE; } else if (!*cleartext) password = t_strdup_noconst(vpw->pw_passwd); else password = NULL; *result_r = password != NULL ? PASSDB_RESULT_OK : PASSDB_RESULT_SCHEME_NOT_AVAILABLE; } </snippet> Looking for an option to make dovecot use hashed password instead of clear text. Hope this makes sense. -EricB -- Eric Broch White Horse Technical Consulting (WHTC) -------------- next part ------...

Hi guys, Just tested yesterday's stable build, when including SQL into the build I am getting an error on like 86 of passdb-sql.c (passdb_result = PASSDB_RESULT_OK;) It rightly says passdb_result is undeclared. Commenting out this line fixes it and build appears to work fine after that. Regards Andrew -- Andrew Hutchings Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

...> *cleartext = TRUE; > } else if (!*cleartext) > password = t_strdup_noconst(vpw->pw_passwd); > else > password = NULL; > *result_r = password != NULL ? PASSDB_RESULT_OK : > PASSDB_RESULT_SCHEME_NOT_AVAILABLE; > } > </snippet> > > > Looking for an option to make dovecot use hashed password instead of clear text. > > Hope this makes sense. > > -EricB > > We seem to have lost quoting.. > F...

...any later version. + */ + +#include "common.h" +#include "mech.h" +#include "passdb.h" +#include "safe-memset.h" + +static void verify_callback(enum passdb_result result, + struct auth_request *request) +{ + mech_auth_finish(request, NULL, 0, result == PASSDB_RESULT_OK); +} + +static int +mech_login_auth_continue(struct auth_request *auth_request, + const unsigned char *data, size_t data_size, + mech_callback_t *callback) +{ + struct auth_client_request_reply reply; + static const char prompt2[] = "Password:"; + + auth_request->callback = callb...

...*cleartext = TRUE; >>> ? ? ? ? ? ? ? ?} else if (!*cleartext) >>> ? ? ? ? ? ? ? ? ? ? ? ?password = t_strdup_noconst(vpw->pw_passwd); >>> ? ? ? ? ? ? ? ?else >>> ? ? ? ? ? ? ? ? ? ? ? ?password = NULL; >>> ? ? ? ? ? ? ? ?*result_r = password != NULL ? PASSDB_RESULT_OK : >>> ? ? ? ? ? ? ? ? ? ? ? ?PASSDB_RESULT_SCHEME_NOT_AVAILABLE; >>> ? ? ? ?} >>> </snippet> >>> >>> Looking for an option to make dovecot use hashed password instead >>> of clear text. >>> >>> Hope this makes sense. &g...

Hi, I'm setting up a Postfic and Dovecot with LDAP email server. My users in LDAP is like this: dn: uid=firstname,ou=People,dc=domain,dc=com uid: firstname uidNumber: 4025 gidNumber: 4025 givenName: firstname objectClass: top objectClass: person objectClass: posixAccount objectClass: shadowAccount objectClass: organizationalPerson objectClass:

...har *credentials, size_t size, struct auth_request *auth_request) { + const char *const *fields; + size_t len; + int iter; + const char *salt; struct scram_auth_request *request = (struct scram_auth_request *)auth_request; - const char *server_final_message; switch (result) { case PASSDB_RESULT_OK: - if (!verify_credentials(request, credentials, size)) { + fields = t_strsplit(t_strndup(credentials, size), ","); + + iter = atoi(fields[0]); + salt = fields[1]; + + len = strlen(fields[2]); + request->stored_key = buffer_create_dynamic(request->pool, + MAX_BASE64_DECODE...