lkml.org 
[lkml]   [2013]   [Jan]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [Xen-devel] [PATCH v3 00/11] xen: Initial kexec/kdump implementation
    On 01/11/2013 12:52 PM, Vivek Goyal wrote:
    >
    > Eric,
    >
    > In a private conversation, David Howells suggested why not pass kernel
    > signature in a segment to kernel and kernel can do the verification.
    >
    > /sbin/kexec signature is verified by kernel at exec() time. Then
    > /sbin/kexec just passes one signature segment (after regular segment) for
    > each segment being loaded. The segments which don't have signature,
    > are passed with section size 0. And signature passing behavior can be
    > controlled by one new kexec flag.
    >
    > That way /sbin/kexec does not have to worry about doing any verification
    > by itself. In fact, I am not sure how it can do the verification when
    > crypto libraries it will need are not signed (assuming they are not
    > statically linked in).
    >
    > What do you think about this idea?
    >

    A signed /sbin/kexec would realistically have to be statically linked,
    at least in the short term; otherwise the libraries and ld.so would need
    verification as well.

    Now, that *might* very well have some real value -- there are certainly
    users out there who would very much want only binaries signed with
    specific keys to get run on their system.

    -hpa




    \
     
     \ /
      Last update: 2013-01-11 22:41    [W:4.224 / U:0.504 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site