On Fri, Sep 08, 2017 at 01:59:00PM -0700, h...@zytor.com wrote:
> On September 8, 2017 2:45:10 AM PDT, Gary Lin wrote:
> >On Thu, Sep 07, 2017 at 02:16:21PM -0700, h...@zytor.com wrote:
> >> On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
> >> >On Thu, Jun 01,
On Fri, Sep 08, 2017 at 01:59:00PM -0700, h...@zytor.com wrote:
> On September 8, 2017 2:45:10 AM PDT, Gary Lin wrote:
> >On Thu, Sep 07, 2017 at 02:16:21PM -0700, h...@zytor.com wrote:
> >> On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
> >> >On Thu, Jun 01, 2017 at 08:46:26AM +, Ard
On Fri, Sep 08, 2017 at 01:59:00PM -0700, h...@zytor.com wrote:
> On September 8, 2017 2:45:10 AM PDT, Gary Lin wrote:
> >On Thu, Sep 07, 2017 at 02:16:21PM -0700, h...@zytor.com wrote:
> >> On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
> >> >On Thu, Jun 01,
On Fri, Sep 08, 2017 at 01:59:00PM -0700, h...@zytor.com wrote:
> On September 8, 2017 2:45:10 AM PDT, Gary Lin wrote:
> >On Thu, Sep 07, 2017 at 02:16:21PM -0700, h...@zytor.com wrote:
> >> On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
> >> >On Thu, Jun 01, 2017 at 08:46:26AM +, Ard
On September 8, 2017 2:45:10 AM PDT, Gary Lin wrote:
>On Thu, Sep 07, 2017 at 02:16:21PM -0700, h...@zytor.com wrote:
>> On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
>> >On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
>> >> On 1 June 2017 at
On September 8, 2017 2:45:10 AM PDT, Gary Lin wrote:
>On Thu, Sep 07, 2017 at 02:16:21PM -0700, h...@zytor.com wrote:
>> On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
>> >On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
>> >> On 1 June 2017 at 08:11, Gary Lin wrote:
>> >>
On Thu, Sep 07, 2017 at 02:16:21PM -0700, h...@zytor.com wrote:
> On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
> >On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
> >> On 1 June 2017 at 08:11, Gary Lin wrote:
> >> > On Fri, May 12, 2017 at
On Thu, Sep 07, 2017 at 02:16:21PM -0700, h...@zytor.com wrote:
> On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
> >On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
> >> On 1 June 2017 at 08:11, Gary Lin wrote:
> >> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
>On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
>> On 1 June 2017 at 08:11, Gary Lin wrote:
>> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
>> >> A new section, secdata, in the
On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
>On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
>> On 1 June 2017 at 08:11, Gary Lin wrote:
>> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
>> >> A new section, secdata, in the setup header is introduced to
On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
> On 1 June 2017 at 08:11, Gary Lin wrote:
> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
> >> A new section, secdata, in the setup header is introduced to store the
> >> distro-specific security version
On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
> On 1 June 2017 at 08:11, Gary Lin wrote:
> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
> >> A new section, secdata, in the setup header is introduced to store the
> >> distro-specific security version which is
Hi,
On Mon, Jul 10, 2017 at 11:24:44AM +0800, Gary Lin wrote:
> A new section, secdata, in the setup header is introduced to store the
> distro-specific security version which is designed to help the
> bootloader to warn the user when loading a less secure or vulnerable
> kernel. The secdata
Hi,
On Mon, Jul 10, 2017 at 11:24:44AM +0800, Gary Lin wrote:
> A new section, secdata, in the setup header is introduced to store the
> distro-specific security version which is designed to help the
> bootloader to warn the user when loading a less secure or vulnerable
> kernel. The secdata
A new section, secdata, in the setup header is introduced to store the
distro-specific security version which is designed to help the
bootloader to warn the user when loading a less secure or vulnerable
kernel. The secdata section can be presented as the following:
struct sec_hdr {
__u16
A new section, secdata, in the setup header is introduced to store the
distro-specific security version which is designed to help the
bootloader to warn the user when loading a less secure or vulnerable
kernel. The secdata section can be presented as the following:
struct sec_hdr {
__u16
On 30 June 2017 at 23:52, joeyli wrote:
> Hi Ard,
>
> On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
>> On 1 June 2017 at 08:11, Gary Lin wrote:
>> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
>> >> A new section, secdata, in the
On 30 June 2017 at 23:52, joeyli wrote:
> Hi Ard,
>
> On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
>> On 1 June 2017 at 08:11, Gary Lin wrote:
>> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
>> >> A new section, secdata, in the setup header is introduced to
Hi Ard,
On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
> On 1 June 2017 at 08:11, Gary Lin wrote:
> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
> >> A new section, secdata, in the setup header is introduced to store the
> >> distro-specific
Hi Ard,
On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
> On 1 June 2017 at 08:11, Gary Lin wrote:
> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
> >> A new section, secdata, in the setup header is introduced to store the
> >> distro-specific security version which
On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
> On 1 June 2017 at 08:11, Gary Lin wrote:
> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
> >> A new section, secdata, in the setup header is introduced to store the
> >> distro-specific security version
On Thu, Jun 01, 2017 at 08:46:26AM +, Ard Biesheuvel wrote:
> On 1 June 2017 at 08:11, Gary Lin wrote:
> > On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
> >> A new section, secdata, in the setup header is introduced to store the
> >> distro-specific security version which is
On 1 June 2017 at 08:11, Gary Lin wrote:
> On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
>> A new section, secdata, in the setup header is introduced to store the
>> distro-specific security version which is designed to help the
>> bootloader to warn the user when
On 1 June 2017 at 08:11, Gary Lin wrote:
> On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
>> A new section, secdata, in the setup header is introduced to store the
>> distro-specific security version which is designed to help the
>> bootloader to warn the user when loading a less
On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
> A new section, secdata, in the setup header is introduced to store the
> distro-specific security version which is designed to help the
> bootloader to warn the user when loading a less secure or vulnerable
> kernel. The secdata section
On Fri, May 12, 2017 at 04:05:34PM +0800, Gary Lin wrote:
> A new section, secdata, in the setup header is introduced to store the
> distro-specific security version which is designed to help the
> bootloader to warn the user when loading a less secure or vulnerable
> kernel. The secdata section
A new section, secdata, in the setup header is introduced to store the
distro-specific security version which is designed to help the
bootloader to warn the user when loading a less secure or vulnerable
kernel. The secdata section can be presented as the following:
struct sec_hdr {
__u16
A new section, secdata, in the setup header is introduced to store the
distro-specific security version which is designed to help the
bootloader to warn the user when loading a less secure or vulnerable
kernel. The secdata section can be presented as the following:
struct sec_hdr {
__u16
28 matches
Mail list logo