similar to: dovecot-auth crash

#0 io_remove (io=0x0) at ioloop.c:51 51 if ((io->condition & IO_NOTIFY_MASK) != 0) { (gdb) bt #0 io_remove (io=0x0) at ioloop.c:51 #1 0x0804fd68 in auth_client_connection_destroy_wait (conn=0x80877d8) at auth-client-connection.c:494 #2 0x08050acd in auth_callback (request=0x84716b8, result=134681554, reply=0x0, reply_size=0) at auth-client-connection.c:104 #3 0x08050950 in

OpenBSD 3.6 -current (i386) dovecot-1.0-test51 I'm now getting this error message as soon as I start dovecot: "Authentication client 0 not compatible with this server (mixed old and new binaries?)" Here's the process I'm using: ./configure --sysconfdir=/etc \ --with-ssl=openssl \ --with-pam=NO \ --with-ldap=no \ --with-vpopmail=no \

If the auth backend (postgresql in my case) returns extra fields, and all of these extra_fields begin with 'userdb_', the auth_callback functions adds an unwanted extra tab at the end of the response: auth(default): client out: OK^I8^Iuser=foo at bar^I This extra tab at the end confuses exim's dovecot-auth handler (the exim-dovecot auth handler does not correctly count the number of

The man page for getline says: ssize_t getline(char **lineptr, size_t *n, FILE *stream); [...] If *lineptr is set to NULL and *n is set 0 before the call, then get‐ line() will allocate a buffer for storing the line. This buffer should be freed by the user program even if getline() failed. which seems to indicate that we must initialize both line and len to 0 before the first

From: "Richard W.M. Jones" <rjones at redhat.com> This commit models libvirt authentication events through the API, adding one new event (GUESTFS_EVENT_LIBVIRT_AUTH) and several new APIs: guestfs_set_libvirt_supported_credentials guestfs_get_libvirt_requested_credentials guestfs_get_libvirt_requested_credential_prompt guestfs_get_libvirt_requested_credential_challenge

Hi! I started using wine (wine-20020122 compiled from source tarball) a couple of weeks ago to run a store-point-of-sale application. The idea is to port this windows application to linux. Before porting, we decided to check if the app could be emulated on linux with wine or recompiled with winelib. This is also necessary to run proprietary windows DLLs from third parties such as credit card

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 8 Apr 2003, werner maes wrote: > Can you tell me where to find the change that is necessary to enable dfs > on xp clients in samba 2.2.8? Has this fix been introduced in the latest > 2.2.8a? Here's the patch to fix msdfs & WinXP clients. This was not included in 2.2.8a (only security fixes there), but is already checked

I've trying to get dovecot-auth to talk to exim and have been running debugging on both sides. I've added the line: i_info("auth_client_input: client disconnected: %s", strerror(errno)); just after the "case -1" in the first switch statement in: auth-client-connection.c: auth_client_input() and get this in the logs: dovecot: Feb 27 13:35:09 Info: auth(default):

Hi Aki, > Aki Tuomi <aki.tuomi at open-xchange.com> hat am 30. M?rz 2020 16:23 geschrieben: > > Can you install dovecot-dbg to get debug symbols, open the core in gdb and run > > bt full > Full backtrace: :~# gdb /usr/lib/dovecot/auth core.juu GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version

Running Dovecot-1.1.5, I see this assertion failure: Panic: pop3-login: file sasl-server.c: line 75 (authenticate_callback): assertion failed: (client->auth_request == request) Error: pop3-login: Raw backtrace: 2 pop3-login 0x000000010000ac41 default_fatal_finish + 41 -> 3 pop3-login 0x000000010000acac i_syslog_fatal_handler +

The SOF ADSP vhost driver consists of two parts: a sound and a vhost part. This patch implements the vhost part of the driver. It handles QEMU communication with the vhost misc device and virtual queues to any VirtIO RPMsg guests. Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski at linux.intel.com> --- This is marked as an RFC / request for review, since it depends on other

Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the

Another crahs with backtrace: GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was

Hi, version: 1.2.10 OS: Debian unstable/x86_64 [118905.528497] dovecot-auth[3856]: segfault at 0 ip (null) sp 00007fff6666ad98 error 14 in dovecot-auth[400000+61000] 2010-02-26 22:17:45 dovecot: Error: child 3856 (auth) killed with signal 11 (core dumped) (gdb) bt full #0 0x0000000000000000 in ?? () No symbol table info available. #1 0x0000000000423b0e in vpopmail_lookup_vqp

GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as

Hi all, We moved our Dovecot installation first of all to have all folders and inboxes on NetApps via NFS (with indexes local) then from a physical Solaris 8 4-way UltraSparc server running Dovecot 1.2.5 (32-bit) to a virtualised Ubuntu 8.04 64-bit server with a single virtual processor (in VMWare ESX 3.5) running Dovecot 1.2.8 (64-bit). Since the change, many of our users have experienced

Seeing dovecot-auth segfault on amd64 dovecot is 1.2.4 pertinent details below: ldd /usr/local/libexec/dovecot/dovecot-auth linux-vdso.so.1 => (0x00007fffef1fe000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007fe8e6bae000) libvpopmail.so => /usr/lib/libvpopmail.so (0x00007fe8e6986000) libdl.so.2 => /lib/libdl.so.2 (0x00007fe8e6782000) librt.so.1 => /lib/librt.so.1

Hi everyone. I just got a copy of Win2k in and have been messing with it. Have a question, and have searched the archives for the answer, but didn't find it. Can Win2k domain logon to a pre-3.0.0 samba server? Or di I need to get TNG running? I can get NT4.0 boxes to authenticate and login fine (Samba pre-3.0.0), but Win2k keeps complaining: "The following error occurred validating

Yo Timo, did you say that login processes "just don't crash"? Found these while doing load/malformed data tests. Got the kernel patch allow_setid_cores working. Don't have time to check if they're exploitable. Probably time to get a gamma version out for people, eh? Cheers, Jared :)

Like with the previous commit, this replaces instances of: if (something_bad) { fprintf (stderr, "%s: error message\n", guestfs_int_program_name); exit (EXIT_FAILURE); } with: if (something_bad) error (EXIT_FAILURE, 0, "error message"); (except in a few cases were errno was incorrectly being ignored, in which case I have fixed that). It's slightly