Bug 64883 – (grsec) gradm gets confused by the equivalence of lib and lib64. I am providing an ugly patch.

• Product: Gentoo Linux
• Status: RESOLVED UPSTREAM

[Description Barry Schwartz 2004-09-21 12:19:21 UTC]

When you use learning mode, gradm may complain that lib and lib64 objects are both present and equivalent, in implicitly generated subjects.

gradm tries to do the right thing, but I think it may be assuming a multilib system.  I've written an ugly, gentoo-amd64-specific patch.

Reproducible: Always
Steps to Reproduce:
1.Run learning mode for a role that can validate to gradm.
2.Try converting the logging output to a policy, using gradm.
3.Try to load the policy.

Actual Results:  
Complaints of lib and lib64 being the same.  Refusal to load.

Expected Results:  
Loaded the policy.

An ugly patch is attached.

[Comment 1 Barry Schwartz 2004-09-21 12:23:24 UTC]

Created attachment 40119 [details, diff]
Patch for gradm-2.0.1-r1 on amd64

This patch is ugly, because the issue isn't really an "amd64" issue, but a
filesystem structural problem.	But the patch refers specifically to amd64.

[Comment 2 solar (RETIRED) 2004-09-28 19:01:45 UTC]

lv: Can you look at this multilib change?

[Comment 3 Adam Mondl (RETIRED) 2005-01-19 10:40:32 UTC]

Is this patch still needed for gradm-2.1.0?

[Comment 4 Barry Schwartz 2005-01-19 11:19:42 UTC]

Created attachment 48982 [details, diff]
workaround for amd64 multilib-noncompliance

[Comment 5 Barry Schwartz 2005-01-19 11:21:57 UTC]

I've provided the new patch for 2.1.0.  This workaround won't be needed when amd64 goes fully multilib, but that probably won't be for several months.

[Comment 6 Adam Mondl (RETIRED) 2005-01-22 10:46:32 UTC]

This issue has been fixed in grsecurity CVS.  The next grsecurity/gradm release should resolve this issue in portage as well.