> -----Original Message----- > From: Stipe Tolj [mailto:[EMAIL PROTECTED]] > Sent: Sunday, June 02, 2002 10:48 AM > To: [EMAIL PROTECTED] > Subject: [RFC] timeline for stable 1.2.0 > > > Hi all, > > can we do some voting for releasing the stable version 1.2.0 from the > current cvs head tree, please?! > > I'd like to hear votes from anyone who is a) core developer, b) core > productive user of Kannel and vetos from anyone who see major bugs in > current cvs tree. > > If there is noone claiming to have segmenation faults or similar on > production environments running cvs and we can get rid of the > outstanding release showstopper from STATUS (Stefan, comments > please?!) then I'd like to suggest releasing 1.2.0 stable upcoming > week.
We at m-Wise encountered a crash problem when sending messages using SMPP. we tracked
it to the new validity/defered patch which uses a too short a buffer for composing the
time stamp. Attached is a patch to fix that, as well as cleaning up handling of error
messages in NACK responses - something which was a major issue for us as it caused us
to fail a conformity test.
The problem with the buffer that it is staticly defined as 16 byte long, while 17
bytes are needed (including the terminating NULL) to store the time stamp. sprintf is
used to fill the buffer, which always appends the terminating NULL, over flowing the
buffer and rewriting something (in our case - the memory location holding the pointer
to the PDU). The fix we did is to use Octstr to store the buffer and to build it using
octstr_format.
I'd like to get at least the buffer overflow patch to be submitted before 1.2 as it's
a major show stopper.
--
Oded Arbel
m-Wise Inc.
[EMAIL PROTECTED]
(972)-67-340014
(972)-9-9581711 (ext: 116)
::..
This book fills a much-needed gap.
-- Moses Hadas in a review
smsc_smpp.patch
Description: smsc_smpp.patch
