At 2017-04-07T20:08:05+0200, Graham Inggs wrote:
> On 7 April 2017 at 19:06, G. Branden Robinson
> wrote:
> > All of this hardening stuff, as I understand it, involves mitigation
> > strategies for unsafe memory usage in the C language family in the ELF
> > object file format.
>
> It's not only h
On 7 April 2017 at 19:06, G. Branden Robinson
wrote:
> All of this hardening stuff, as I understand it, involves mitigation
> strategies for unsafe memory usage in the C language family in the ELF
> object file format.
It's not only hardening stuff, it's whatever flags someone building
the packag
At 2017-04-07T14:10:06+0200, Graham Inggs wrote:
> On 07/04/2017 13:12, G. Branden Robinson wrote:
> > compile_rom is an utility internal to the build. It's not shipped and
> > thus not subject to attacks. I'm considering adding an --ignore-line
> > for it, but I need to figure out how to embed t
On 07/04/2017 13:12, G. Branden Robinson wrote:
compile_rom is an utility internal to the build. It's not shipped and
thus not subject to attacks. I'm considering adding an --ignore-line
for it, but I need to figure out how to embed this information in the
package itself so the buildd log scann
package xtrs
tag 859751 + pending
thanks
At 2017-04-06T22:01:05+0200, Graham Inggs wrote:
> Source: xtrs
> Version: 4.9c-4
> Severity: wishlist
> Tags: patch
>
> Hi Maintainer
>
> Welcome back!
Thanks!
> According to the buildd log scanner [1],
>
> Issues found in current buildd logs for xtrs
Source: xtrs
Version: 4.9c-4
Severity: wishlist
Tags: patch
Hi Maintainer
Welcome back!
According to the buildd log scanner [1],
Issues found in current buildd logs for xtrs:
W dpkg-buildflags-missing CPPFLAGS 27 (of 27), CFLAGS 27 (of 27),
LDFLAGS 5 (of 5) missing (amd64, arm64, armel, armhf,
6 matches
Mail list logo
