Description of problem: When trying to create a user with DB authentication using zarafa-admin, the zarafa-server crashes with a SIGSEGV error. Version-Release number of selected component (if applicable): libmapi-6.30.10-1.fc12.x86_64 zarafa-monitor-6.30.10-1.fc12.x86_64 zarafa-server-6.30.10-1.fc12.x86_64 zarafa-ical-6.30.10-1.fc12.x86_64 php-mapi-6.30.10-1.fc12.x86_64 zarafa-6.30.10-1.fc12.x86_64 zarafa-dagent-6.30.10-1.fc12.x86_64 zarafa-debuginfo-6.30.10-1.fc12.x86_64 zarafa-spooler-6.30.10-1.fc12.x86_64 zarafa-gateway-6.30.10-1.fc12.x86_64 zarafa-utils-6.30.10-1.fc12.x86_64 zarafa-common-6.30.10-1.fc12.x86_64 zarafa-client-6.30.10-1.fc12.x86_64 zarafa-webaccess-6.30.10-1.fc12.noarch How reproducible: Everytime, see above and below. Steps to Reproduce: 1. yum --enablerepo=updates-testing install zarafa 2. gdb /usr/bin/zarafa-server 3. run -F 4. (on another console, type): "zarafa-admin -c tux -e tux@localhost -f 'Tux' -p secure" Actual results: SIGSEGV error in zarafa-server with DB authentication Expected results: No segmentation fault when using zarafa-admin Additional info: Mo 22 Feb 2010 13:21:13 CET: Caught SIGSEGV (6), traceback: Mo 22 Feb 2010 13:21:13 CET: 0x000000004735ab /usr/bin/zarafa-server(_Z7sigsegvi+0x4b) [0x4735ab] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb80f0f0 /lib64/libpthread.so.0() [0x39fb80f0f0] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb0326c5 /lib64/libc.so.6(gsignal+0x35) [0x39fb0326c5] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb033ea5 /lib64/libc.so.6(abort+0x175) [0x39fb033ea5] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb06f0f3 /lib64/libc.so.6() [0x39fb06f0f3] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb0f75e7 /lib64/libc.so.6(__fortify_fail+0x37) [0x39fb0f75e7] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb0f5600 /lib64/libc.so.6() [0x39fb0f5600] Mo 22 Feb 2010 13:21:13 CET: 0x00000000613dbb /usr/bin/zarafa-server(_Z13ABIDToEntryIDP4soapjRKSsmP17xsd__base64Binary+0x13b) [0x613dbb] Mo 22 Feb 2010 13:21:13 CET: 0x000000004d2304 /usr/bin/zarafa-server(_Z12GetABEntryIDjP4soapP17xsd__base64Binary+0xf4) [0x4d2304] Mo 22 Feb 2010 13:21:13 CET: 0x00000000519f14 /usr/bin/zarafa-server(_Z19ns__resolveUsernameP4soapyPcP19resolveUserResponse+0x444) [0x519f14] Mo 22 Feb 2010 13:21:13 CET: 0x0000000060332d /usr/bin/zarafa-server(_Z30soap_serve_ns__resolveUsernameP4soap+0xad) [0x60332d] Mo 22 Feb 2010 13:21:13 CET: 0x0000000060e244 /usr/bin/zarafa-server(_Z10soap_serveP4soap+0xa4) [0x60e244] Mo 22 Feb 2010 13:21:13 CET: 0x00000000479758 /usr/bin/zarafa-server(_ZN22ECSoapServerConnection15process_requestEPv+0x78) [0x479758] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb806a3a /lib64/libpthread.so.0() [0x39fb806a3a] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb0de67d /lib64/libc.so.6(clone+0x6d) [0x39fb0de67d] Mo 22 Feb 2010 13:21:13 CET: When reporting this traceback, please include Linux distribution name, system architecture and Zarafa version. Mo 22 Feb 2010 13:21:13 CET: Caught SIGSEGV (11), traceback: Mo 22 Feb 2010 13:21:13 CET: 0x000000004735ab /usr/bin/zarafa-server(_Z7sigsegvi+0x4b) [0x4735ab] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb80f0f0 /lib64/libpthread.so.0() [0x39fb80f0f0] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb0d73e3 /lib64/libc.so.6(__select+0x33) [0x39fb0d73e3] Mo 22 Feb 2010 13:21:13 CET: 0x0000000047837a /usr/bin/zarafa-server(_ZN22ECSoapServerConnection6SelectEv+0x12a) [0x47837a] Mo 22 Feb 2010 13:21:13 CET: 0x00000000477375 /usr/bin/zarafa-server(_Z14running_serverPcS_+0x1f95) [0x477375] Mo 22 Feb 2010 13:21:13 CET: 0x00000000477dec /usr/bin/zarafa-server(main+0x5ec) [0x477dec] Mo 22 Feb 2010 13:21:13 CET: 0x000039fb01eb1d /lib64/libc.so.6(__libc_start_main+0xfd) [0x39fb01eb1d] Mo 22 Feb 2010 13:21:13 CET: 0x000000004731d9 /usr/bin/zarafa-server() [0x4731d9] Mo 22 Feb 2010 13:21:13 CET: When reporting this traceback, please include Linux distribution name, system architecture and Zarafa version.
http://koji.fedoraproject.org/koji/taskinfo?taskID=2005731 seems to contain a working fix, please verify. Note that you need to drop your Zarafa database again, because otherwise you can't create the same user (gets corrupted at the zarafa-server crash as it seems).
Created attachment 395505 [details] Remerged changeset of Subversion Revision 18952 from 6.40.0 (trunk) to 6.30.10
I saw it and I'm gonna try...but looking at the version (not sure.), should be better to increase the revision number? 6.30.10-2 instead of having 6.30.10-1 Thanks Luca
Yes, you're of course right - sorry. Will do that the next time then. The cause for this issue seems to be, that Zarafa doesn't honor a long-time Fedora feature in their code: http://fedoraproject.org/wiki/Security/Features#Compile_Time_Buffer_Checks_.28FORTIFY_SOURCE.29
zarafa-6.30.10-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/zarafa-6.30.10-2.fc13
zarafa-6.30.10-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/zarafa-6.30.10-2.fc12
zarafa-6.30.10-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/zarafa-6.30.10-2.fc11
zarafa-6.30.10-2.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/zarafa-6.30.10-2.el5
zarafa-6.30.10-2.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update zarafa'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F13/FEDORA-2010-2816
zarafa-6.30.10-2.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update zarafa'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/EL-5/FEDORA-EPEL-2010-2312
zarafa-6.30.10-2.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/EL-5/FEDORA-EPEL-2010-2312
zarafa-6.30.10-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/F13/FEDORA-2010-2816
zarafa-6.30.10-2.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update zarafa'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-2948
zarafa-6.30.10-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update zarafa'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-2958
zarafa-6.30.10-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/F11/FEDORA-2010-2958
zarafa-6.30.10-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/F12/FEDORA-2010-2948
zarafa-6.30.10-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-6.30.10-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-6.30.10-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-6.30.10-2.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.