So I can't believe I'm asking this again. But where the fuck is the source code for BOOTX64.efi for linux ?

And why when i run strings BOOTX64.efi does the word microsoft show up ?

Microsoft Time-Stamp PCA 20100

20220615030002Z

20220616030002Z0w0=

1/0-0

1(0&0

\MWG

Washington1

Redmond1

Microsoft Corporation1&0$

Microsoft Time-Stamp PCA 2010

?t}k

~0|1

Washington1

Redmond1

Microsoft Corporation1&0$

Microsoft Time-Stamp PCA 2010

ep"A

<q

{q<Y

ViJ5

@sqOgY

}!zyw

9C[3/

Looks like key ownership entries.

amusingly placed right at the end of 1000s of strings just to mock me.

Its part of grub2
And the microspft in the strings come from the certificate that is used in grub to sign it. It needs to be signed by Microsoft because they are the only CA that in the UEFIs.

@stop yeah i was just looking at the code.

its using that filename as a destination gonna have to trace awhile to figure out where the damn source itself is !

@stop hehe didn't immediately find it when i downloaded the source again yesterday :P course I was in a piss poor i want the world to die mood yesterday as well. their fault as usual.

@stop drags from core_name which resolves to core.efi, core.elf etc

trying to find a target somewhere heh

@stop are there any utilities that visualize how a variable reaches its value at a point in c ? or at least tries showing different composition points ?

@intrusioncm @stop

https://pastebin.com/PUA9GMCc

why is it using braces randomly without being part of a code block for a conditional or loop ?

@AvatarOfKaine i only know that its no problem in c

@stop weird. you'd think there would be a purpose, maybe its supposed to be visually organized. eh. just grouping like statements together for the maintainers benefit.

@AvatarOfKaine

https://wiki.mageia.org/en/...

Read that. Fully.

BootX64 usually is the Microsoft bootloader payload... Which is installed to this location as it is the default location stored in the NVRAM.

Regarding the C code.

Seems like scoping, Grub probably has a very old C standard to compile to - due to it being extremely low level.

do you know how much it bothers me that they try to offer me there bullshit based on thej color of a fucking hoody that was the only one that was available ?

or that they make these stupid associations with their retard shit at all ?

I have no idea how their stupid shit works except to try to make people look bad or confuse someone who's looking for them when in reality they likely already mostly know.

this is simple harassment.

keep your freak shit to yourselves.

you can have all the women in the world bend over, don't mind that but it does get a little excessive sometimes and i'm not going to fuck them if they're going to destroy another generation they can just sit there get tormented and get nothing just like they should be, in lieau of being shot.

but quit this shit asshole or one of these fucks will get slice up :)

@AvatarOfKaine

What the frigging fuck are you talking about?

Need a pan over the head couple of times to get the looney tunes whacked out?

@IntrusionCM see. That's the standard repeat response along with the "ageless" women showing up in the same order with a copy of a previous kid and more cellulite

@IntrusionCM John loves daddy to death with a shovel :) all over again lol as in you bitched like this previously and or a bot repeated it

@AvatarOfKaine honestly, your sane side is more appealing.

Your insane side is plain annoying...

@IntrusionCM every side is my sane side there is no insane side there is only aggravated by something people are doing or did or unencumbered by unwanted negative emotion

Meanwhile all this repetition can eat a really big dick ? I'm listening to the same group of male whores much aged have the same conversation.

If people want less crazy move them to a whorebouse and then to a morgue later if they're chomos and get it over with

The world didn't used to be this nuts and stupid

@IntrusionCM and don't pot calls the kettle black me jackass

@IntrusionCM basically you people reduced existence to factory work for a bunch of old people with liver spots on their dicks and money in their hand to your own fucked up detriments

@IntrusionCM and took those nasty old dicks meanwhile

@IntrusionCM *slow applause*

Booya !

https://gist.github.com/deitch/...

I thought mkimage did something else

Betcha the format for uefi binaries is in there too yay

@AvatarOfKaine

I still have no idea what triggered your outburst...

But these files just run on a default grub-mkconfig.

https://manpages.ubuntu.com/manpage...

Grub mkimage just generates the bootable payload, installs it to the *default NVRAM* location so there is no configuration needed. Same as Microshit does.

Except that Microshit contains the payload to load BCD.

@IntrusionCM well what i'm looking for is where those initial 'fallback' bootloaders come from that the uefi firmware loads. i want to know how they are generated.

@AvatarOfKaine the fallback I'm talking about is just the name bootX64.efi

https://universalscalablefirmware.github.io/...

Should contain all knowledge you need.

It'sproprietairy. You can't see it.

@NoToJavaScript that makes no sense because you have to sign images you create that aren't trusted.

@AvatarOfKaine and then you can't boot these images without puting your machine at risk (eg : disactivating secure boot).

If you need to disactivate secure boot in any way, well you are :

1. Experementing

2. doing it for fuin

NO system for day to day usage should have TPM and secure boot disabled, ever

@NoToJavaScript well yeah or that or you suspect the vendor bugged things and you're working on as clean an offline system as you can to create a new boot image :P

in a way the mbr method was good in that it was pretty easy to determine what was going on even with mbr boot sector viruses fucking things up.

@NoToJavaScript its like android. you can see all the source except one proprietary binary :P who the hell knows whats in it ?

well someone who knows the binary format and can descramble and then decompile it.

noone else.