-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I was working on some Grub2 module a few days ago and I spent a lot of
time on this. Basically, I was unable to correctly generate the file
command.lst; my new commands simply didn't appeared in it.
I finally found that gen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pavel Roskin a écrit :
> On Thu, 2009-07-02 at 00:34 +0200, Duboucher Thomas wrote:
>
>> I was working on some Grub2 module a few days ago and I spent a lot of
>> time on this. Basically, I was unable to correctly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pavel Roskin a écrit :
>> LUA integration.
>> LUA is quite powerful, it's more suitable to do complicated task than
>> sh script. For example, we can use it to detect os at runtime,
>> implement simple commands, or draw the graphic menu.
>
> Yes, I th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was reading the code and now I have a question. You are creating a
grub librairy writen in C including useful functions such as
'grub.file_open'. But in your implementation, you removed base libraries
such as 'os' and 'io'. So why don't you j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> [1] http://michael.gorven.za.net/bzr/grub/luks
>
I have a stupid question what's the difference between the tip in
your Mercurial repository[1] and the head in your Bazaar repository[2]?
[1] http://michael.gorven.za.net/hg/grub/luks/
[2] http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Gorven a écrit :
> On Monday 17 August 2009 19:15:23 Duboucher Thomas wrote:
>> I have a stupid question what's the difference between the tip in
>> your Mercurial repository[1] and the head in your Bazaar rep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The Mercurial code is not up to date with the GRUB2 trunk, but is only
> missing
> a minor addition to the new crypto code. I've created a tarball[1] of the
> latest code if that helps.
>
Thanks a lot! I'll check that out tomorrow.
I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> 1) Technical Aspects
>
>
>>From a purely technical point of view, the TPM support in GRUB is about
> the "Trusted Boot" with a partial support and a full one.
>
> Partial support means that GRUB is able to (TPM commands are ta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isaac Dupree a écrit :
> Suppose you are the proud technical support person at a third-world
> school that just bought a thousand OLPC XOs. You, as part of your
> country's government, are instructed to own those XOs. If they are
> stolen and get int
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
>>> 2) Ethical Aspects
>>> ==
>>>
>> Every technology has its evil uses, so does TPM. However, there's a very
>> large gap between currently implemented solutions and what you suggest.
> How can y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
>> I can imagine a world with computers you can access from free and from
>> whom you can boot with your USB pen-drive (or trust the installed OS, or
>> whatever you want). But this world is still far away from h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
> But why does a third instance (manufacturer) need to trust my key?
> Only one: he wants a control.
I don't see where the TPME needs to trust the EKP in the specification.
>> Also, most of the time, the reset
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
> Could you please avoid using abbreviations. It's already hard to read
> TPM specs because of their twisted terminology. If EKP is the key
> stored in the TPM then manufacturer can keep a copy of public or
> pri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
> There is a point in keeping them - remote atestation. Why do I need
> manufacturer to sign my key?
No, the endorsement key pair is not used in remote attestation. Only to
generate one time key pairs for owners
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
> How many record labels will not jump on occasion of an efficient DRM?
In France, they still believe it takes three days for a .mp3 to travel
from Japan to France ...
> How many banks will resist the temptatio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michal Suchanek a écrit :
>>> Without threat model we're speaking placebo.
>>>
>> Stoned Bootkit?
>
> Coreboot can prevent that as well as TPM can.
>
Coreboot can be "stoned" as easily as your MBR since you can easily
rewrite the MBR from the softwa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
> You can remove TPM too
And if you remove the TPM, how do you retrieve the secret? oO
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michal Suchanek a écrit :
> 2009/8/20 Michael Gorven :
>> On Thursday 20 August 2009 10:20:02 Michal Suchanek wrote:
>>> 2009/8/20 Michael Gorven :
On Thursday 20 August 2009 09:59:42 Michal Suchanek wrote:
> 2009/8/20 Michael Gorven :
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
>>> It's also what I meant. Most sysadmins just need someone to blame if
>>> it goes wrong.
>> Oh great, so all we need to provide is someone to blame! Problem solved!
> Unfortunately in some cases it's really so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Seems that my smtp was down :|
Michal Suchanek a écrit :
> 2009/8/20 Michael Gorven :
>> On Thursday 20 August 2009 10:20:02 Michal Suchanek wrote:
>>> 2009/8/20 Michael Gorven :
On Thursday 20 August 2009 09:59:42 Michal Suchanek wrote:
> 20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Millan a écrit :
> On Sun, Sep 06, 2009 at 02:19:54PM +0200, Yves Blusseau wrote:
>> Is it ok to commit ?
>
> Please wait a few more days. It's doubtful that anyone would be interested
> (and capable) of reviewing ruby code, but it's still wor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
> Bean wrote:
>> On Mon, Nov 9, 2009 at 9:50 PM, Vladimir 'phcoder' Serbinenko
>> wrote:
>>
>> Hi,
>>
>> int
>> grub_auth_strcmp (const char *s1, const char *s2)
>> {
>> int ret;
>> grub_uint64_t end;
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bean a écrit :
>
> Hi,
>
> This one work:
>
> int
> auth_strcmp (const char *s1, const char *s2)
> {
> int result = 0;
>
> while (1)
> {
> result += (*s1 != *s2);
> if (*s1 == 0)
> break;
>
> s1++;
> s2++;
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
> Duboucher Thomas wrote:
>> Bean a écrit :
>>> Hi,
>>> This one work:
>>> int
>>> auth_strcmp (const char *s1, const char *s2)
>>> {
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Millan a écrit :
> On Mon, Nov 09, 2009 at 10:43:48PM +0100, Duboucher Thomas wrote:
>> Well, the only way to solve that problem would be IMHO to add a limit
>> to the size of s2, and use this maximum size as an end co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bean a écrit :
> Hi,
>
> Oh, I just come up with a better way to do this:
>
> typedef char grub_password_t[1024];
>
> int
> grub_auth_strcmp (const grub_password_t s1, const grub_password_t s2)
> {
> char r1 = 0;
> char r2 = 0;
> char *p;
> int
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
richardvo...@gmail.com a écrit :
>
> for (it = retval = 0; it < PASSPHRASE_MAXSIZE; it++, input++, key++)
>
>> After changing the parameter type, those postincrements won't do what
>> you expect.
>
Damn examinations; I really need to sleep! =)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bean a écrit :
>
> Hi,
>
> My previous function ensures that execution time is the same
> regardless of the input. Although it's not necessary, I guess it's a
> nice feature to have. BTW, the simpler function does leak one
> information, the size of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir 'phcoder' Serbinenko a écrit :
> With this change grub_auth_strcmp becomes a misnomer. I would prefer to
> call it grub_auth_memcmp then. I'll also look into which other free
> secure strcmp are available
Asking developpers of project
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johannes Bauer a écrit :
> Johannes Bauer schrieb:
>
>> I've read a whole lot about problems booting Windows through Grub - but
>> found no solution at all. By playing around with the options, I found a
>> solution which *almost* works:
>
> [...] Usi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felix Zielcke a écrit :
> MBR would be (hd1) or (hd0) not (hd1,1)
>
> But maybe it's really like Vladimir thinks and Truecrypt loader and
> windows bootloader are different in this case.
>
If you have a 'pro' version of Windows Seven, you can give a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Jones a écrit :
> On Thu, Dec 03, 2009 at 10:16:17AM EST, Vladimir 'φ-coder/phcoder' Serbinenko
> wrote:
>> Chris Jones wrote:
>
>>> I am trying to have grub boot off a partition on a USB stick.
>>>
>>>
>> You can't chainload to disk invisib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 18/07/2010 10:45, James Courtier-Dutton a écrit :
> Hi,
>
> Is there any encryption support in grub?
>
> Summary:
> Permit grub boot menu to be in LUKS encrypted partition.
>
> Kind Regards
>
> James
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 05/11/2010 23:02, Evan Broder a écrit :
> Hi again -
> Having actually tried to work with this patch, I realized that I
> wanted a little more information passed into the callback function. I
> also realized that it's rather difficult to do thin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 06/11/2010 21:12, Evan Broder a écrit :
> Sure, I'd be happy to submit a new patch that leaves the bit mangling
> out if that library could be added. Can you point me at the specific
> version of bitlib that Lua 5.2 will be using? The only bitlib I
35 matches
Mail list logo
