Bug#869774: Enigmail update broke ppc support

2017-08-10 Thread Stiepan Aurélien Kovac
are other (security) implications, what are they? Stiepan On 08/10/17 19:40, Stiepan Aurélien Kovac wrote: > Hi Daniel, > > Thank you for your reply. > > I have checked my Thunderbird version and I have the latest available > one on my platform: > > "apt

Bug#869774: Enigmail update broke ppc support

2017-08-10 Thread Stiepan Aurélien Kovac
of) So I still think that this bug should be reopened for the specific architecture that I am using. (in clear, that Bug #869774 should be reopened for PPC) Regards, Stiepan On 08/10/17 15:12, Daniel Kahn Gillmor wrote: > Hi there Stiepan-- > > On Wed 2017-08-09 01:21:38 +0200, Stiepan A

Bug#869774: Info received (Enigmail update broke ppc support)

2017-08-08 Thread Stiepan Aurélien Kovac
it to that version for powerpc, if there are no other security implications (did not have the time to sort them out, but basically messages sent encrypted were sent encrypted, never in clear). -- Stiepan A. Kovac M Sc ICT Security IT+Tech. Tel. Eng.

Bug#869774: Enigmail update broke ppc support

2017-08-08 Thread Stiepan Aurélien Kovac
and taking necessary action. And let me know if I can be of any further help, this is a productivity killer for me. Best regards, -- Stiepan A. Kovac M Sc ICT Security IT+Tech. Tel. Eng. P.S.: When trying to install from the official Thunderbird repo., getting the message: "eni

Bug#857295: [oss-security] LXC: CVE-2017-5985: lxc-user-nic didn't verify network namespace ownership

2017-03-28 Thread Stiepan
suggesting (specifically for lxc-user-nic - the current approach with 1-1 uid mappings seems fine for network-unrelated things). Stiepan Original Message Subject: Re: [oss-security] LXC: CVE-2017-5985: lxc-user-nic didn't verify network namespace ownership Local Time: 15 March 2017 11

Bug#857295: [pkg-lxc-devel] Bug#857295: Bug#857295: Info received ([oss-security] LXC: CVE-2017-5985: lxc-user-nic didn't verify network namespace ownership)

2017-03-28 Thread Stiepan
h includes the fixes for the aforementioned CVE). I will post an update on oss-security with the security-relevant part of this thread. Stiepan Sent with [ProtonMail](https://protonmail.com) Secure Email. Original Message Subject: Re: [pkg-lxc-devel] Bug#857295: Bug#857295: Inf

Bug#857295: [pkg-lxc-devel] Bug#857295: Info received ([oss-security] LXC: CVE-2017-5985: lxc-user-nic didn't verify network namespace ownership)

2017-03-24 Thread Stiepan
ne. Still, I thought that LXC enabled using lxcbr0 bridges in user mode, as lxc-user-nic's man page suggests is possible. Can you confirm whether this is the case with the current version? Regards, Stiepan Sent with [ProtonMail](https://protonmail.com) Secure Email. Original Message

Bug#857295: Info received ([oss-security] LXC: CVE-2017-5985: lxc-user-nic didn't verify network namespace ownership)

2017-03-24 Thread Stiepan
interface "vethXJW6PL" from host: Operation not permitted. With "plain old" br0, it still works as expected. Stiepan Sent with [ProtonMail](https://protonmail.com) Secure Email. Original Message Subject: Bug#857295: Info received ([oss-security] LXC: CVE-2017-598

Bug#857295: [oss-security] LXC: CVE-2017-5985: lxc-user-nic didn't verify network namespace ownership

2017-03-15 Thread Stiepan
unning lxc 2.0.6 in user mode using lxc-net. So a safe fallback (for Debian 8), for the time being, seems to be to avoid using user mode lxc networking and use a plain old br0 instead. This should work on all CPU architectures (even on powerpc, known to be recalcitrant to lxc on Debian 8)

Bug#857295: [oss-security] LXC: CVE-2017-5985: lxc-user-nic didn't verify network namespace ownership

2017-03-14 Thread Stiepan
finds its way into jessie-backports: that would be great! Stiepan Original Message Subject: Re: [oss-security] LXC: CVE-2017-5985: lxc-user-nic didn't verify network namespace ownership Local Time: 14 March 2017 2:06 AM UTC Time: 14 March 2017 01:07 From: tyhi...@canonical.com