Bug 10150 - Allow per-feed signature verification
Summary: Allow per-feed signature verification
Status: RESOLVED FIXED
Alias: None
Product: opkg
Classification: Yocto Project Subprojects
Component: opkg (show other bugs)
Version: unspecified
Hardware: All Multiple
: Undecided enhancement
Target Milestone: 0.3.4
Assignee: Alejandro del Castillo
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-08-16 09:25 UTC by Ioan-Adrian Ratiu
Modified: 2016-11-23 20:05 UTC (History)
0 users

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ioan-Adrian Ratiu 2016-08-16 09:25:15 UTC
Right now opkg signature verification happens globally for all feeds, with an on/off switch 'option check_signature 0/1'. It might be useful to be able to enable/disable signature checking on a per-feed basis, to have something like a core feed which is verified and additional feeds which are not.

An interesting problem is how does the attack surface vary if one feed's signature is checked while another feed's is not. Can an unsigned feed packages override core packages? Because if something like this can happen then disabling feed signatures for one feed is like disabling for all. Perhaps this is why there is no per-feed signature verification in opkg and it makes sense to keep it this way?
Comment 1 Alejandro del Castillo 2016-10-31 22:49:43 UTC
Debian already have the concept of trusted feeds. By setting a feed to "trusted" you are explicitly saying that you are OK bypassing security checks:

deb [trusted=yes] http://localmachine/debian wheezy main

I am OK implementing something similar on opkg.
Comment 2 Alejandro del Castillo 2016-11-23 20:05:36 UTC
implemented on 7a8c2f62c758c062a9b545caf9e941e79f80a2b4