From: Dale Amon <amon@vnl.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Crypto patches for losetup
Date: Thu, 15 Feb 2001 18:21:02 +0000 [thread overview]
Message-ID: <20010215182101.J21919@vnl.com> (raw)
I'm trying to update some patches of Harald's to work
with the official 2.4.0 international patches. He had
a very nice unofficial patch set that doesn't use a
table, it just sees what is in /proc/crypto. I fixed
a few bugs and it worked marvelously with unofficial
test9 patches all the way up to t12.
However the official patches have changed the data
structure underlying the "files", ie
/proc/crypto/cipher/twofish-ecb no longer has int t_id;
it has int t_flags instead. And it isn't just a name
change, it does something entirely different.
Since Harald's code depended on predefined id's in the
international patches, that broke it pretty thoroughly.
I'm looking at them to see if I can excise that dependance
entirely. I think I can, but I'd like someone who I
could chat with about some of the underlying reasons
for certain things being there. Harald is busy with
other things and can't take time off to refresh himself
on the contents of the patch-int's enough to help.
I'm working on some mods now but I can see a couple
ways to go and I'd rather pick the right one first
time.
Please contact me directly, amon@vnl.com; since the
LK-digest went away I've been finding I often (mostly?)
miss things in the flood of thousands of itty bitty
messages :-)
--
------------------------------------------------------
Use Linux: A computer Dale Amon, CEO/MD
is a terrible thing Village Networking Ltd
to waste. Belfast, Northern Ireland
------------------------------------------------------
reply other threads:[~2001-02-15 18:20 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=20010215182101.J21919@vnl.com \
--to=amon@vnl.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox