Arch Linux

Zorbik

Member

Registered: 2016-08-09

Posts: 42

[SOLVED] grsec errors while installing aur packages with pacaur

Concerned whether packages installed using pacaur are being installed correctly. Running

pacaur -y lemonbar

gets me this:

:: resolving dependencies...
[ 2913.942445] grsec: denied RWX mmap of <anonymous mapping> by /usr/bin/grep[grep:10642] uid/euid:1000/1000 gid/egid:100/100, parent /usr/bin/pacaur[pacaur:10638] uid/euid:1000/1000 gid/egid:100/100
[ 2914.756028] grsec: denied RWX mmap of <anonymous mapping> by /usr/bin/grep[grep:10699] uid/euid:1000/1000 gid/egid:100/100, parent /usr/bin/pacaur[pacaur:10695] uid/euid:1000/1000 gid/egid:100/100
[ 2914.764368] grsec: denied RWX mmap of <anonymous mapping> by /usr/bin/grep[grep:10706] uid/euid:1000/1000 gid/egid:100/100, parent /usr/bin/pacaur[pacaur:10702] uid/euid:1000/1000 gid/egid:100/100
[ 2914.773987] grsec: denied RWX mmap of <anonymous mapping> by /usr/bin/grep[grep:10715] uid/euid:1000/1000 gid/egid:100/100, parent /usr/bin/pacaur[pacaur:10710] uid/euid:1000/1000 gid/egid:100/100
:: looking for inter-conflicts...
:: lemonbar-1.2-1 is up to date -- reinstalling

AUR Packages  (1) lemonbar-1.2-1

:: Proceed with installation? [Y/n]

Proceeding with the installation seems to go fine. The same message pops up elsewhere throughout the installation but all seems to be ok.
My main concern is whether the packages I am installing are installed correctly or if grsec is interfering and leaving me with broken packages.
System info:

linux-grsec 1:4.7.4r201609211951-1
pacaur 4.6.9-1

NOTE: This was showing up on the previous version of linux-grsec (updated today).

Last edited by Zorbik (2016-09-26 12:35:49)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: [SOLVED] grsec errors while installing aur packages with pacaur

Not a Sysadmin issue, moving to AUR Issues...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Zorbik

Member

Registered: 2016-08-09

Posts: 42

Re: [SOLVED] grsec errors while installing aur packages with pacaur

Sorry and thank you

Spyhawk

Member

Registered: 2006-07-07

Posts: 485

Re: [SOLVED] grsec errors while installing aur packages with pacaur

Looks like something is wrong with 'grep' due to grsec. Not related to pacaur, apart from the fact that it calls grep.

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: [SOLVED] grsec errors while installing aur packages with pacaur

It's indeed not a pacaur problem, but more things then grep suffer from this.

A DDG-search for 'grsec: denied RWX mmap of <anonymous mapping>' gives tons of results.
Making an MPROTECT exception for the denied program seems to be the most common solution.

Disclaimer :
I don't use PaX / Grsec myself and have no idea if such an exception is a good idea and/or how to configure it.

My main concern is whether the packages I am installing are installed correctly or if grsec is interfering and leaving me with broken packages.

hard to tell, requires someone with intimate pacaur knowledge .

Last edited by Lone_Wolf (2016-09-26 11:36:33)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Zorbik

Member

Registered: 2016-08-09

Posts: 42

Re: [SOLVED] grsec errors while installing aur packages with pacaur

It's indeed not a pacaur problem, but more things then grep suffer from this.

A DDG-search for 'grsec: denied RWX mmap of <anonymous mapping>' gives tons of results.
Making an MPROTECT exception for the denied program seems to be the most common solution.

Disclaimer :
I don't use PaX / Grsec myself and have no idea if such an exception is a good idea and/or how to configure it.

My main concern is whether the packages I am installing are installed correctly or if grsec is interfering and leaving me with broken packages.

hard to tell, requires someone with intimate pacaur knowledge .

It was indeed a problem with grep, as removing the MPROTECT feature from it, using

$ setfattr -n user.pax.flags -v "emr" /usr/bin/grep

removed the messages I was receiving. As to MPROTECT, it is by definition

The function mprotect() specifies the desired protection for the memory page(s) containing part or all of the interval [addr,addr+len-1]. If an access is disallowed by the protection given it, the program receives a SIGSEGV. prot is a bitwise-or of the following values: Tag.

Also, according to the wiki, this is the most common issue with compatibility.

Thank you guys for the help. Will mark the thread as solved

Last edited by Zorbik (2016-09-26 12:34:41)