The new license for SINIT allows to _redistribute_ in binary form
without modification.
To make SINIT to be part of firmware, I think it will meet the upgrade
problem. The upgrade of firmware is rare and not so easy for users.
Thanks.
Shane
Jonathan M. McCune wrote:
> Is it not also the case that the long-term plan is for the module
> specific to a particular system to be included with that system as part
> of its firmware? I.e., code that wants to use TXT can just read the
> appropriate module out of a well-known memory location?
>
> If this is the case, then it solves the distribution problem, at least
> in the long run.
>
> Thanks,
> -Jon
>
>
>
> Shane Wang wrote:
>> Yes, you are right.
>>
>> Shane
>>
>> Martin Pirker wrote:
>>> Reading the "Intel Software License Agreement" packaged along
>>> with the SINIT binaries, I would interpret it that it is not
>>> allowed to distribute the SINIT modules.
>>> Rather, every user who wants to do a TXT boot needs to
>>> download and install the SINIT binaries by himself.
>>>
>>> Is my reading correct?
>>>
>>> Martin
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> tboot-devel mailing list
>>> tbo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> tboot-devel mailing list
>> tbo...@li...
>> https://lists.sourceforge.net/lists/listinfo/tboot-devel
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> tboot-devel mailing list
> tbo...@li...
> https://lists.sourceforge.net/lists/listinfo/tboot-devel
|