Page MenuHomeFreeBSD

portsnap: use lam on the 'good' hash list instead of sed on the untrusted one
ClosedPublic

Authored by emaste on Sep 29 2016, 1:43 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 27, 1:14 PM
Unknown Object (File)
Sat, Apr 27, 1:04 PM
Unknown Object (File)
Sat, Apr 27, 11:56 AM
Unknown Object (File)
Dec 20 2023, 12:28 AM
Unknown Object (File)
Nov 15 2023, 12:55 AM
Unknown Object (File)
Jul 1 2023, 8:07 AM
Unknown Object (File)
Jun 29 2023, 4:01 AM
Unknown Object (File)
May 9 2023, 7:04 AM
Subscribers

Details

Summary

This change should be equivalent to the approach committed in rS306417, but if sed has a bug it could be exploited by the untrusted tar file. Instead, convert the expected hash list to the expected tar content filesystem layout, and compare that with find's output.

Submitted by: @cperciva in D8052

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

emaste retitled this revision from to portsnap: use lam on the 'good' hash list instead of sed on the untrusted one.
emaste updated this object.
emaste edited the test plan for this revision. (Show Details)
emaste added reviewers: cperciva, allanjude.
emaste added a subscriber: cperciva.

I am capsicumizing lam(1), and will have a review soon

oshogbo edited edge metadata.
oshogbo added inline comments.
usr.sbin/portsnap/portsnap/portsnap.sh
694

\ - is not needed, or you should add some space like in rest file.

This revision is now accepted and ready to land.Oct 7 2016, 7:52 PM