[arch-general] PIE repo considerations
From what i glean from the conversation below, i think a (totally
i was wondering if anyone had any ideas on how one might setup unofficial user repos with all the offical arch packages but built with hardening-wrapper. presumed needs 1) download latest sources for all official arch packages. abs does this but i's rather not wait up to a day to get security updates. Why doesn't abs just sync however the repo mirrors do? 2) build all of them (with hardening-wrapper) automatically 3) auto-rebuild when arch official package gets upgraded. 4) make available as binary packages in unofficial user repo.(assuming arch doesn't want to have official aslr repos) For #1 i'm thinking asp would be nice as it grabs the latest sources but it doesn't currently have an "-all" option or similar. Assuming its dev would add it, do scripts or packages currently exist that would facilitate the other items(mainly 2 & 3 above)? ----------------------------------------------------------------- https://www.archlinux.org/packages/community/x86_64/hardening-wrapper/ https://wiki.archlinux.org/index.php/DeveloperWiki:Security#PIE theoretical) user vote would have resulted in an affirmative on full aslr: https://lists.archlinux.org/pipermail/arch-dev-public/2014-December/026843.h... I also don't understand the lack of discussion on something this important by other devs. one person had concerns about various things and another mentioned whether upstream would support it and that was it. I was hoping to at least hear why the wrapper method was so out of spec for arch as to warrant not supporting full aslr. I'm sure it seems obvious to those devs opposed, but not to me or possibly other end users. Also, i don't think i'm owed an explanation. I'm just saying more context for something this important would have been nice. thanks, ITwrx
On 05/16/2016 05:47 PM, Information Technology Works wrote:
I also don't understand the lack of discussion on something this important by other devs. one person had concerns about various things and another mentioned whether upstream would support it and that was it. I was hoping to at least hear why the wrapper method was so out of spec for arch as to warrant not supporting full aslr. I'm sure it seems obvious to those devs opposed, but not to me or possibly other end users. Also, i don't think i'm owed an explanation. I'm just saying more context for something this important would have been nice.
I think at the current state it will be waste of efforts to setup a user repository and build everything with hardening-wrapper. There has been several internal discussion about PIE in the past and recent times, that is definitively something that we are aware of. In the past there has been various (performance) reasons with gcc5 that hold up stepping further, so the decision was to not backport gcc6 patches and wait for gcc6 so arrive. Fortunately gcc6 arrived so the topic landed again on the tables for discussion. The current state is that we wanted to have some benchmarking with current (non-PIE) and PIE enabled binaries to compare them and make sure it eliminated all previous concerns. If you want to to really help pushing this topic in an official way then the most useful and best step you could do is helping out to do those benchmarks. cheers, Levente
participants (2)
-
Information Technology Works
-
Levente Polyak