From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: mc 4.8.19: segfaults while searching for contents
Date: Wed, 04 Oct 2017 16:41:32 +0100 [thread overview]
Message-ID: <1507131692.433.10.camel@ipfire.org> (raw)
In-Reply-To: <16f3832e-4f8a-94d8-d577-688713d65886@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
Hi,
this doesn't have anything to do with PaX. It's just a bug in mc.
Probably has this problem with files that have the SUID bit set?!
Did you try to update mc?
-Michael
On Tue, 2017-10-03 at 09:24 +0200, Matthias Fischer wrote:
> Hi,
>
> On 03.10.2017 08:50, Matthias Fischer wrote:
> > ...
> >
> > Suddenly 'mc 4.8.19' starts throwing segfaults...
> >
> > ...
>
> This is weird.
>
> As soon as directory (e.g. '/usr/local/bin') contains the file
> 'ipfirereboot', 'mc' crashes while searching for content 'flush' (e.g.).
>
> Thus, I would say, 'mc' has problems searching in (specific) binaries -
> searching in '/usr/bin' has the same effect.
>
> And:
>
> The following 'paxctl'-options had NO effect:
>
> ...
> root(a)ipfire: /usr/bin # paxctl -v /usr/bin/mc
> PaX control v0.9
> Copyright 2004,2005,2006,2007,2009,2010,2011,2012,2014 PaX Team
> <pageexec(a)freemail.hu>
>
> - PaX flags: -p-s-m-x-e-- [/usr/bin/mc]
> PAGEEXEC is disabled
> SEGMEXEC is disabled
> MPROTECT is disabled
> RANDEXEC is disabled
> EMUTRAMP is disabled
> ...
>
> Searching in text-only files is ok, but as soon as directory contains
> the above file (or something similar), 'mc' crashes.
>
> This does NOT happen on my devel with 'mc 4.8.15'... ;-)
>
> Best,
> Matthias
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-04 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 6:50 Matthias Fischer
2017-10-03 7:24 ` Matthias Fischer
2017-10-04 15:41 ` Michael Tremer [this message]
2017-10-04 16:34 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1507131692.433.10.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox