Dear Ilias,
In message <20190627070821.GA10271@apalos> you wrote:
>
> > > > > There have been thoughts about using signed environment storage
> > > > > before. This is manageable as long as your environment is read-only.
> > > > > But for writing ("env save") you need access to the private key to
Dear Takahiro,
In message <20190627051518.gb19...@linaro.org> you wrote:
>
> In UEFI environment, *not* all the variables are to be authenticated,
> but just a few. The signature verification for such "authenticated"
> variables should be done *per* variable.
I see.
> * authenticated variables c
Dear Wolfgang, Akashi-san,
On Thu, Jun 27, 2019 at 02:15:19PM +0900, AKASHI Takahiro wrote:
> Wolfgang,
>
> I think that we are getting much closer than a few days ago,
> but first let me explain one point that I'm afraid that you
> might misunderstand somehow:
>
> On Wed, Jun 26, 2019 at 11:44:0
Wolfgang,
I think that we are getting much closer than a few days ago,
but first let me explain one point that I'm afraid that you
might misunderstand somehow:
On Wed, Jun 26, 2019 at 11:44:03AM +0200, Wolfgang Denk wrote:
> Dear Ilias,
>
> In message
> you
> wrote:
> >
> > > There have been
Dear Ilias,
In message
you wrote:
>
> > There have been thoughts about using signed environment storage
> > before. This is manageable as long as your environment is read-only.
> > But for writing ("env save") you need access to the private key to
> > sign the new data. Do you have a good solu
Dear Takahiro,
In message <20190626052624.gr6...@linaro.org> you wrote:
>
> > See above. If you think small (and go for minimal coding efforts),
> > just add a UEFI flag now to provide a UEFI context. If tomorrow
> > someone needs a FOO context, add a FOO flag. We did not really need
> > such c
Dear Francois,
it would have been _very_ helpful to keep the Subject: and the Cc:
list in place.
In message
you wrote:
>
> On one side we have UEFI have objects that can be persistent and/or
> secure. More importantly, a UEFI application can register a storage
> backend to perform
> UEFI variab
Dear Wolfgang,
On Tue, 25 Jun 2019 at 12:27, Wolfgang Denk wrote:
>
> Dear Ilias,
>
> In message <20190625091140.GA19606@apalos> you wrote:
> >
> > > > Currently UEFI variables are stored in U-Boot variables. Saving the
> > > > U-Boot variables will persist all UEFI variables in the environment b
Wolfgang,
On Tue, Jun 25, 2019 at 11:11:18AM +0200, Wolfgang Denk wrote:
> Dear Takahiro,
>
> In message <20190625075931.gp6...@linaro.org> you wrote:
> >
> > > It does not have to be ugly, and I think it is also not so
> > > complicatred. In any case it seems more attractive to me than
> > > ad
Dear Wolfgang,
> >
> > thanks a lot for the good online meeting this morning together with your
> > colleague Suggan where we discussed the requirements for the
> > implementation of non-volatile variables in U-Boot.
> >
> > Currently UEFI variables are stored in U-Boot variables. Saving the
> >
Dear Ilias,
In message <20190625091140.GA19606@apalos> you wrote:
>
> > > Currently UEFI variables are stored in U-Boot variables. Saving the
> > > U-Boot variables will persist all UEFI variables in the environment both
> > > volatile and non-volatile. This does not conform the the UEFI standard.
Dear Takahiro,
In message <20190625075931.gp6...@linaro.org> you wrote:
>
> > It does not have to be ugly, and I think it is also not so
> > complicatred. In any case it seems more attractive to me than
> > adding a completly separate, new implementation for variable
> > storage.
>
> Really? Take
On Tue, Jun 25, 2019 at 08:33:30AM +0200, Wolfgang Denk wrote:
> Dear Takahiro,
>
> In message <20190625011039.go6...@linaro.org> you wrote:
> >
> > > Think about secure boot. It is a bad idea to expose variables in this way.
> >
> > Actually, we are thinking of disabling U-Boot environment (I mea
Dear Takahiro,
In message <20190625011039.go6...@linaro.org> you wrote:
>
> > Think about secure boot. It is a bad idea to expose variables in this way.
>
> Actually, we are thinking of disabling U-Boot environment (I mean,
> ENV_IS_NOWHERE) still allowing for UEFI variables for security reason.
Dear Heinrich,
In message <63fcd992-2d43-d168-64e8-7058c3a24...@gmx.de> you wrote:
>
> > Oops? Is it possible that you are not aware of the
> > tools/env/fw_env* code?
>
> I am fully aware of this.
OK, then why do you claim that U-Boot nvironment variables are not
"available to the operating sys
On 6/25/19 3:10 AM, AKASHI Takahiro wrote:
On Mon, Jun 24, 2019 at 09:10:07PM +0200, Heinrich Schuchardt wrote:
On 6/24/19 8:50 PM, Wolfgang Denk wrote:
Dear Heinrich,
In message <7083d208-4b3c-7261-a03b-9066dc8d2...@gmx.de> you wrote:
to be really useful UEFI variables should be available t
On Mon, Jun 24, 2019 at 09:10:07PM +0200, Heinrich Schuchardt wrote:
> On 6/24/19 8:50 PM, Wolfgang Denk wrote:
> >Dear Heinrich,
> >
> >In message <7083d208-4b3c-7261-a03b-9066dc8d2...@gmx.de> you wrote:
> >>
> >>to be really useful UEFI variables should be available to the operating
> >>system. T
On 6/24/19 8:50 PM, Wolfgang Denk wrote:
Dear Heinrich,
In message <7083d208-4b3c-7261-a03b-9066dc8d2...@gmx.de> you wrote:
to be really useful UEFI variables should be available to the operating
system. This is not possible using U-Boot variables as storage.
Oops? Is it possible that you a
Dear Heinrich,
In message <7083d208-4b3c-7261-a03b-9066dc8d2...@gmx.de> you wrote:
>
> to be really useful UEFI variables should be available to the operating
> system. This is not possible using U-Boot variables as storage.
Oops? Is it possible that you are not aware of the
tools/env/fw_env* co
On 6/24/19 12:23 PM, Wolfgang Denk wrote:
Dear Heinrich,
In message <83a2d8c5-1b06-c502-8a63-dc3ca307d...@gmx.de> you wrote:
thanks a lot for the good online meeting this morning together with your
colleague Suggan where we discussed the requirements for the
implementation of non-volatile vari
Dear Heinrich,
In message <83a2d8c5-1b06-c502-8a63-dc3ca307d...@gmx.de> you wrote:
>
> thanks a lot for the good online meeting this morning together with your
> colleague Suggan where we discussed the requirements for the
> implementation of non-volatile variables in U-Boot.
>
> Currently UEFI
Hi Heinrich,
(+ Sughosh and Francois)
On Thu, 20 Jun 2019 at 11:06, Heinrich Schuchardt wrote:
>
> Hello Ilias,
>
> thanks a lot for the good online meeting this morning together with your
> colleague Suggan where we discussed the requirements for the
> implementation of non-volatile variables
Hello Ilias,
thanks a lot for the good online meeting this morning together with your
colleague Suggan where we discussed the requirements for the
implementation of non-volatile variables in U-Boot.
Currently UEFI variables are stored in U-Boot variables. Saving the
U-Boot variables will persist
23 matches
Mail list logo
