[lkml]   [2019]   [May]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/2] public key: IMA signer logging: Log public key of IMA Signature signer in IMA log
On 5/16/19 7:34 AM, Ken Goldman wrote:

>> But outside the client machine this key id is not sufficient to
>> uniquely determine which key the signature corresponds to.
> Why is this not sufficient?
> In my implementation, I create a lookup table at the attestation service
> that maps the 4-byte IMA log key identifier to the signing public key.
> Are you concerned about collisions?  Something else?

Yes - the concern is collision.

The "Subject Key Identifier" (SKI) for no two certificate can be the
same. But since we are using only the last 4 bytes of the SKI it can
collide. That's mainly the reason I want to log the entire public key.

> Are you suggesting that the client supply the verification public key
> and that the verifier trust it?  Wouldn't that make the log self signed?
> How would the verifier determine that the key from the IMA log is valid
> / trusted / not revoked from the log itself?

IMA log is backed by the TPM. So if the public key is added to the IMA
log the attestation service can validate the key information.
I am not sure if that answers your question.

> A minor question here.
> Are you proposing that the IMA log contain a single ima-sigkey entry per
> public key followed by ima-sig entries?
> Or are you proposing that ima-sig be replaced by ima-sigkey, and that
> each event would contain both the signature and the public key?
> If the latter, this could add 25M to a server's 100K log.  Would that
> increase in size concern anyone?  Could it be a concern on the other
> end, an IoT device with limited memory?

Mimi had raised the same concern. I will update my implementation to
include the certification information in the IMA log only once per key -
when that key is added to the IMA or Platform keyring.


 \ /
  Last update: 2019-05-17 03:30    [W:0.102 / U:8.248 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site