On Mon, 27 Jul 2020 12:13:44 +0200 Samuel Thibault wrote:
> Alessandro Vesely, le lun. 27 juil. 2020 11:47:34 +0200, a ecrit:
> > So this turns out to be a documentation bug. The execve man page should
> > mention that EACCESS can result as an (unforeseen) apparmor impediment.
>
> Well,
Alessandro Vesely, le lun. 27 juil. 2020 11:47:34 +0200, a ecrit:
> So this turns out to be a documentation bug. The execve man page should
> mention that EACCESS can result as an (unforeseen) apparmor impediment.
Well, basically all system calls would then need this...
Samuel
Hi Mark,
On Mon 27/Jul/2020 11:14:01 +0200 Mark Hindley wrote:
> On Mon, Jul 27, 2020 at 10:32:15AM +0200, Alessandro Vesely wrote:
>> Package: libc6
>> Version: GNU C Library (Debian GLIBC 2.28-10) stable release version 2.28.
>> Severity: normal
>>
>> in certain situations, execve fails
On Mon, Jul 27, 2020 at 11:47:34AM +0200, Alessandro Vesely wrote:
> > However, one thought that occurs to me is whether apparmor is causing this?
> > Does
> > disabling it[1] restore predictable behaviour?
>
> Bingo!
>
> Jul 27 09:47:25 pcale kernel: [ 1569.887279] audit: type=1400
>
4 matches
Mail list logo
