From: Stephen Hemminger <stephen@networkplumber.org>
To: "Jaroslav Šafka" <jaroslav.safka@tieto.com>
Cc: netdev@vger.kernel.org
Subject: Re: iproute2 small patches for xfrm
Date: Fri, 1 Aug 2014 09:05:08 -0700 [thread overview]
Message-ID: <20140801090508.384adbc1@haswell.linuxnetplumber.net> (raw)
In-Reply-To: <2141002.LfKmUBSlWz@ul001176>
On Fri, 01 Aug 2014 13:16:09 +0200
Jaroslav Šafka <jaroslav.safka@tieto.com> wrote:
> Hi,
> I found the tool "ip xfrm" is not able to add "cipher_null" because there is
> no possibility to set key with zero length.
>
> I solved it by this change:
>
> - if (slen > 2 && strncmp(key, "0x", 2) == 0) {
> + if (slen >= 2 && strncmp(key, "0x", 2) == 0) {
>
> By this change you can specify key as "0x" which will pass for key existence
> and set key len to 0.
>
> this patch is against version iproute2-3.14.0
>
> Second patch enable use proto ip. Because it is supported by kernel.
>
> Have a nice day :)
>
> Regards
> Jarek
Please format patches in same manner as kernel patches as described
in Documentation/SubmittingPatches. One patch per email; email with [PATCH]
in subject line; and please don't use attachments if possible.
prev parent reply other threads:[~2014-08-01 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 11:16 iproute2 small patches for xfrm Jaroslav Šafka
2014-08-01 16:05 ` Stephen Hemminger [this message]
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=20140801090508.384adbc1@haswell.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=jaroslav.safka@tieto.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.