Wooohhoooo. Hit me up.
On Thu, 28 May 2015 00:33:46 -0700 (PDT)
fowl...@riseup.net wrote:
> I starred this post a while ago. I have been busy with school, so
> sorry I am just replying. Since dom0 is not networked, the security
> of the Qubes system would probably not receive benefit from a dom0
> change unless the new dom0 used reproducible builds w/
> multi-signatures (Debian is the furthest along in this regard and I
> could see the Qubes team going w/ it for Qubes 4 dom0--they mentioned
> their interest in a trustless system in their most recent roadmap).
I have plans of eventually utilizing gitian with Alpine in the future.
However there are bigger things on my list of what I want to see
accomplished for Alpine.
> Fedora does not use PIE for everything like Alpine does, but uses it
> for security critical packages (I'm not sure how to confirm, but I
> assume/hope this includes Xen and related libraries). Further, it
> uses fstack-protector-strong w/ GCC.
From what I've checked in the alpine port repository it keeps all of
the stack & other compilation hardening for xen.
> Correct me if I'm wrong, but Pax and GrSec only provide Linux kernel
> hardening, and would do nothing for Xen.
I don't know. Since I don't know how Xen's hypervisor works.
> On the other hand, Alpine would make a fantastic addition as a
> template VM. I really appreciate the categorical approach to bug
> elimination Pax/GrSec takes and Alpine seems like a great distro
> (although I have yet to run it myself!). I have a lot of free time on
> my hands at the moment as an unemployed college grad living at home
> with his parents :D and would very much be interested in helping you
> build it as a template if you'd like to work together on this.
Let's get started. :D
--
keybase.io/systmkor