search for: t_strndup

...: Aug 16 16:59:38 postamt dovecot: IMAP(username): file strfuncs.c: line 165 (p_strndup): assertion failed: (max_chars != (size_t)-1) Aug 16 16:59:38 postamt dovecot: IMAP(username): Raw backtrace: imap [0x80c6d53] -> imap(i_fatal+0) [0x80c6795] -> imap(p_strndup+0x38) [0x80d8316] -> imap(t_strndup+0x22) [0x80d86d7] -> imap(cmd_create+0xb5) [0x8059a39] -> imap [0x805eb09] -> imap [0x805ecf9] -> imap(_client_input+0x116) [0x805ee1b] -> imap(io_loop_handler_run+0x191) [0x80cebf8] -> imap(io_loop_run+0x20) [0x80cde56] -> imap(main+0xb8) [0x8069cbf] -> /lib/i686/cmov/libc....

...uid >> ?0?"-message? >> >> from fts-solr source: >> ????case?SOLR_XML_CONTENT_STATE_UID: >> ????????if?(uint32_parse(str,?len,?&ctx->uid)?<?0?||?ctx->uid?==?0)?{ >> ????????????i_error("fts_solr:?received?invalid?uid?'%s'",?t_strndup(str,?len)); >> It means that plugin tries to parse '0' when in state of parsing uid >> in xml response from solr or there is a bug in xml response parser. >> I would enable rawlog_dir in config and look there for unusual >> response or extra tags near usual uid in...

...been seen with two different users, following syslog entries: Jan 7 18:27:01 siege dovecot: IMAP(userA): file strfuncs.c: line 165 (p_strndup): assertion failed: (max_chars != (size_t)-1) Jan 7 18:27:01 siege dovecot: IMAP(userA): Raw backtrace: imap [0x46372e] -> imap [0x46349c] -> imap(t_strndup+0) [0x470cf0] -> imap(cmd_create+0xd1) [0x4142c1] -> imap [0x4178f7] -> imap [0x417989] -> imap(_client_input+0x6d) [0x417fbd] -> imap(io_loop_handler_run+0x101) [0x468e61] -> imap(io_loop_run+0x18) [0x467f28] -> imap(main+0x3f2) [0x41f6c2] -> /lib/libc.so.6(__libc_star...

...ns->sep) directory = FALSE; else { /* name ends with hierarchy separator - client is just informing us that it wants to create children under this mailbox. */ directory = TRUE; mailbox = t_strndup(mailbox, len-1); full_mailbox = t_strndup(full_mailbox, strlen(full_mailbox)-1); i_info("Z CREATE NAME: YYY%sYYY", mailbox); } We've been having trouble with people not being able to create a mail folder that will contain other folders. Tried it both...

...oxy *proxy) { X509 *x509; - char buf[1024]; + char buf[256]; const char *name; if (!ssl_proxy_has_valid_client_cert(proxy)) @@ -508,10 +508,16 @@ if (x509 == NULL) return NULL; /* we should have had it.. */ - X509_NAME_oneline(X509_get_subject_name(x509), buf, sizeof(buf)); - name = t_strndup(buf, sizeof(buf)); + /* HJHJ */ + /* the X509_N_gtbN can return -1 without 0-terminating buf */ + /* if the call succeeds buf is 0-terminated (openssl 0.9.7e / 0.9.8b src) */ + buf[0] = '\0'; + if( X509_NAME_get_text_by_NID(X509_get_subject_name(x509),NID_commonName,buf,sizeof(buf)) < 0...

...gt; > >>> from fts-solr source: > >>> case SOLR_XML_CONTENT_STATE_UID: > >>> if (uint32_parse(str, len, &ctx->uid) < 0 || ctx->uid == 0) { > >>> > i_error("fts_solr: received invalid uid '%s'", t_strndup(str, len)); > > >>> > >>> It means that plugin tries to parse '0' when in state of parsing uid > >>> in xml response from solr or there is a bug in xml response parser. > >>> I would enable rawlog_dir in config and look there for unusual &g...

...#6 0xb7751886 in p_strndup (pool=0xb7796544 <static_unsafe_data_stack_pool>, str=str at entry=0x0, max_chars=max_chars at entry=4294967295) at strfuncs.c:74 mem = <optimized out> len = <optimized out> __FUNCTION__ = "p_strndup" #7 0xb7751d7f in t_strndup (str=0x0, max_chars=4294967295) at strfuncs.c:236 No locals. #8 0x08057003 in auth_request_append_password (str=str at entry=0x97e68a8, request=0x97f8da8, request=0x97f8da8) at auth-request.c:1799 p = <optimized out> log_type = <optimized out> max_len = 42949672...

...; >>> case SOLR_XML_CONTENT_STATE_UID: > > >>> > > if (uint32_parse(str, len, &ctx->uid) < 0 || ctx->uid == 0) { > > >>> > > > i_error("fts_solr: received invalid uid '%s'", t_strndup(str, len)); > > > > >>> > > >>> It means that plugin tries to parse '0' when in state of > > parsing uid > > >>> in xml response from solr or there is a bug in xml response > > parser. > > >>&...

...hints or tips regarding this ?invalid uid ?0?"-message? > from fts-solr source: > case SOLR_XML_CONTENT_STATE_UID: > if (uint32_parse(str, len, &ctx->uid) < 0 || ctx->uid == 0) { > i_error("fts_solr: received invalid uid '%s'", t_strndup(str, len)); > It means that plugin tries to parse '0' when in state of parsing uid in xml response from solr or there is a bug in xml response parser. > I would enable rawlog_dir in config and look there for unusual response or extra tags near usual uid in xml response. For example: &...

..."-message? >>> >>> from fts-solr source: >>> ????case?SOLR_XML_CONTENT_STATE_UID: >>> ????????if?(uint32_parse(str,?len,?&ctx->uid)?<?0?||?ctx->uid?==?0)?{ >>> ????????????i_error("fts_solr:?received?invalid?uid?'%s'",?t_strndup(str,?len)); >>> >>> It means that plugin tries to parse '0' when in state of parsing uid >>> in xml response from solr or there is a bug in xml response parser. >>> I would enable rawlog_dir in config and look there for unusual >>> response or...

http://dovecot.org/test/ Fixes several crashes. Apparently can still break with mboxes, although it works with me.. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL:

...st char *plaintext, const char *user ATTR_UNUSED, const unsigned char *raw_password, size_t size) { const char *password; if (size == 0) { /* the default mycrypt() handler would return match */ return FALSE; } password = t_strndup(raw_password, size); return strcmp(mycrypt(plaintext, password), password) == 0; } but according to man page crypt() can fail and NULL is returned then. On other hand glibc info page is silent about such failure. The thing is that I'm seeing crypt() failure here with new glibc 2.10.1...

...o this, but in RFC 4422 this is explicitly allowed, and means the authz identity is identical to the authn identity. I believe the attached patches (for the 1.2 and 2.1 branches) fix the problem, though I'm not entirely sure if the difference between the p_strndup in mech_gssapi_unwrap and the t_strndup in get_display_name is important. Ben -------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot12-sasl-gssapi.patch Type: text/x-diff Size: 2859 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20120714/a5c28b1c/attachment-0008....

Hello dovecot users, I have updated the MANAGESIEVE patch to apply and compile against dovecot 1.0.rc28. Not much has changed with respect to the functionality of the previous version however: ChangeLog vs v2 - Updated source to compile with dovecot 1.0.rc28, tested with rc27 (debian package) - Daemon now uses the same location for .dovecot.sieve as dovecot-lda This is typically

...m fts-solr source: > >>> ????case?SOLR_XML_CONTENT_STATE_UID: > >>> > ????????if?(uint32_parse(str,?len,?&ctx->uid)?<?0?||?ctx->uid?==?0)?{ > >>> > ????????????i_error("fts_solr:?received?invalid?uid?'%s'",?t_strndup(str,?len)); > > >>> > >>> It means that plugin tries to parse '0' when in state of > parsing uid > >>> in xml response from solr or there is a bug in xml response > parser. > >>> I would enable rawlog_dir in co...

.../dovecot/libdovecot.so.0 [0x9fefd9e1] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0 [0x9fefda5f] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(i_error+0) [0x9fefdd18] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0 [0x9ff1a2df] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(t_strndup+0x30) [0x9ff1a310] -> /usr/local/dovecot/lib/dovecot/lib01_acl_plugin.so [0x9fd32747] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(mailbox_list_iter_next+0x12) [0x9ff559f2] -> dovecot/imap [0x8051deb] -> dovecot/imap(cmd_list_full+0x424) [0x8052d34] -> dovecot/imap(cmd_l...

...lds; + 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_DECODED_SIZE(len)); + if (base64_decode(fields[2], len, NULL, + request->stored_key) <...

Hy, over the last days I have implemented SCRAM-SHA-1 in Dovecot's 2.1 branch. It does not do SCRAM-SHA-1-PLUS, but should be extendable enough to introduce it later. There are some checks for the message format which (assuming the client acts correclty) are not strictly necessary during parsing. This is partially in the hope that it might aid client implementers, partially because it (IMHO)

I also tried the 0.99 and hacking login-process.c, with no success. It seems to expect a slash delimited string like 'name/protocol' and it just gets "imap" there, but I didn't figure out where this string comes from or what it ought to be. So I would be grateful if someone could enlighten me. Thanks, Peter --- Some blafa: Feb 17 21:45:44 office dovecot: Dovecot

Hi, It looks like I've found something strange. It looks like dovecot updates fts-lucene index every time I'm opening virtual folder that contains FTS query: indexer-worker(dion): Warning: fts-lucene: Settings have changed, rebuilding index for mailbox dovecot-virtual is pretty simple: archive/INBOX BODY "test" first of all, I'm trying to perform FTS in archive/INBOX