From: Felix von Leitner <felix-kernel@fefe.de>
To: linux-kernel@vger.kernel.org
Subject: twofish missing in ipsec kernel headers
Date: Wed, 13 Aug 2003 17:41:05 +0200 [thread overview]
Message-ID: <20030813154105.GA30999@codeblau.de> (raw)
I just saw that ipsec-tools did not let me use twofish as cipher, and
further grepping showed that ipsec-tools does support it, but the Linux
kernel headers (in particular <linux/pfkeyv2.h>) do not define the
necessary constant, SADB_X_EALG_TWOFISHCBC.
Please add this constant and the necessary glue code to the IPsec layer!
Felix
reply other threads:[~2003-08-13 15:43 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=20030813154105.GA30999@codeblau.de \
--to=felix-kernel@fefe.de \
--cc=linux-kernel@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.