Do I understand correctly that you’re saying booting an amd64 machine with syscall.x32=y should suffice to reproduce the issue?
On Sun, Nov 12, 2017 at 6:17 PM, Aaron M. Ucko <u...@debian.org> wrote: > Michael Stapelberg <stapelb...@debian.org> writes: > >> ucko, what’s the procedure here? How can Steffen get access to a >> machine on which to reproduce this issue? > > Good question. Technically, x32 is an alternate ABI for amd64, so the > amd64 porter box could in principle additionally host x32 chroots. > However, to do so, it would need an explicit kernel command line setting > (syscall.x32=y), since x32 binary support is off by default for now to > avoid adding a potential attack vector for little practical gain. > > I'm not an official porter or buildd maintainer, and don't know what > setup they use, sorry. > > -- > Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) > http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- Best regards, Michael
