On 19/12/14 03:50 AM, Lukas Jirkovsky wrote:
>
> No matter how much I like the idea of making Arch more secure, there
> is one thing that makes compiling the whole system with ASLR one big
> no-go for me (please correct me if I'm wrong). As far as I know, the
> ASLR makes core dumps completely usel
Warning : the repository multilib does not exist in /srv/abs/rsync/any
===
= Integrity Check x86_64 of core,extra,community,multilib =
===
Performing integrity checks...
==> parsing pkg
= Integrity Check i686 of core,extra,community =
Performing integrity checks...
==> parsing pkgbuilds
==> parsing db files
==> checking mismatches
==> checking archs
==> checking dependencies
==> che
On Fri, Dec 19, 2014 at 08:03:37AM -0500, keenerd wrote:
> On 12/14/14, Dave Reisner wrote:
> > No objections to Kyle taking over namcap alone, but I have to ask, Kyle,
> > are you interested in taking on pyalpm as well?
>
> Not terribly interested, but I guess I can if I have to. Attached is
>
On 12/14/14, Dave Reisner wrote:
> No objections to Kyle taking over namcap alone, but I have to ask, Kyle,
> are you interested in taking on pyalpm as well?
Not terribly interested, but I guess I can if I have to. Attached is
a quick 30 minute hack that lets pyalpm build against 4.2 and restore
=== Signoff report for [testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 4 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 5 fully signed off packages
* 32 packages missing signoffs
* 0 packages older than 14 days
(Note: t
On 19 December 2014 at 00:31, Daniel Micay wrote:
> Arch's single biggest security weakness is that it's not benefiting from
> address space layout randomization (ASLR). Fixing this issue would be a
> major step towards being a leader in this area. Many distributions enable
> ASLR, stack protector
7 matches
Mail list logo
