Ok - I'll have to budget some time to look into this - I'm not sure that I'll be able to fix this upstream in the next ~14-20days. I will find some time in the next week to look into the details. It may be as simple as disabling seccomp on mips for now. I'd rather not do that as it is simply not the security direction I'd like for tlsdate...
On 12/12/14, James Cowgill <james...@cowgill.org.uk> wrote: > On Fri, 2014-12-12 at 14:29 +0000, Jacob Appelbaum wrote: >> Thanks for the bug report! >> >> I think it might make sense to disable seccomp when building on that >> platform until the next upstream release. I've not had access to a >> mips64 box with seccomp - it may also be a trivial patch and I haven't >> had any time to look into this specific issue yet. >> >> Could you give me an idea of the timeline within this should be >> resolved to make sure we can ship a seccomp enabled tlsdate for >> mips64? Does this happen on any other mips system? > > I'm not sure if I was very clear on this. The machine is running jessie > mipsel (ie a 32 bit userspace) but uses a 64-bit kernel - this one: > https://packages.debian.org/sid/linux-image-3.16.0-4-loongson-3 > > This was the commit in the kernel: > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=490b004fe > > Since the change was applied to "config MIPS" I would guess this bug > affects all mips kernels (big / little endian, 32/64 bit, all flavours) > since 3.15. > > James > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
