Hacking Question About Hekate's Configuration File

[starburst]

I bought this Switch last May but it was never used for almost a year, until yesterday. Its firmware is 4.0.1.

I followed this guide [1] and made a NAND backup using the latest version of Hekate. For this, I used the basic hekate_ipl.ini provided in the guide.
Then I enabled AutoRCM, loaded Atmosphere and updated the system to 6.2.0 using ChoiDujourNX. I did not understand it, but just in case I replaced the basic hekate_ipl.ini file with the template provided directly by Hekate's developer(s). [2]

After using ChoiDujourNX, I noticed that another hekate_ipl.ini had been created in the root of the SD card. A security measure, I assume. This file only reads:

[stock_DANGEROUS]
[PreventGCUpdate]
kip1patch=nogc

Now, the more complete, template file includes this line:

[line 8] autonogc=1

Do both configuration options refer to the same setting? Can I only use the more complete one? Which one takes precedence, the one in the bootloader directory?
I understand that applications such as ChoiDujourNX may need to specify their own settings to the boot loader, for they deal with important system changes (a firmware upgrade, none the less.) What I do not understand is why this file was created at the root of the SD at not within an application-specific or 'rules' directory within the bootloader one. It is not easy to tell which one takes precedence.

Related to this, are there any particular settings that one should specify to allow playing backups?
I grabbed the latest version of the patches and placed them within the atmosphere directory. But I have read messages referring to the disabling of signature checks within Hekate.


1. https://switchgui.de/switch-guide/
2. https://github.com/CTCaer/hekate/blob/master/res/hekate_ipl_template.ini

 

[Draxzelex]

Unfortunately, ChoiDujoruNX creates a new hekate_ipl.ini file based on outdated versions of Hekate where it read the ini file from the root as opposed to within the bootloader folder. However that doesn't really matter here as the nogc patch is useless to you since your cartridge slot has already been updated since your console was running a firmware above 4.0 before the update which is when the cartridge slot was applied.

 

[starburst]

Thanks on your answer, mate. I thought that version 4.x was still part of old cartridge slot controller.

About the duplicate Hekate configuration files, are both settings the same? Should I leave them as is? Copy the ChoiDujourNX's setting within the more complete one in the bootloader directory?
I am interested in the general procedure, even if this particular setting is useless in my case, for this could happen in the future with a relevant setting.

 

[Draxzelex]

Thanks on your answer, mate. I thought that version 4.x was still part of old cartridge slot controller.

About the duplicate Hekate configuration files, are both settings the same? Should I leave them as is? Copy the ChoiDujourNX's setting within the more complete one in the bootloader directory?
I am interested in the general procedure, even if this particular setting is useless in my case, for this could happen in the future with a relevant setting.

Like I said, newer versions of Hekate read the hekate_ipl.ini file in the bootloader folder, not on the root. Unless you're booting an old version of Hekate, of which there is no reason to, then having a hekate_ipl.ini file on the root is useless because Hekate won't read it. ChoiDujourNX automatically makes a hekate_ipl.ini file with the nogc patch whenever it detects you are installing a firmware of 4.0 or higher which is not useful because some people may already be updating from a firmware above 4.0 meaning their cartridge slot is already updated.

 

[starburst]

Unless you're booting an old version of Hekate, of which there is no reason to, then having a hekate_ipl.ini file on the root is useless because Hekate won't read it.

Crystal clear, mate. Thanks.