[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cryptoapi kernel-patch packages for debian

All this is being done right now...and the more I thought about ti
today...I'd much prefer having a:

  "make clean; make get_crypto; make menuconfig; make bzImage; make modules;"
               ^^^^^^^^^^^^^^^
               New kernel make command!

This command would hold nothing but a few shell commands, one being:
  lynx -source http://www.kerneli.org/go?<kernelVersion>/<countryCode> | sh

As I'm developing now (EXTREME ALPHA):
  http://jlcooke.ca/go

When was the last time linus/alen/marcelo added a new Makefile command? (I'm
serious, really!)

JLC

On Sat, Jul 06, 2002 at 12:33:08PM +0200, Fruhwirth Clemens wrote:
> On Fri, Jul 05, 2002 at 02:04:31PM -0400, Jean-Luc Cooke wrote:
> > A very simple (distro-Agnostic) patch installer is in the works now. 
> > Something akin to go-gnome.com's method.
> > 
> > Speaking of which, can I get everyone's input on known crypto restrictions
> > and recommendations so this installer can help people comply with the laws
> > in their locality.
> > 
> > Clemens, my suspicion that DEBs are better then RPMs is re-confirmed, good
> > work!  Once the kerneli.org/go script-rules are ready (with your gracious
> > input) could you wrap it into a DEB?
> 
> Sure, but I warn to start using different patch files for different
> legislations. A simple solution to prevent the patch file maintainance mess
> is to integrate the selection of legal ciphers/digests with the kernel
> Config.in mechanism.  The go script would have to generate a source-able
> file (i.e. /etc/kernel-site.cfg) with a content like
> 
> CONFIG_LEGAL_CIPHERS_STRONG=[y|n]
> CONFIG_LEGAL_CIPHERS_WEAK=[y|n]
> ... and so on
> 
> This file would be "source"-ed by crypto's Config.in scripts, that select the
> allowed options based on the defined symbols.
> 
> For deb packaging it'd be convienent to split the /etc/kernel-site.cfg
> generating part off the rest of the go script, since the deb packages don't
> need the rest of the patching mechanism.
> 
> > The goals we're all striving for:
> >   - make the cryptoapi installer part of standard distros (sans crypto)
> 
> For the deb packages it'll be all or nothing ATM (in terms of source).
> 
> Regards, Clemens



-- 
http://www.certainkey.com
Suite 4560 CTTC
1125 Colonel By Dr.
Ottawa ON, K1S 5B6
C: 613.263.2983
-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/