That MIME module has had its issues, so I would not be surprised that
it crashes on malformed input. Without a log it is not easy to find
offending code (i.e. code that should properly handle such
problems)... Let me know if you are able to reproduce it...
On Oct 03, 2007, at 17:31, Gabi Mahu wrote:
Thank you for your reply, Paul.
So, I understand that there are only two options for a "bad MMS
scenario"
a) mmsbox crashes
b) mmsbox discards the message and creates a http response with a
4xx code and an error message,
the choice between a) and b) depending on the actual content of the
MMS.
Unfortunately, I have no logs with mmsbox crashing, but I remember
that when we encountered the situation described in my previous
mail, the one with the multipart content missing, we solved it with
a small hack in mime.c from the kannel sources. If I am not
mistaking, there was a method, mime_something_to_entity, that at
some point parses the boundary blocks in a loop. In that loop,
since our actual block was only "\r\n\r\n", some string operations
caused the segmentation fault. Also, just to be on the safe side,
we surrounded the recursive call in a string length sanity check
for the boundary block . That did the trick, but it was just a
small local fix.
I hope that this can still help you somehow.
Thanks again,
Gabi
Paul Bagyenda <[EMAIL PROTECTED]> wrote:
The answer is it depends. In general it should return an error, but
I would not rule out crashing. If you have a trace of such a crash,
pray share as that helps improve the code.
Paul.
On 10/3/07, Gabi Mahu <[EMAIL PROTECTED]> wrote:
Hello all,
I am using mmsbox, mmsproxy and mmsrelay without any problems in a
small project, a small application that sends a constructed MMS to
mmsbox. I just have some questions regarding the behavior of Mbuni
when a malformed MMS is sent to mmsbox. When I say malformed, I
mean any kind of multipart headers or multipart content errors.
At some point, due to some bugs, the MMS message that was created
by the application was corrupted. Everything that was between the
multipart boundaries (where headers and content for an images
should have been, for example...), except the pair of \r\n, was
missing. Mmsbox crashed due to a segmentation fault, caused by some
string manipulation for the empty multipart.
The code that generates the MMS is out of my reach now, so I can't
answer my question by modifying the way the MMS is created and
observing mmsbox reactions. And the application seams to works
without a flaw now, so.... That is way I am writing this email.
So, if someone could please explain how does mmsbox react when a
corrupt MMS arrives? It forwards the MMS to mmsc, even though it
doesn't "understand" it (it can't parse it, or finds some bad
headers...), and responds with 200ok, or discards the message and
answers with some 4xx code, or what? (I did leave out "it crashes"
on purpose, because I hope that is not the case...)
Thank you for your time
Gabi Mahu
Don't let your dream ride pass you by. Make it a reality with
Yahoo! Autos.
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
Check out the hottest 2008 models today at Yahoo! Autos.
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
