mirror of
https://github.com/Atmosphere-NX/Atmosphere.git
synced 2024-11-26 13:52:21 +00:00
16 KiB
16 KiB
Changelog
0.8.2
- A number of bugs were fixed causing users to sometimes see
Key Derivation Failed!
.- KFUSE clock enable timings have been adjusted to allow time to stabilize before TSEC is granted access.
- A race condition was fixed that could cause wrong key data to be used on 6.2.0
- The TSEC firmware is now retried on failure, fixing a failure affecting ~1/50 boots on 6.2.0.
- A bug was fixed causing some modules to not work on firmware 1.0.0.
- A bug was fixed causing sleep mode to not work with debugmode enabled.
- As a result, debugmode is now enabled in the default BCT.ini.
- General system stability improvements to enhance the user's experience.
0.8.1
- A bug was fixed causing users to see
Failed to enable SMMU!
if fusee had previously rebooted.- This message will still occur sporadically if fusee is not launched from coldboot, but it can never happen twice in a row.
- A race condition was fixed in Atmosphere
bis_protect
functionality that could cause NS to be able to overwrite BCT public keys.- This sometimes broke AutoRCM protection, the current fix has been tested on hardware and verified to work.
- Support was added for enabling
debugmode
based on theexosphere
section ofBCT.ini
:- Setting
debugmode = 1
will cause exosphere to tell the kernel that debugmode is active. - Setting
debugmode_user = 1
will cause exosphere to tell userland that debugmode is active. - These are completely independent of one another, allowing fine control of system behavior.
- Setting
- Support was added for
nogc
functionality; thanks to @rajkosto for the patches.- By default,
nogc
patches will automatically apply if the user is booting into 4.0.0+ with fuses from <= 3.0.2. - Users can override this functionality via the
nogc
entry in thestratosphere
section ofBCT.ini
:- Setting
nogc = 1
will force enablenogc
patches. - Setting
nogc = 0
will force disablenogc
patches.
- Setting
- If patches are enabled but not found for the booting system, a fatal error will be thrown.
- This should prevent running FS without
nogc
patches after updating to an unsupported system version.
- This should prevent running FS without
- By default,
- An extension was added to
exosphere
allowing userland applications to cause the system to reboot into RCM:- This is done by calling smcSetConfig(id=65001, value=); user homebrew can use splSetConfig for this.
- On fatal error, the user can now choose to perform a standard reboot via the power button, or a reboot into RCM via either volume button.
- A custom message was added to
fatal
for when an Atmosphère API version mismatch is detected (2495-1623). - General system stability improvements to enhance the user's experience.
0.8.0
- A custom
fatal
system module was added.- This re-implements and extends Nintendo's fatal module, with the following features:
- Atmosphère's
fatal
does not create error reports. - Atmosphère's
fatal
draws a custom error screen, showing registers and a backtrace. - Atmosphère's
fatal
attempts to gather debugging info for all crashes, and not just ones that include info. - Atmosphère's
fatal
will attempt saving reports to the SD, if a crash report was not generated bycreport
.
- Atmosphère's
- This re-implements and extends Nintendo's fatal module, with the following features:
- Title flag handling was changed to prevent folder clutter.
- Instead of living in
atmosphere/titles/<tid>/%s.flag
, flags are now located inatmosphere/titles/<tid>/flags/%s.flag
- The old format will continue to be supported for some time, but is deprecated.
- Flags can now be applied to HBL by placing them at
atmosphere/flags/hbl_%s.flag
.
- Instead of living in
- Changes were made to the mitm API, greatly improving caller semantics.
sm
now informs mitm services of a new session's process id, enabling custom handling based on title id/process id.
- smhax is no longer enabled, because it is no longer needed and breaks significant functionality.
- Users with updated HBL/homebrew should see no observable differences due to this change.
- Functionality was added implementing basic protections for NAND from userland homebrew:
- BOOT0 now has write protection for the BCT public key and keyblob regions.
- The
ns
sysmodule is no longer allowed to write the BCT public keys; all other processes can.- This should prevent system updates from removing AutoRCM.
- No processes should be allowed to write to the keyblob region.
- The
- By default, BIS partitions other than BOOT0 are now read-only, and CAL0 is neither readable nor writable.
- Adding a
bis_write
flag for a title will allow it to write to BIS. - Adding a
cal_read
flag for a title will allow it to read CAL0.
- Adding a
- An automatic backup is now made of CAL0 on boot.
fs.mitm
maintains a file handle to this backup, so userland software cannot read it.
- To facilitate this,
fs.mitm
now mitms all sessions for non-system modules; content overriding has been made separate from service interception. - Please note: these protections are basic, and sufficiently malicious homebrew ++can defeat them++.
- Please be careful to only run homebrew software from sources that you trust.
- BOOT0 now has write protection for the BCT public key and keyblob regions.
- A bug involving HDCP titles crashing on newer firmwares was fixed.
- Support was added for system version 6.2.0; our thanks to @motezazer for his invaluable help.
- By default, new keys will automatically be derived without user input.
- Support is also present for loading new keys from
atmosphere/prod.keys
oratmosphere/dev.keys
- General system stability improvements to enhance the user's experience.
0.7.5
- DRAM training was added to fusee-secondary, courtesy @hexkyz.
- This greatly improves the speed of memory accesses during boot, resulting in a boot time that is ~200-400% faster.
- creport has had its code region detection improved.
- Instead of only checking one of the crashing thread's PC/LR for code region presence, creport now checks both + every address in the stacktrace. This is also now done for every thread.
- This matches the improvement Nintendo added to official creport in 6.1.0.
- The code region detection heuristic was further improved by checking whether an address points to .rodata or .rwdata, instead of just .text.
- This means that a crash appears in a loaded NRO (or otherwise discontiguous) code region, creport will be able to detect all active code regions, and not just that one.
- Instead of only checking one of the crashing thread's PC/LR for code region presence, creport now checks both + every address in the stacktrace. This is also now done for every thread.
0.7.4
- libstratosphere has been completely refactored/rewritten, and split into its own, separate submodule.
- While this is mostly "under the hood" for end-users, the refactor is faster (improving both boot-time and runtime performance), more accurate (many of the internal IPC structures are now bug-for-bug compatible with Nintendo's implementations), and significantly more stable (it fixes a large number of bugs present in the old library).
- The refactored API is significantly cleaner and easier to write system module code for, which should improve/speed up development of stratosphere.
- Developers looking to write their own custom system modules for the Switch can now easily include libstratosphere as a submodule in their projects.
- Loader was extended to add a new generic way to redirect content (ExternalContentSources), courtesy @misson20000:
- A new command was added to ldr:shel, taking in a tid to redirect and returning a session handle.
- When the requested TID is loading, Loader will query the handle as though it were an IFileSystem.
- This allows clients to generically define their own filesystems, and override content with them in loader.
- fs.mitm has gotten several optimizations that should improve its performance and stability:
- RomFS redirection now only occurs when there is content to redirect, even if the title is being mitm'd elsewhere.
- A cache is now maintained of the active data storage, if any, for all opened title IDs. This means if two processes both try to open the same archive, fs.mitm won't duplicate any of its work.
- RomFS metadata is now cached to the SD card on build instead of being persisted in memory -- this greatly reduces memory footprint and allows fs.mitm to redirect more titles simultaneously than before.
- A number of bugs were fixed, including:
- A resource leak was fixed in process creation. This fixes crashes that occur when a large number (>32) games have been launched since the last reboot.
- fs.mitm no longer errors when receiving a zero-sized buffer. This fixes crashes in some games, including The Messenger.
- Multi-threaded server semantics should no longer cause deadlocks in certain circumstances. This fixes crashes in some games, including NES Classics.
- PM now only gives full FS permissions to the active KIPs. This fixes a potential crash where new processes might be unable to be registered with FS.
- The
make dist
target now includes the branch in the generated zip name. - General system stability improvements to enhance the user's experience.
0.7.3
- Loader and fs.mitm now try to reload loader.ini before reading it. This allows for changing the override button combination/HBL title id at runtime.
- Added a MitM between set:sys and qlaunch, used to override the system version string displayed in system settings.
- The displayed system version will now display
<Actual version> (AMS <x>.<y>.<z>)
.
- The displayed system version will now display
- General system stability improvements to enhance the user's experience.
0.7.2
- Fixed a bug in fs.mitm's LayeredFS read implementation that caused some games to crash when trying to read files.
- Fixed a bug affecting 1.0.0 that caused games to crash with fatal error 2001-0106 on boot.
- Improved filenames output by the make dist target.
- General system stability improvements to enhance the user's experience.
0.7.1
- Fixed a bug preventing consoles on 4.0.0-4.1.0 from going to sleep and waking back up.
- Fixed a bug preventing consoles on < 4.0.0 from booting without specific KIPs on the SD card.
- An API was added to Atmosphère's Service Manager for deferring acquisition of all handles for specific services until after early initialization is completed.
- General system stability improvements to enhance the user's experience.
0.7.0
- First official release of Atmosphère.
- Supports the following featureset:
- Fusée, a custom bootloader.
- Supports loading/customizing of arbitrary KIPs from the SD card.
- Supports loading a custom kernel from the SD card ("/atmosphere/kernel.bin").
- Supports compile-time defined kernel patches on a per-firmware basis.
- All patches at paths like /atmosphere/kip_patches//.ips will be applied to the relevant KIPs, allowing for easy distribution of patches supporting multiple versions.
- Both the IPS and IPS32 formats are supported.
- All patches at paths like /atmosphere/kernel_patches//.ips will be applied to the kernel, allowing for easy distribution of patches supporting multiple versions.
- Both the IPS and IPS32 formats are supported.
- Configurable by editing BCT.ini on the SD card.
- Atmosphère should also be launchable by the alternative hekate bootloader, for those who prefer it.
- Exosphère, a fully-featured custom secure monitor.
- Exosphere is a re-implementation of Nintendo's TrustZone firmware, fully replicating all of its features.
- In addition, it has been extended to provide information on current Atmosphere API version, for homebrew wishing to make use of it.
- Stratosphère, a set of custom system modules. This includes:
- A loader system module.
- Reimplementation of Nintendo's loader, fully replicating all original functionality.
- Configurable by editing /atmosphere/loader.ini
- First class support for the Homebrew Loader.
- An exefs NSP (default "/atmosphere/hbl.nsp") will be used in place of the victim title's exefs.
- By default, HBL will replace the album applet, but any application should also be supported.
- Extended to support arbitrary redirection of executable content to the SD card.
- Files will be preferentially loaded from /atmosphere/titles//exefs/, if present.
- Files present in the original exefs a user wants to mark as not present may be "stubbed" by creating a .stub file on the SD.
- If present, a PFS0 at /atmosphere/titles//exefs.nsp will fully replace the original exefs.
- Redirection is optionally toggleable by holding down certain buttons (by default, holding R disables redirection).
- Full support for patching NSO content is implemented.
- All patches at paths like /atmosphere/exefs_patches//.ips will be applied, allowing for easy distribution of patches supporting multiple firmware versions and/or titles.
- Both the IPS and IPS32 formats are supported.
- Extended to support launching content from loose executable files on the SD card, without requiring any official installation.
- This is done by specifying FsStorageId_None on launch.
- A service manager system module.
- Reimplementation of Nintendo's service manager, fully replicating all original functionality.
- Compile-time support for reintroduction of "smhax", allowing clients to optionally skip service access verification by skipping initialization.
- Extended to allow homebrew to acquire more handles to privileged services than Nintendo natively allows.
- Extended to add a new API for installing Man-In-The-Middle listeners for arbitrary services.
- API can additionally be used to safely detect whether a service has been registered in a non-blocking way with no side-effects.
- Full API documentation to come.
- A process manager system module.
- Reimplementation of Nintendo's process manager, fully replicating all original functionality.
- Extended to allow homebrew to acquire handles to arbitrary processes, and thus read/modify system memory without blocking execution.
- Extended to allow homebrew to retrieve information about system resource limits.
- Extended by embedding a full, extended implementation of Nintendo's boot2 system module.
- Title launch order has been optimized in order to grant access to the SD card faster.
- The error-collection system module is intentionally not launched, preventing many system telemetry error reports from being generated at all.
- Users may place their own custom sysmodules on the SD card and flag them for automatic boot2 launch by creating a /atmosphere/titles/
- A loader system module.
- Fusée, a custom bootloader.