silc-server 1.1.2 segfault: bug or config error?

Stuart Henderson stu at spacehopper.org
Thu Mar 27 00:14:22 CET 2008


I'm running silc-server 1.1.2 on OpenBSD -current, and tried to
configure a backup router which refused client connections so
left out Client { } in silcd.conf. This results in a segfault as
soon as a server connects, which doesn't happen if Client { } is
included.

No problem for me either way as I have my server running now, but
I thought I'd mention it so it can either be documented, fixed, or
at least in the list archives for someone else who looks.

thanks (-:

silc_schedule_task_del_by_context:836: Unregister task by context
silc_server_accept_completed:2528: Setting keys into use
silc_cipher_alloc:193: Allocating new cipher object
silc_cipher_alloc:193: Allocating new cipher object
silc_hmac_alloc:192: Allocating new HMAC
silc_hash_alloc:178: Allocating new hash sha256
silc_hmac_alloc:192: Allocating new HMAC
silc_hash_alloc:178: Allocating new hash sha256
silc_hash_alloc:178: Allocating new hash sha256
silc_packet_set_keys:1226: Setting new keys to packet stream 0x7c7c2d00
<boom>

(gdb) bt
#0  0x1c0794ab in silc_pkcs_public_key_copy (public_key=0x0)
    at silcpkcs.c:637
#1  0x1c01b604 in silc_server_accept_completed (ske=0x81db3200, 
    status=SILC_SKE_STATUS_OK, prop=0x7de22b20, keymat=0x85730440, 
    rekey=0x81db9c70, context=0x84bbbf80) at server.c:2543
#2  0x1c09ee0f in silc_ske_completion (ske=0x81db3200) at silcske.c:969
#3  0x1c099c17 in silc_ske_st_responder_end (fsm=0x81db3264, 
    fsm_context=0x81db3200, state_context=0x0) at silcske.c:2333
#4  0x1c06a002 in silc_fsm_run (schedule=0x84bbb800, 
    app_context=0x80c21200, type=0, fd=0, context=0x81db3264)
    at silcfsm.c:429
#5  0x1c069d15 in silc_fsm_continue_sync (fsm=0x81db3264)
    at silcfsm.c:309
#6  0x1c09d065 in silc_ske_packet_receive (engine=0x84bbbe80, 
    stream=0x84bbbf80, packet=0x85730140, callback_context=0x81db3200, 
    app_context=0x7da70000) at silcske.c:121
#7  0x1c050b89 in silc_packet_dispatch (packet=0x85730140)
    at silcpacket.c:2053
#8  0x1c05185d in silc_packet_read_process (stream=0x84bbbf80)
    at silcpacket.c:2317
#9  0x1c053454 in silc_packet_stream_io (stream=0x85730300, 
    status=SILC_STREAM_CAN_READ, context=0x84bbbf80) at silcpacket.c:438
#10 0x1c0a53a5 in silc_socket_stream_io (schedule=0x84bbb800, 
    app_context=0x80c21200, type=SILC_TASK_READ, fd=10, 
    context=0x85730300) at silcunixsocketstream.c:36
#11 0x1c06326d in silc_schedule_dispatch_fd (schedule=0x84bbb800)
    at silcschedule.c:61
#12 0x1c063714 in silc_schedule_iterate (schedule=0x84bbb800, 
    timeout_usecs=-1) at silcschedule.c:455
#13 0x1c061ee5 in silc_schedule (schedule=0x84bbb800)
    at silcschedule.c:499
#14 0x1c01321a in silc_server_run (server=0x80c21200) at server.c:1187
#15 0x1c008c34 in main (argc=3, argv=0xcfbfb4e8) at silcd.c:753




More information about the silc-users mailing list