[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: store reference detection (was Re: JARs and reference scanning)
From: |
Leo Famulari |
Subject: |
Re: store reference detection (was Re: JARs and reference scanning) |
Date: |
Fri, 12 May 2017 14:27:05 -0400 |
User-agent: |
Mutt/1.8.2 (2017-04-18) |
On Fri, May 12, 2017 at 01:39:18PM -0400, Mark H Weaver wrote:
> One thing we could do is add a phase to certain build systems, which
> would try to use additional methods to detect these hidden references,
> and deliberately cause the build to fail in that case, raising the alarm
> that grafting would silently fail.
It's a good idea, and worth doing. I do think we will always find new
types of obfuscated references, unfortunately, but we should try to
address the types we know about.
Re: store reference detection (was Re: JARs and reference scanning), Mark H Weaver, 2017/05/12
- Re: store reference detection (was Re: JARs and reference scanning), Chris Marusich, 2017/05/12
- Re: store reference detection, Hartmut Goebel, 2017/05/12
- Re: store reference detection (was Re: JARs and reference scanning), Mark H Weaver, 2017/05/12
- Re: store reference detection (was Re: JARs and reference scanning),
Leo Famulari <=
- Re: store reference detection (was Re: JARs and reference scanning), Hartmut Goebel, 2017/05/12
- Re: store reference detection (was Re: JARs and reference scanning), Mark H Weaver, 2017/05/12
- Re: store reference detection (was Re: JARs and reference scanning), Hartmut Goebel, 2017/05/13
- Re: store reference detection (was Re: JARs and reference scanning), Chris Marusich, 2017/05/23