netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denis Joseph Barrow <D.Barow-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org>
To: "Németh Tamás" <nice-OZwXound/Z2+mM1/5BeW/g@public.gmane.org>
Cc: Filip Aben <f.aben-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org>,
	Linux USB kernel mailing list
	<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux netdev Mailing list
	<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: 2 bugs found in Cisco vpnclient-4.8.02.0030
Date: Tue, 09 Sep 2008 14:11:25 +0200	[thread overview]
Message-ID: <48C667ED.9060206@option.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 651 bytes --]

Hi Tamas,
I've got the vpn client going over ethernet but not yet over the hso device.
I found 2 idiotic substantial bugs in the vpn client one which caused
the crash in linuxcniapi.c as you were seeing
You'll note that in some places the code was looping to <MAX_INTERFACES
& other places to <=MAX_INTERFACES, this was flying over the edge
of the array.
These bugs are not unique to the hso driver they just happened to
manifest there.

Let me know if you still find crashes somehow, post them to me & more importantly
let me know if you get hso going over vpn.

Please find some way to get the bugfixes back to Cisco.

-- 
best regards,
D.J. Barrow

[-- Attachment #2: vpnclient.patch --]
[-- Type: text/x-diff, Size: 838 bytes --]

--- cisco-vpn-client.orig/vpnclient-4.8.02.0030/interceptor.c	2008-06-23 18:59:12.000000000 +0200
+++ cisco-vpn-client/vpnclient-4.8.02.0030/interceptor.c	2008-09-09 13:54:02.000000000 +0200
@@ -502,7 +502,7 @@
 {
     int i;
     
-    for (i=0; i <= MAX_INTERFACES; i++)
+    for (i=0; i < MAX_INTERFACES; i++)
     {
         BINDING *b = &Bindings[i];
         if (b->pDevice && (dev->ifindex == b->pDevice->ifindex))
--- cisco-vpn-client.orig/vpnclient-4.8.02.0030/linuxcniapi.c	2008-06-23 18:59:12.000000000 +0200
+++ cisco-vpn-client/vpnclient-4.8.02.0030/linuxcniapi.c	2008-09-09 13:37:33.000000000 +0200
@@ -577,7 +577,7 @@
 {
     int i;
     
-    for (i=0; i <= MAX_INTERFACES; i++)
+    for (i=0; i < MAX_INTERFACES; i++)
     {
         BINDING *b = &Bindings[i];
         if (b->pDevice && (iIndex == b->pDevice->ifindex))

                 reply	other threads:[~2008-09-09 12:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48C667ED.9060206@option.com \
    --to=d.barow-x9gzzrpc1qbqt0dzr+alfa@public.gmane.org \
    --cc=f.aben-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nice-OZwXound/Z2+mM1/5BeW/g@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).