On 15-05-21 08:45:08, Greg Kroah-Hartman wrote: > On Thu, May 21, 2015 at 09:05:21AM -0400, Mimi Zohar wrote: > > > > Signatures don't provide any guarantees as to code quality or > > correctness. They do provide file integrity and provenance. In > > addition to the license and a Signed-off-by line, having the firmware > > provider include a signature of the firmware would be nice. > > That would be "nice", but that's not going to be happening here, from what I > can tell. The firmware provider should be putting the signature inside the > firmware image itself, and verifying it on the device, in order to properly > "know" that it should be running that firmware. The kernel shouldn't be > involved here at all, as Alan pointed out. It is device's job to verify firmware's correctness. It is user's job to verify vendor's identity. Two different things, not related to each other. I think Alan meant something else. What i read is that if somebody have physical access to the device they may harm the device much easier and would not bother to tamper with firmware. > > > What is verifying a firmware image signature in the kernel attesting > > > that isn't already known in userspace? > > > > Appraising and enforcing firmware integrity before use. > > That should be done on the device itself, not in the kernel. Oh, well... -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
