November 2011 - sr-dev - kamailio.org

[tracker] Comment added: tls module crash on initialization when used together with the dialog module (Attachment added)
by sip-router 25 Nov '11

25 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#183 - tls module crash on initialization when used together with the dialog module User who did this - Øyvind Kolbu (kolbu) ---------- kamailio with debug=3. Still no core, as there is no crash. Kamailio exists properly when it encounters an error. ---------- One or more files have been attached. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=183#comment410 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Comment added: Double Free -- Crash/Coredump and possible security vulnerability
by sip-router 25 Nov '11

25 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#173 - Double Free -- Crash/Coredump and possible security vulnerability User who did this - Daniel-Constantin Mierla (miconda) ---------- I will have a fix shortly for shutdown case -- the problem is that dialog module is destroyed before tm module, there has to be an extra check for this case. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=173#comment409 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Comment added: tls module crash on initialization when used together with the dialog module
by sip-router 25 Nov '11

25 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#183 - tls module crash on initialization when used together with the dialog module User who did this - Daniel-Constantin Mierla (miconda) ---------- Log messages with debug=3 will be useful. For getting core, be sure you have 'ulimit -c unlimited' and parameter to kamailio '-w /path/to/writedir' (eventually run it as root). ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=183#comment408 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Comment added: Double Free -- Crash/Coredump and possible security vulnerability
by sip-router 25 Nov '11

25 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#173 - Double Free -- Crash/Coredump and possible security vulnerability User who did this - Bayan Towfiq (btowfiq) ---------- Sorry, this is a crash during shutdown only: I just tested it. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=173#comment407 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Comment added: Double Free -- Crash/Coredump and possible security vulnerability
by sip-router 25 Nov '11

25 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#173 - Double Free -- Crash/Coredump and possible security vulnerability User who did this - Bayan Towfiq (btowfiq) ---------- this crash was even with the simplified config snippet i posted above ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=173#comment406 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Comment added: Double Free -- Crash/Coredump and possible security vulnerability
by sip-router 25 Nov '11

25 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#173 - Double Free -- Crash/Coredump and possible security vulnerability User who did this - Bayan Towfiq (btowfiq) ---------- I also had a crash with dlgnewref -- it was not during shutdown: Program terminated with signal 11, Segmentation fault. #0 0x00007f11fb8bbe61 in dlg_lookup (h_entry=9097, h_id=1731333290) at dlg_hash.c:442 442 if (h_entry>=d_table->size) (gdb) bt #0 0x00007f11fb8bbe61 in dlg_lookup (h_entry=9097, h_id=1731333290) at dlg_hash.c:442 #1 0x00007f11fb8b2bf5 in unref_dlg_from_cb (t=<value optimized out>, type=1731333290, param=0x7fffb1193a40) at dlg_handlers.c:964 #2 0x00007f1200dea164 in run_trans_callbacks_internal (cb_lst=<value optimized out>, type=32768, trans=0x7f11eb1e1750, params=0x7fffb1193a40) at t_hooks.c:290 #3 0x00007f1200dea503 in run_trans_callbacks (type=32768, trans=<value optimized out>, req=<value optimized out>, rpl=0x0, code=0) at t_hooks.c:317 #4 0x00007f1200dcfc9a in free_cell (dead_cell=0x7f11eb1e1750) at h_table.c:152 #5 0x00007f1200dcfe68 in free_hash_table () at h_table.c:443 #6 0x00007f1200ddff15 in tm_shutdown () at t_funcs.c:126 #7 0x00000000004e25af in destroy_modules () at sr_module.c:783 #8 0x00000000004616ff in cleanup (show_status=1) at main.c:564 #9 0x000000000046236b in shutdown_children (show_status=1, sig=<value optimized out>) at main.c:706 #10 0x0000000000463382 in handle_sigs () at main.c:797 #11 0x000000000046451e in main_loop () at main.c:1741 #12 0x0000000000465f98 in main (argc=11, argv=0x7fffb1193ef8) at main.c:2508 (gdb) bt full #0 0x00007f11fb8bbe61 in dlg_lookup (h_entry=9097, h_id=1731333290) at dlg_hash.c:442 dlg = <value optimized out> d_entry = <value optimized out> #1 0x00007f11fb8b2bf5 in unref_dlg_from_cb (t=<value optimized out>, type=1731333290, param=0x7fffb1193a40) at dlg_handlers.c:964 dlg = <value optimized out> iuid = 0x2389 #2 0x00007f1200dea164 in run_trans_callbacks_internal (cb_lst=<value optimized out>, type=32768, trans=0x7f11eb1e1750, params=0x7fffb1193a40) at t_hooks.c:290 cbp = 0x7f11eb1b8620 backup_from = 0x8cb110 backup_to = 0x8cb118 backup_dom_from = 0x8cb120 backup_dom_to = 0x8cb128 backup_uri_from = 0x8cb100 backup_uri_to = 0x8cb108 backup_xavps = 0x8cb210 #3 0x00007f1200dea503 in run_trans_callbacks (type=32768, trans=<value optimized out>, req=<value optimized out>, rpl=0x0, code=0) at t_hooks.c:317 params = {req = 0x0, rpl = 0x0, param = 0x7f11eb1b8630, code = 0, flags = 0, branch = 0, t_rbuf = 0x0, dst = 0x0, send_buf = {s = 0x0, len = 0}} #4 0x00007f1200dcfc9a in free_cell (dead_cell=0x7f11eb1e1750) at h_table.c:152 b = <value optimized out> i = <value optimized out> rpl = <value optimized out> tt = <value optimized out> foo = <value optimized out> cbs = <value optimized out> __FUNCTION__ = "free_cell" #5 0x00007f1200dcfe68 in free_hash_table () at h_table.c:443 p_cell = 0x2389 tmp_cell = 0x7f11eaee5dc8 i = 598 __FUNCTION__ = "free_hash_table" #6 0x00007f1200ddff15 in tm_shutdown () at t_funcs.c:126 No locals. #7 0x00000000004e25af in destroy_modules () at sr_module.c:783 t = <value optimized out> foo = 0x7f12028fe0f0 __FUNCTION__ = "destroy_modules" #8 0x00000000004616ff in cleanup (show_status=1) at main.c:564 memlog = <value optimized out> __FUNCTION__ = "cleanup" #9 0x000000000046236b in shutdown_children (show_status=1, sig=<value optimized out>) at main.c:706 No locals. #10 0x0000000000463382 in handle_sigs () at main.c:797 chld = 0 chld_status = 134 memlog = <value optimized out> #11 0x000000000046451e in main_loop () at main.c:1741 i = 8 pid = <value optimized out> si = 0x0 si_desc = "udp receiver child=7 sock=70.167.xxx.xxx:5160\000\000\000\000\000@\020", '\000' <repeats 12 times>, "\016\b\000\000\000\000\000\000\000=\206=\220]֛&\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\300\v\215\000\000\000\000\000\"\000\000\000\000\000\000\000\000\000@\020", '\000' <repeats 11 times> #12 0x0000000000465f98 in main (argc=11, argv=0x7fffb1193ef8) at main.c:2508 cfg_stream = <value optimized out> c = <value optimized out> r = <value optimized out> tmp = 0x7fffb1195e83 "" ---Type <return> to continue, or q <return> to quit--- tmp_len = 0 port = <value optimized out> proto = <value optimized out> ret = <value optimized out> seed = 3986280357 rfd = <value optimized out> debug_save = 272629760 debug_flag = 34 dont_fork_cnt = 0 n_lst = 0x10400000 p = <value optimized out> ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=173#comment405 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Comment added: tls module crash on initialization when used together with the dialog module
by sip-router 25 Nov '11

25 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#183 - tls module crash on initialization when used together with the dialog module User who did this - Øyvind Kolbu (kolbu) ---------- No backtrace as there is no crash. Any other debug info I can provide? ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=183#comment404 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Comment added: Double Free -- Crash/Coredump and possible security vulnerability
by sip-router 25 Nov '11

25 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#173 - Double Free -- Crash/Coredump and possible security vulnerability User who did this - Brandon Armstead (CRYY2010) ---------- Daniel, I believe the following backtrace I'm going to post is from the "work around" crash. As for restarting the SIP server --- this is possible but ONLY after a crash - so not sure if somehow the core file was still being generated and kamailio hadn't completely shutdown... **** BACK TRACE **** #0 0x00007fd59be0fed5 in raise () from /lib/libc.so.6 #1 0x00007fd59be113f3 in abort () from /lib/libc.so.6 #2 0x0000000000528679 in qm_free (qm=0x7fd584f78000, p=0x7fd585269fe8, file=0x7fd599fd66bb "dialog: dlg_hash.c", func=0x7fd599fd7022 "destroy_dlg", line=215) at mem/q_malloc.c:447 #3 0x00007fd599fbe224 in destroy_dlg (dlg=0x7fd58526c828) at dlg_hash.c:215 #4 0x00007fd599fc069b in unref_dlg (dlg=0x7fd58526c828, cnt=514) at dlg_hash.c:584 #5 0x00007fd599fc5a94 in profile_cleanup (msg=<value optimized out>, flags=<value optimized out>, param=0x6) at dlg_profile.c:317 #6 0x00000000004bc9d1 in exec_post_script_cb (msg=0xe04b18, type=<value optimized out>) at script_cb.c:195 #7 0x000000000049598d in receive_msg ( buf=0x8a4300 "INVITE sip:RURI@KAMAILIO SIP/2.0\r\nRecord-Route: <sip:KAMAILIO_REGISTRAR;lr=on;ftag=658fa5a34456db0do0>\r\nVia: SIP/2.0/UDP KAMAILIO_REGISTRAR;branch=z9hG4bK8177.1bcb9436.0\r\nVia: SIP/2."..., len=<value optimized out>, rcv_info=0x7fffa4763210) at receive.c:221 #8 0x000000000051c9d1 in udp_rcv_loop () at udp_server.c:532 #9 0x0000000000464b35 in main_loop () at main.c:1560 #10 0x0000000000467fa3 in main (argc=<value optimized out>, argv=0x7fffa47634d8) at main.c:2410 #0 0x00007fd59be0fed5 in raise () from /lib/libc.so.6 No symbol table info available. #1 0x00007fd59be113f3 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x0000000000528679 in qm_free (qm=0x7fd584f78000, p=0x7fd585269fe8, file=0x7fd599fd66bb "dialog: dlg_hash.c", func=0x7fd599fd7022 "destroy_dlg", line=215) at mem/q_malloc.c:447 f = <value optimized out> size = <value optimized out> #3 0x00007fd599fbe224 in destroy_dlg (dlg=0x7fd58526c828) at dlg_hash.c:215 ret = <value optimized out> __FUNCTION__ = "destroy_dlg" #4 0x00007fd599fc069b in unref_dlg (dlg=0x7fd58526c828, cnt=514) at dlg_hash.c:584 d_entry = <value optimized out> #5 0x00007fd599fc5a94 in profile_cleanup (msg=<value optimized out>, flags=<value optimized out>, param=0x6) at dlg_profile.c:317 No locals. #6 0x00000000004bc9d1 in exec_post_script_cb (msg=0xe04b18, type=<value optimized out>) at script_cb.c:195 cb = (struct script_cb *) 0xe19c08 flags = 2147483649 #7 0x000000000049598d in receive_msg ( buf=0x8a4300 "INVITE sip:RURI@KAMAILIO SIP/2.0\r\nRecord-Route: <sip:KAMAILIO_REGISTRAR;lr=on;ftag=658fa5a34456db0do0>\r\nVia: SIP/2.0/UDP KAMAILIO_REGISTRAR;branch=z9hG4bK8177.1bcb9436.0\r\nVia: SIP/2."..., len=<value optimized out>, rcv_info=0x7fffa4763210) at receive.c:221 msg = (struct sip_msg *) 0xe04b18 ctx = {rec_lev = 8, run_flags = 0, last_retcode = 0, jmp_env = {{__jmpbuf = {9420032, 5082547, 140735952597839, 0, 140555419815472, 140555429711872, 8, 4294967295}, __mask_was_saved = 9420904, __saved_mask = {__val = {8357392, 140735952597528, 14699168, 4294967245, 140555429709464, 0, 140555427602890, 1, 0, 140557099728895, 4250091, 140555419815472, 14775720, 14699160, 140555427627026, 16}}}}} ret = <value optimized out> inb = { s = 0x8a4300 "INVITE sip:RURI@KAMAILIO SIP/2.0\r\nRecord-Route: <sip:KAMAILIO_REGISTRAR;lr=on;ftag=658fa5a34456db0do0>\r\nVia: SIP/2.0/UDP KAMAILIO_REGISTRAR;branch=z9hG4bK8177.1bcb9436.0\r\nVia: SIP/2."..., len = 1077} __FUNCTION__ = "receive_msg" #8 0x000000000051c9d1 in udp_rcv_loop () at udp_server.c:532 len = 1077 from = (union sockaddr_union *) 0xe04a98 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {2512315459, 8}, addr32 = {2512315459, 0, 8, 0}, addr16 = {58435, 38334, 0, 0, 8, 0, 0, 0}, addr = "C��\225\000\000\000\000\b\000\000\000\000\000\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = {162653251, 0}, addr32 = {162653251, 0, 0, 0}, addr16 = {58435, 2481, 0, 0, 0, 0, 0, 0}, addr = "C��\t", '\0' <repeats 11 times>}}, src_port = 5060, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\023�C��\225\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 2512315459}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 2512315459, sin6_addr = {in6_u = {u6_addr8 = '\0' <repeats 15 times>, u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0xe175a8, proto = 1 '\001'} buf = "INVITE sip:RURI@KAMAILIO SIP/2.0\r\nRecord-Route: <sip:KAMAILIO_REGISTRAR;lr=on;ftag=658fa5a34456db0do0>\r\nVia: SIP/2.0/UDP KAMAILIO_REGISTRAR;branch=z9hG4bK8177.1bcb9436.0\r\nVia: SIP/2."... __FUNCTION__ = "udp_rcv_loop" #9 0x0000000000464b35 in main_loop () at main.c:1560 i = 7 pid = <value optimized out> si = (struct socket_info *) 0xe175a8 si_desc = "udp receiver child=7 sock=KAMAILIO:5060\000\000\000\000\000�o�\000\000\000\000\000\001\000\000\000�\177", '\0' <repeats 18 times>, "t\000\000\000\000\000\000\000\030��\204\001\000\000\000\001\000\000\000\000\000\000\000\003", '\0' <repeats 22 times> #10 0x0000000000467fa3 in main (argc=<value optimized out>, argv=0x7fffa47634d8) at main.c:2410 cfg_stream = (FILE *) 0x2316010 c = <value optimized out> r = <value optimized out> tmp = 0x7fffa4764f76 "" tmp_len = 32725 port = <value optimized out> proto = <value optimized out> ret = <value optimized out> seed = 427627096 rfd = 4 debug_save = <value optimized out> debug_flag = 0 dont_fork_cnt = 0 n_lst = <value optimized out> p = <value optimized out> ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=173#comment403 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Comment added: tls module crash on initialization when used together with the dialog module
by sip-router 25 Nov '11

25 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#183 - tls module crash on initialization when used together with the dialog module User who did this - Daniel-Constantin Mierla (miconda) ---------- Can you attach the backtrace? ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=183#comment402 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[tracker] Task opened: tls module crash on initialization when used together with the dialog module
by sip-router 25 Nov '11

25 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Øyvind Kolbu (kolbu) Attached to Project - sip-router Summary - tls module crash on initialization when used together with the dialog module Task Type - Bug Report Category - dialog Status - Assigned Assigned To - Timo Reimann Operating System - Linux Severity - Medium Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - I've tried to enable the tls module, but if the dialog module is loaded the tls module crash. If I disable the dialog module tls loads fine. Note that if «enable_tls» is «no» Kamailio doesn't crash. Tested both on latest 3.2 and master branch. Built only with db_postgres and tls modules. Running on 32-bit RHEL 5. Error message from Kamailio: Nov 25 18:49:45 voipt2-edge1 /nett/kamailio/current/sbin/kamailio[21067]: INFO: tls [tls_init.c:511]: tls: _init_tls_h: compiled with openssl version "OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008" (0x0090802f), kerberos support: on, compression: on Nov 25 18:49:45 voipt2-edge1 /nett/kamailio/current/sbin/kamailio[21067]: INFO: tls [tls_init.c:519]: tls: init_tls_h: installed openssl library version "OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008" (0x0090802f), kerberos support: on, zlib compression: on compiler: gcc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -I/usr/kerberos/include -DL_ENDIAN -DTERMIO -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 -mtune=generic -fasynchronous-unwind-tables -Wa,--noexecstack -DOPENSSL_USE_NEW_FUNCTIONS -fno-strict-aliasing -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM Nov 25 18:49:45 voipt2-edge1 /nett/kamailio/current/sbin/kamailio[21067]: ERROR: tls [tls_init.c:550]: Unable to set the memory allocation functions Nov 25 18:49:45 voipt2-edge1 /nett/kamailio/current/sbin/kamailio[21067]: : <core> [main.c:2469]: could not initialize tls, exiting... # /nett/kamailio/current/sbin/kamailio -V version: kamailio 3.3.0-dev2 (i386/linux) 629970 flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 629970 compiled on 18:42:26 Nov 25 2011 with gcc 4.1.2 Example config which will cause Kamailio to crash: #!KAMAILIO debug=3 log_stderror=no log_facility=LOG_LOCAL0 fork=yes children=6 alias="voipt2-edge1.uio.no" alias="129.240.253.133" port=5060 listen=udp:129.240.253.133:5060 listen=tcp:129.240.253.133:5060 enable_tls=yes mpath="/nett/kamailio/current/lib/kamailio/modules_k/:/nett/kamailio/current/lib/kamailio/modules/" #!define VOIP_DATA4 "postgres://redacted" loadmodule "db_postgres.so" # POSTGRES-backend for database API module loadmodule "tm.so" # Transaction (stateful) module loadmodule "rr.so" # Record-Route and Route module loadmodule "pv.so" # Module holding Pseudo-Variables loadmodule "dialog.so" # Dialog support module - For busy level handling loadmodule "tls.so" modparam("tls", "private_key", "/nett/edge/ssl/common.key") modparam("tls", "certificate", "/nett/edge/ssl/voipt2-edge1.uio.no.crt") modparam("tls", "ca_list", "/nett/edge/ssl/uninett-chain.pem") modparam("tls", "tls_method", "TLSv1") modparam("dialog", "dlg_flag", 3) modparam("dialog", "default_timeout", 21600) modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "db_url", VOIP_DATA4) modparam("dialog", "db_mode", 1) modparam("dialog", "table_name", "dialog2") modparam("dialog", "vars_table_name", "dialog_vars2") modparam("dialog", "profiles_with_value", "busy") route{ exit; } More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=183 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0