Hi Serge,
On 07/22/15 22:55, Serge Hallyn wrote:
> Quoting Harald Dunkel (harald.dun...@aixigo.de):
>>
>> This looks pretty fragile to me. Shouldn't lxc report the same
>> state for both paths, no matter what?
>
> No, because when you start the container, it listens on a
> abstract unix socket, i
Quoting Harald Dunkel (harald.dun...@aixigo.de):
> Hi Serge,
>
> On 07/22/15 22:55, Serge Hallyn wrote:
> > Quoting Harald Dunkel (harald.dun...@aixigo.de):
> >>
> >> This looks pretty fragile to me. Shouldn't lxc report the same
> >> state for both paths, no matter what?
> >
> > No, because when
Hi Serge,
On 07/23/15 15:12, Serge Hallyn wrote:
> Quoting Harald Dunkel (harald.dun...@aixigo.de):
>>
>> My suggestion would be to use the "real" lxcpath (resolving
>> all the symlinks and .. and .) for constructing the abstract
>> socket name.
>
> Well that's true, perhaps lxc should do a realp
Quoting Harald Dunkel (harald.dun...@aixigo.de):
> Hi Serge,
>
> On 07/23/15 15:12, Serge Hallyn wrote:
> > Quoting Harald Dunkel (harald.dun...@aixigo.de):
> >>
> >> My suggestion would be to use the "real" lxcpath (resolving
> >> all the symlinks and .. and .) for constructing the abstract
> >>
Hi,
the fix for CVE-2015-1334 (commit 659e807) does not apply cleanly to
1.1.2. Should one also cherry-pick commit 8af7999 then?
- Thomas
___
lxc-devel mailing list
lxc-devel@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-devel
Just CC'ing the Debian LXC maintainer and the upstream LXC mailing lists.
I guess they may find relevant this bug.
https://bugs.debian.org/793372
Regards.
On 23/07/15 13:57, Pablo Abelenda wrote:
> Package: systemd
> Version: 215-17+deb8u1
> Severity: important
>
> Dear Maintainer,
>
> I have
