Re: Bug: libefibootguard corrupts efibootguard configuration

['Raphael Lisicki' via EFI Boot Guard]

On 19.02.25 17:49, Jan Kiszka wrote:
> On 19.02.25 17:30, 'Raphael Lisicki' via EFI Boot Guard wrote:
>> Hi Jan,
>>
>> On 19.02.25 16:56, Jan Kiszka wrote:
>>>
>>> We can simply make that usage of ebg_env_getglobalstate with NULL as
>>> parameter official. It was and it will be never used because that
>>> "global" in this function implies that a single, externally managed env
>>> cannot contribute anything to the call.
>>>
>>
>> At least in version 0.15-1 directly calling ebg_env_getglobalstate did not
>> work. It appeared to work but the returned result was always the same.
>> That's why Bjoerns snippet still contains ebg_env_open_current allthough
>> its return value is not used.
>>
>> ebg_env_open_current and others do some internal initialization (not
>> referenced by their returned handle) that is needed as well.
>>
> 
> That seems even more weird. All that should still be needed is bgenv_init.

I don't remember which function it was, maybe that one. I only remember that
the function was not declared in a system header. Linking by implicit
declaration worked, but seemed worse than the lone ebg_env_open_current.

> 
> Can you reproduce with the latest version as well?

I can try again tomorrow.


> 
> Jan
> 


best regards
Raphael

-- 
You received this message because you are subscribed to the Google Groups "EFI 
Boot Guard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to efibootguard-dev+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/efibootguard-dev/3f7c7f5b-b21a-4ec6-98e1-653dea8c0c44%40siemens.com.