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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00fd0e10-2c64-7a19-dd01-ec1a4440933d@redhat.com>
Date:   Wed, 21 Mar 2018 09:40:22 +0000
From:   Nick Clifton <nickc@...hat.com>
To:     Laura Abbott <labbott@...hat.com>,
        Andy Lutomirski <luto@...nel.org>, mjw@...oraproject.org,
        "H . J . Lu" <hjl.tools@...il.com>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        X86 ML <x86@...nel.org>, linux-kernel@...r.kernel.org,
        Cary Coutant <ccoutant@...il.com>
Subject: Re: [RFC PATCH 0/3] Salted build ids via linker sections

Hi Laura,

> This is an implementation of the counter proposal. If an environment variable
> is set, that value gets added as a .comment section to the necessary binaries.

This is not really my purview but ... can I just say that I really do not like
using environment variables to control build behaviour.  It makes reproducing a
build much harder.  Especially when you are trying to reproduce a bug report from
a user who does not even know that the environment variable exits.

Cheers
  Nick

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ