linux-kernel - Re: 2.6.22.7 autoconf.h is screwed up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 24 Sep 2007 17:36:43 +0530
From:	"Jaswinder Singh" <jaswinderlinux@...il.com>
To:	"Sam Ravnborg" <sam@...nborg.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.22.7 autoconf.h is screwed up

Dear Sam,

On 9/24/07, Sam Ravnborg <sam@...nborg.org> wrote:
> On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote:
> > Hi all,
> >
> > 2.6.22.7's include/linux/autoconf.h is completely screwed up as
> > compare to 2.6.10's autoconf.h .
> >
> > 2.6.22.7 totally changed the meaning of autoconf.h
>
> autoconf.h has always been autogenerated. And autoconf.h has always
> been used to publish the configuration to .c files.
>
> What changed between 2.6.10 and 26.22 are the algorithm used to
> produce autoconf.h.

I just curious, how algorithm is written that it makes readable to non-readable.

Thank you,

Jaswinder Singh.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/