|
Bugzilla – Full Text Bug Listing |
| Summary: | glibc/ld- versions | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Andreas Jaeger <aj> |
| Component: | AppArmor | Assignee: | Seth R Arnold <seth.arnold> |
| Status: | RESOLVED WONTFIX | QA Contact: | Keiran Haggerty <khaggerty> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andreas Jaeger
2005-08-30 07:26:57 UTC
Seth: can we add these profiles to the default ld-<SPLAT> set? Andreas, are there platforms where ld-lsb.so.2 and ld-lsb.so.3 aren't symlinks? AppArmor doesn't use the symlink name when deciding which profile to apply, so unless they aren't symlinks somewhere, those profiles would never be applied. Removing the older loaders is a good idea. 80+ profiles loaded seems a bit silly when so many are blank. :) Thanks There're current no platforms where ld-lsb.so.2 is not a symlink but this is an implementation detail that might change. |