Re: [Trustedgrub-users] Kernel upgrade question

[Olga G. <ol...@gm...>]

Hi Marcel,

So I downloaded a .deb package for the 2.6.34.1-blackjack kernel and
installed it using dpkg. That booted with no problems with TrustedGrub!
Apparently, if you use the package manager, then the new kernel installs and
boots fine. I guess there was something wrong with my manual install.

Actually, that brings up another question. I guess, I am not quite sure what
is going on behind the scenes in TrustedGrub. Why is it that if you upgrade
the kernel, the new kernel image and initrd hashes are instantly verified?
Shouldn't that verification fail because we've just overwritten the original
version (the one running when TrustedGrub was installed)? Is there a
document that describes what TrustedGrub is doing exactly?

best regards,
Olga

On Thu, Sep 30, 2010 at 10:28 AM, Olga Gelbart <ol...@gm...> wrote:

> Hi Marcel,
> I don't have Grub2 installed, because I have been using the same system
> since Ubuntu 9.04 (which still have grub 0.97). I just kept upgrading, so
> grub2 never got installed. Then I just installed TrustedGrub over 0.97 grub.
> What's interesting is that I just ran the update manager and updated my
> currently-running 2.6.32-24 kernel to 2.6.32-25, and that booted fine in
> TrustedGrub!
> In order to install 2.6.34.1 kernel, I downloaded the source, configured,
> compiled and installed it manually. Maybe I missed some step in the process?
>
> thanks,
> Olga
>
>
> On Thu, Sep 30, 2010 at 9:28 AM, Marcel Selhorst <m.s...@si...>wrote:
>
>> Hi Olga,
>>
>> I think the problem is, that Ubuntu usually comes with GRUB-2 and thus
>> updates only the "grub.cfg" file instead of the "menu.lst".
>> I think they had an update to 2.6.32-25, so you might need to change the
>> filenames from 2.6.32-24 to 2.6.32-25 in the following lines:
>> kernel= ...
>> initrd= ...
>>
>> Then, if you can boot, re-do the same thing in the /boot/grub/menu.lst and
>> save.
>>
>> Best regards,
>> Marcel
>>
>> Am 30.09.2010 15:08, schrieb Olga Gelbart:
>> > Hello everyone,
>> > I have currently running Ubuntu 10.04 with TrustedGrub 1.1.5 and the
>> kernel
>> > version 2.6.32-24. Yesterday I had to compile and install a newer
>> version of
>> > the kernel, 2.6.34.1. Of course now TrustedGrub fails on kernel
>> > verification:
>> > it is still looking for the 2.6.32-24 version and is giving me "Error
>> 15:
>> > File not found" error. I tried to re-install TrustedGrub by running
>> > grub-install again, but that does not help. I am happy that TrustedGrub
>> is
>> > doing what it is supposed to do, the can someone recommend what I have
>> to do
>> > to upgrade to a new kernel and have TrustedGrub verify it as well.
>> >
>> > thanks,
>> > Olga
>> >
>> >
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Start uncovering the many advantages of virtual appliances
>> > and start using them to simplify application deployment and
>> > accelerate your shift to cloud computing.
>> > http://p.sf.net/sfu/novell-sfdev2dev
>> >
>> >
>> >
>> > _______________________________________________
>> > Trustedgrub-users mailing list
>> > Tru...@li...
>> > https://lists.sourceforge.net/lists/listinfo/trustedgrub-users
>>
>> --
>> Sirrix AG security technologies -- http://www.sirrix.com
>> Dipl.-Ing. Marcel Selhorst  eMail: m.s...@si...
>> Tel: +49 (234) 610071-126   Fax: +49 (234) 610071-526
>> Tel: +49 (681)  95986-126   Fax: +49 (681)  95986-526
>> Get my public key from keyserver, KeyId: 0x7C9821CC
>> Fingerprint 4138 E617 E62E 79D3 E663 BE5A 14E7 1CD8 7C98 21CC
>>
>> Vorstand: Ammar Alkassar (Vors.), Christian Stueble
>> Vorsitzender des Aufsichtsrates: Prof. Dr. Kai Rannenberg
>> Sitz der Gesellschaft: Homburg/Saar, HRB 3857 Amtsgericht Saarbruecken
>>
>> This message may contain confidential and/or privileged information.
>> If you are not the addressee, you must not use, copy, disclose or
>> take any action based on this message or any information herein.
>> If you have received this message in error, please advise the sender
>> immediately by reply e-mail and delete this message.
>>
>
>