...@kannel.org
To: Michael Zervakis mich...@zervakis.com
Cc: devel@kannel.org
Sent: Sunday, September 20, 2009 9:21 PM
Subject: Re: Bearerbox Panic after receiving CIFS/SMB request at
smsbox-port
Hi,
thanks for report. I just fixed this issue in cvs. Please retest.
Thanks,
Alexander Malysh
Am
:30 AM
Subject: Re: Bearerbox Panic after receiving CIFS/SMB request at smsbox-port
Hi Nikos,
hmm I saw your patch after I commited my version. sorry...
Thanks,
Alexander Maysh
Am 20.09.2009 um 21:58 schrieb Nikos Balkanas:
Hi Alex,
Which one? I just sent a patch about the very same thing 10
...@gmail.com
Cc: devel@kannel.org
Sent: Tuesday, September 22, 2009 10:30 AM
Subject: Re: Bearerbox Panic after receiving CIFS/SMB request at
smsbox-port
Hi Nikos,
hmm I saw your patch after I commited my version. sorry...
Thanks,
Alexander Maysh
Am 20.09.2009 um 21:58 schrieb Nikos Balkanas:
Hi
nbalka...@gmail.com
Cc: devel@kannel.org
Sent: Tuesday, September 22, 2009 11:54 AM
Subject: Re: Bearerbox Panic after receiving CIFS/SMB request at smsbox-port
Hi,
don't know why you don't see my patch, cvs up?
here is commited patch again:
diff --git a/gw/msg.c b/gw/msg.c
index 8fb5017
Hi,
thanks for report. I just fixed this issue in cvs. Please retest.
Thanks,
Alexander Malysh
Am 18.09.2009 um 17:00 schrieb Michael Zervakis:
Dear all,
During testing of Bearerbox using version cvs-20090506 I found that
if smsbox socket receives a CIFS/SMB request bearerbox panics. This
Hi Alex,
Which one? I just sent a patch about the very same thing 10 hrs ago.
BR,
Nikos
- Original Message -
From: Alexander Malysh amal...@kannel.org
To: Michael Zervakis mich...@zervakis.com
Cc: devel@kannel.org
Sent: Sunday, September 20, 2009 9:21 PM
Subject: Re: Bearerbox Panic
Dear all,
During testing of Bearerbox using version cvs-20090506 I found that if
smsbox socket receives a CIFS/SMB request bearerbox panics. This means
that a malicious user could easily crash bearerbox simply by scanning
the host (for example via nmap -sV).
2009-09-18 17:09:18 [2002] [5]
Giulio Harding wrote:
Giulio Harding wrote:
Further to this, we've had a few more incidents this past week which
shed a little more light on the problem:
Sometimes, a transmit/receive bind to a carrier (this has happened
with 2 different carriers now) goes strange: MTs will start queuing
on
Further to this, we've had a few more incidents this past week which
shed a little more light on the problem:
Sometimes, a transmit/receive bind to a carrier (this has happened
with 2 different carriers now) goes strange: MTs will start queuing
on Kannel, seemingly unable to be delivered,
I was quickly looking through the CVS code of today and wonder if this was maybe created by the fact that login is being rejected but enquire link tries to send its message anyway and then crashes. Could you tell me exactly on your CVS 20060727 version where is line 1811 in that version? On
Stuart's just left for the day, but I've picked out line 1811 in
function io_thread in gw/smsc/smsc_smpp.c from the source code we're using:
...
/* unbind
* Read so long as unbind_resp received or timeout passed.
Otherwise
we have
* double delivered
Hi All,
We recently had a situation where one of the carriers we are connecting to (2 separate SMSC's) had some unspecified issue and reconnected, this however caused the following panic
as one of the SMSC's had been turned off (upon communicating with the carrier it's been switched off for
12 matches
Mail list logo