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  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]
Date:   Fri, 23 Sep 2016 18:04:06 -0700
From:   Daniel Mentz <>
To:     Alexey Brodkin <>
Cc:     "" <>,
        Vineet Gupta <>,
Subject: Re: modules still have .debug_* (was Re: [PATCH 0/3] ARC unwinder
 switch to .eh_frame)

On Fri, Sep 23, 2016 at 3:38 AM, Alexey Brodkin
<> wrote:
> On Thu, 2016-09-22 at 15:37 -0700, Daniel Mentz wrote:
>> Sorry, that was a misunderstanding. Buildroot routinely runs the strip
>> command on .ko files before installing them on the target. I was only
>> looking at the .ko files *after* running the strip command. No, the
>> interim patch was not in my tree.
> Well are you sure buildroot really touches modules in Linux kernel build folder?
> Buildroot just runs a simple "make" command in "output/build/linux-x.y".

Sorry, that was phrased badly. Buildroot does not touch the modules in
the Linux kernel build folder. Modules are stripped in the target
directory as you described.

> And only on installation step Buildroot strips binaries in "output/target" folder.
> Moreover starting from that commit
> even on Linux installation step Buildroot reuses kernel's module stripping infrastructure
> but again that happens only on target.

Powered by blists - more mailing lists