Re: [CryptoAPI-devel] Configure.help and other questions

[Herbert V. R. <hv...@hv...>]

On Mon, 2002-03-18 at 09:47, David Bryson wrote:
> So, I may have done something wrong, but the Config.help options are not
> showing up on my kernel config.  I was going to write
> some help options for the different ciphers/digest, but the help that was
> already there never showed up.

> So, i started looking around for why they weren't on there and i ended up
> not seeing any way to "register" the help file as a seperate place to loo=
k
> for help texts.  afaict you just have to "cat crypto/Config.help
> Documentation/Configure.help" ... which seems a little silly to me, can
> anyone else shed some light on this for me?

the Config.help file is there for 2.5's kbuild framework...

I'm trying to use .diff files as little as possible, as they usually
tend to create conflicts while patching, and require one to always
maintain them... or to say in other words, they are a big mess...

that's why I really like the 2.5 kbuild's idea of splitting up
Configure.help; I hope that 2.4 gets this feature backported from 2.5..
or maybe we could could send in a patch to marcelo?

anyway, in order to let this COnfig.help show up, you'll have to insert
it into Documentation/Configure.help of your kernel source tree... this
should be done from within the 'patch-kernel' makefile target... with
some clever textutils aggregation... :-)

> I also implemented gen-cfb today, so now we can use cipher feedback mode
> for everything provided we put the includes in there.  Which brings me to
> my next question, could we just put #include "gen-<cipher>" in the
> crypto.h instead of manually entering block modes into ever different
> cipher?  I want to implement a couple other block modes, pcbc, and ofb,
> maybe some more.  At any rate, we have to put new cipher contexts in ever=
y
> cipher.. so i was trying to figure out a way to try and abstract that a
> bit.  I'll poke around the sources some more, try to come up with ideas.

I originally had plans to templatize the ciphers a bit more, but this'll
have to wait a week...

anyway, adding those includes into <crypto.h> is not such a good idea;=20
adding a local "gen-cipher.h" header (just where the gen-cbc.h and
gen-ecb.h headers lay) is the way to go IMO; I'll commit something like
that very soon... i.e. please don't do major modifications to the
ciphers in CVS that I'll revert anyway... :-)

regards,
--=20
Herbert Valerio Riedel       /    Phone: (EUROPE) +43-1-58801-18840
Email: hv...@hv...       /    Finger hv...@gn... for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748  5F65 4981 E064 883F
4142