View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000784unrealircdpublic2003-03-09 19:582003-11-20 19:46
Reportercomrade Assigned Tocodemastr 
PrioritynormalSeveritycrashReproducibilitysometimes
Status closedResolutionfixed 
Summary0000784: SSL linking crash
DescriptionThis problem occurs in all Unreal versions I've tried (3.1.3, 3.1.5.1-Valek, 3.2-beta15) and it occurs when trying to link servers with SSL enabled. I've tracked down the bug and it is in ssl.c:ssl_get_cipher():362:switch(ssl->session->ssl_version). Coredumps, probably null pointer in that statement? Quick fix to it is just to comment all lines until and including strcat(buf, "-");. Only occurs on some systems, on others it can get version number just fine. First started occurring when I've updated openssl to 0.9.7a.
3rd party modules

Activities

codemastr

2003-03-10 00:20

reporter   ~0001842

Can you give us gdb backtrace output? If you don't give us this info, there is nothing we can do. Knowing WHERE it crashed and knowing WHY it crashed are two different things.

syzop

2003-03-10 16:27

administrator   ~0001852

That would help indeed (in other words: we can't help without).
I tested it here and it links fine
                     using OpenSSL 0.9.7a Feb 19 2003

[17:25:11] -maintest.hok.net- *** Notice -- (link) Secure link maintest.hok.net -> testlink.hok.net[@127.0.0.1.42557] established (SSLv3-AES256-SHA-256bits)

codemastr

2003-03-12 21:20

reporter   ~0001907

Last edited: 2003-03-12 21:25

 I think I found the cause of this, sorry Syzop, stealing your bug ;)

For clients I notice it is if (IsSecure(sptr) && sptr->ssl)
for servers it is just if (IsSecure(cptr)) perhaps that could cause a problem?

edited on: 03-12 21:25

syzop

2003-03-12 21:24

administrator   ~0001908

good ;).

comrade

2003-03-12 21:24

reporter   ~0001909

What do you think it is?

codemastr

2003-04-08 23:50

reporter   ~0002190

Yes I know it has been a long time since I talked to you, but I think I might have fixed this problem. If you are still having the problem, can you upgrade to the current CVS version and tell me if it still exists?

codemastr

2003-04-11 02:23

reporter   ~0002237

Fixed in current CVS.

Issue History

Date Modified Username Field Change
2003-04-08 23:50 codemastr Note Added: 0002190
2003-04-11 02:23 codemastr Status assigned => resolved
2003-04-11 02:23 codemastr Resolution open => fixed
2003-04-11 02:23 codemastr Note Added: 0002237
2003-11-20 19:46 syzop Status resolved => closed