public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <pcg@goof.com ( Marc) (A.) (Lehmann )>
To: linux-kernel@vger.kernel.org
Cc: Marco Maisenhelder <hi41@iss.mach.uni-karlsruhe.de>, oesi@schmorp.de
Subject: 2.4.13-ac5 && vtun not working
Date: Tue, 30 Oct 2001 02:17:40 +0100	[thread overview]
Message-ID: <20011030021740.A8708@schmorp.de> (raw)

After upgrading to linux-2.4.13-ac5, everything seems to work, except all
my vtun tunnels.

a _lot_ of searching revealed this code fragment:

        /*
         * Verify the string as this thing may have come from
         * the user.  There must be one "%d" and no other "%"
         * characters.
         */
        p = strchr(name, '%');
        if (!p || p[1] != 'd' || strchr(p+2, '%'))
                return -EINVAL;

Well, obviously my devicename _do_ come "from the user", as I really like
to name my tun devices (and everything else). The problem is that vtund
passes in "tun2" as devicename, which does not contain a "%d".

Maybe this piece of code is designed to fix security problems, but it
keeps vtund from working properly.

How about this change?

-        if (!p || p[1] != 'd' || strchr(p+2, '%'))
+        if (p && (p[1] != 'd' || strchr(p+2, '%')))


-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg@goof.com      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |

             reply	other threads:[~2001-10-30  1:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  1:17 Lehmann  [this message]
2001-10-30  1:39 ` 2.4.13-ac5 && vtun not working Lehmann 
2001-10-30  1:48 ` Maksim Krasnyanskiy
2001-10-30  1:53   ` David S. Miller
2001-10-31  0:05     ` Lehmann 
2001-10-31  8:30       ` David S. Miller
2001-10-31  9:43         ` Lehmann 
2001-10-31 17:55         ` Maksim Krasnyanskiy
2001-11-06 23:32           ` David S. Miller
2001-11-06 23:53           ` Maksim Krasnyanskiy

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=20011030021740.A8708@schmorp.de \
    --to=pcg@goof.com \
    --cc=hi41@iss.mach.uni-karlsruhe.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oesi@schmorp.de \
    /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