RPM

Use file sanity checking code of RPM instead of POPT

Registered by Jeff Johnson

     Change: stick-with-rpm-file-sanity-checking
     Purpose: Use file sanity checking code of RPM instead of POPT
     Reason: POPT >= 1.15 contains the poptSaneFile() function which
                     is equivalent to rpmSecuritySaneFile(). And POPT >=
                     1.15 also contains a poptReadConfigFiles() which
                     returns POPT_ERROR_BADCONFIG in case poptSaneFile()
                     says a file is not sane. This is all fine from a
                     raw sanity checking point of view. Unfortunately,
                     in the error reporting it is absolutely vital to
                     know _WHICH_ file is considered insecure. Until
                     POPT provides an error reporting callback or other
                     means for RPM to provide again reasonable warning
                     messages, we stick with the RPM sanity checking
                     code. So, this is not because OpenPKG is using
                     POPT < 1.15, but because we need proper warning
                     messages!

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.