Homebrew Question TINFOIL 8.0 /8.0.1 help

[Lacius]

I see you missed the keyword being "native" which means " built into a given system."

As far as your claims of "there is no evidence." You're easily able to recreate the issue using Atmosphere 8.0 and choiNX 1.0.1.

That's not how you phrased it in your first post.

If you want to recreate the issue, be my guest. Until then, your claims are probably baseless.

 

[Crusatyr]

That's not how you phrased it in your first post.

If you want to recreate the issue, be my guest. Until then, your claims are probably baseless.

maybe not in my first post, but 100% I did in my second.

As far as the second point goes, I doubt you'll listen to me even if I was able to recreate it, but the fact is, ChoiNX literally updated to 1.0.2 to add bis_checks and further prevent people from bricking their units if they were ipatched.

 

[Lacius]

maybe not in my first post, but 100% I did in my second.

I'm not particularly interested in arguing semantics. I was making a point about your first post.

As far as the second point goes, I doubt you'll listen to me even if I was able to recreate it, but the fact is, ChoiNX literally updated to 1.0.2 to add bis_checks and further prevent people from bricking their units if they were ipatched.

1.0.2 (26.04.2019) ChoiDujourNXv102.zip - Add bis_protect checks and disable AutoRCM option if unit is ipatched

 

[Crusatyr]

ChoiDujourNXv102.zip - Add bis_protect checks and disable AutoRCM option if unit is ipatched

Thats literally what I said isn't it? I wonder how bad you could mess something up if you tried to do something to a system without checking if you could do that thing? Or worse, Imagine trying to start a system update, but only being able to write a small portion of the update files. Like, I dunno. Boot0/1 being locked so you can't write to them, but being able to update the non-bis parts of the system firmware.

 

[Lacius]

Thats literally what I said isn't it?

No. The ChoiDujourNX 1.0.2 update was in response to having an exploit on ipatched systems that shouldn't be updated with AutoRCM installed, not Atmosphere's security.

Thats literally what I said isn't it? I wonder how bad you could mess something up if you tried to do something to a system without checking if you could do that thing? Or worse, Imagine trying to start a system update, but only being able to write a small portion of the update files. Like, I dunno. Boot0/1 being locked so you can't write to them, but being able to update the non-bis parts of the system firmware.

That's not what the protection does.

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.
• 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.
• 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.

As you put it, you might want to, well, educate yourself.

 

[Crusatyr]

Look man, Imma back down from this, but I do know it happened. You can look at Atmo's releases and see where he fixed issues with the bis_protect stuff. It's the same bug that caused TX's issues with SX OS 2.9 and updating. After all, it's just a rebranded Atmosphere.

 

[blawar]

@Lacius you keep saying atmosphere has security that is designed to prevent malicious software. By scires own admission it does not do this, because it doesn’t. Any homebrew app can write to nand and brick the system on vanilla atmosphere.

As for your claim that tinfoils security being bypassed with gamecart dunps, this is patently false, all ncas are verified for Nintendo’s signature unless the the user enables installed unsigned code, even game arts. You keep arguing about the nand stuff when you don’t have an argument. You just don’t like being forced to do something to run the software.

As I told you before, incognito being removed is irrelevant, it still needs nand write access for firmware installs, and other certain functions (more to be added later). Just stay on 7.01 if you don’t want to remove atmosphere’s bis write blocks.

 

[Lacius]

@Lacius you keep saying atmosphere has security that is designed to prevent malicious software. By scires own admission it does not do this, because it doesn’t. Any homebrew app can write to nand and brick the system on vanilla atmosphere.

As for your claim that tinfoils security being bypassed with gamecart dunps, this is patently false, all ncas are verified for Nintendo’s signature unless the the user enables installed unsigned code, even game arts. You keep arguing about the nand stuff when you don’t have an argument. You just don’t like being forced to do something to run the software.

As I told you before, incognito being removed is irrelevant, it still needs nand write access for firmware installs, and other certain functions (more to be added later). Just stay on 7.01 if you don’t want to remove atmosphere’s bis write blocks.

The code we are talking about exists in response to prodinfo brickers, and it works. It doesn't matter that the security isn't 100% effective against all possible threats. Nobody claimed it was, so saying so is irrelevant to the conversation.

My point about cartridge dumps refers to the fact that you have to disable the Tinfoil security measures to install particular cartridge dumps.

I haven't said anything that isn't true, and you have not provided any real reason to disable Atmosphere's security for Tinfoil. It is needed for Incognito and, allegedly, firmware installs. However, a.) You said Incognito isn't going to remain a part of Tinfoil, b.) People aren't using Tinfoil for Incognito, c.) ChoiDujourNX does firmware installs without disabling the security, d.) The core features of Tinfoil don't require the privledges you're wanting to impose, and e.) If Atmosphere's security is so easy to bypass and basically non-existent, then stop complaining about it and do so; how you talk about it, it basically doesn't exist already anyway.

We've been down this road before. You're disabling the security because you personally don't like it, even though it's actually a good thing to have. There's a community of people who don't want to be forced to use a kip that disables security features for no reason. If your goal is for as many people as possible to use Tinfoil and be happy with it, you're making a poor decision. All you have to do is a.) Don't use the kip, or b.) Don't require the kip for the core functions of Tinfoil. It's not hard to do. It's clearly your prerogative, of course, but I don't know why you would intentionally inconvenience users or force something unnecessary on those who don't want it.

Using an old version of Tinfoil is not a viable long-term solution, which will necessitate the use and advocation of something else entirely.

There's a picture of you overlayed on the Council of Ricks on the Discord, and the irony isn't lost on me that the Council of Ricks had their heads so far up their asses that they refused to listen to reason, and it was eventually their undoing.

All of the above aside, people are going to have fewer problems, and you're going to have fewer headaches, with fewer dependencies, and the kip is a dependency. That alone is reason enough not to require the kip.

 

[blawar]

The code we are talking about exists in response to prodinfo brickers, and it works. It doesn't matter that the security isn't 100% effective against all possible threats. Nobody claimed it was, so saying so is irrelevant to the conversation.

My point about cartridge dumps refers to the fact that you have to disable the Tinfoil security measures to install particular cartridge dumps.

I haven't said anything that isn't true, and you have not provided any real reason to disable Atmosphere's security for Tinfoil. It is needed for Incognito and, allegedly, firmware installs. However, a.) You said Incognito isn't going to remain a part of Tinfoil, b.) People aren't using Tinfoil for Incognito, c.) ChoiDujourNX does firmware installs without disabling the security, d.) The core features of Tinfoil don't require the privledges you're wanting to impose, and e.) If Atmosphere's security is so easy to bypass and basically non-existent, then stop complaining about it and do so; how you talk about it, it basically doesn't exist already anyway.

We've been down this road before. You're disabling the security because you personally don't like it, even though it's actually a good thing to have. There's a community of people who don't want to be forced to use a kip that disables security features for no reason. If your goal is for as many people as possible to use Tinfoil and be happy with it, you're making a poor decision. All you have to do is a.) Don't use the kip, or b.) Don't require the kip for the core functions of Tinfoil. It's not hard to do. It's clearly your prerogative, of course, but I don't know why you would intentionally inconvenience users or force something unnecessary on those who don't want it.

Using an old version of Tinfoil is not a viable long-term solution, which will necessitate the use and advocation of something else entirely.

There's a picture of you overlayed on the Council of Ricks on the Discord, and the irony isn't lost on me that the Council of Ricks had their heads so far up their asses that they refused to listen to reason, and it was eventually their undoing.

All of the above aside, people are going to have fewer problems, and you're going to have fewer headaches, with fewer dependencies, and the kip is a dependency. That alone is reason enough not to require the kip.

Tinfoil Will verify and install xci cart dumps just fine, it just can’t verify nsp converts because they are modified, but between awoo, tinfoil, and ax’s built in installer, people shouldn’t be installing nsp converts anyway.

you are misinformed about atmosphere’s cal0 protection. It does an ok job of stopping homebrew apps from stealing personal data, but it does almost nothing to stop cal0 bricks. A slightly modified version of brickachu would run fine in atmosphere.

users should be using some form of incognito no matter which cfw they are using, to prevent personal info theft.

 

[Lacius]

Tinfoil Will verify and install xci cart dumps just fine, it just can’t verify nsp converts because they are modified, but between awoo, tinfoil, and ax’s built in installer, people shouldn’t be installing nsp converts anyway.

Right, but you seem to have unfortunately missed the point. I'm not arguing Tinfoil's security is a bad thing; I think it's a good thing. I'm telling you there are situations when the user is going to want to manually disable it, so it's by your logic these kinds of restrictions of privledges shouldn't even exist.

We're also not talking about something limited to NSP installations. We are also talking about malicious homebrew applications. Tinfoil does not protect against those, but Atmosphere largely does.

you are misinformed about atmosphere’s cal0 protection. It does an ok job of stopping homebrew apps from stealing personal data, but it does almost nothing to stop cal0 bricks. A slightly modified version of brickachu would run fine in atmosphere.

The argument isn't whether or not Atmosphere's security is 100% effective (it isn't). Bringing it up doesn't contradict anything I've said in my previous posts.

users should be using some form of incognito no matter which cfw they are using, to prevent personal info theft.

I agree. So what?

I find it interesting you ignored most of the points I made in my last point. I also find it interesting you're obsessed with Atmosphere's cal0 protection as though it's at all relevant to Tinfoil. Incognito is the only thing that needs to bypass it. There is literally no reason for Tinfoil to need it. Stop acting like there is.

 

[MikeNS]

Had no luck with usbfs not working with 8.0 and 8.01 so I went back to 7.01. I tried todays 8.1.0 and usbfs is still broken. Well, Back to 7.01

How do you revert back to 7.0?
And do you have the version before change view stop working?

 

[darkxex]

how disgusting, enough Lacius, I use the hbg and the atmosphere modified by blawar that comes inside from the beginning, I also use SX OS, since 2018 with cal0 unprotected, nowadays only an idiot would install something like the virus that was made in pokemon lets go, having emunand and your backing from the nand is logical. you should only create your own fork of the original tinfoil and edit it your way, the blawar fork no longer meets your requirements, then make your own, or use another installer, if nobody is interested in leaving you happy, I am also a developer, and not there is nothing more annoying, that they demand something that the creator himself does not care about. Tinfoil was not made for your exclusivity. therefore if you don't like it, just look for an alternative. If it were Blawar, I would have blocked you long ago. because believe me you have already been given the reasons and repeat as a scratched disk.

 

[linuxares]

If linking to warez keeps happening I will start issuing warnings and possibly suspensions and bans.

 

[Lacius]

how disgusting, enough Lacius, I use the hbg and the atmosphere modified by blawar that comes inside from the beginning, I also use SX OS, since 2018 with cal0 unprotected, nowadays only an idiot would install something like the virus that was made in pokemon lets go, having emunand and your backing from the nand is logical. you should only create your own fork of the original tinfoil and edit it your way, the blawar fork no longer meets your requirements, then make your own, or use another installer, if nobody is interested in leaving you happy, I am also a developer, and not there is nothing more annoying, that they demand something that the creator himself does not care about. Tinfoil was not made for your exclusivity. therefore if you don't like it, just look for an alternative. If it were Blawar, I would have blocked you long ago. because believe me you have already been given the reasons and repeat as a scratched disk.

Acknowledging that I can use alternatives or make my own fork does nothing to address the issues at hand.

 

[darkxex]

The problem is that you consider it an issue. The others don't.

 

[TunaKetchup]

Tinfoil 8.1.0 on SX OS

I'm having problem dumping NSP

The NSP is installed and it tells me to press R to dump it. I press R and a screen comes up that says its dumping the game

The screen goes away and I go to my dump location and nothing is there

 

[Lacius]

The problem is that you consider it an issue. The others don't.

I'm not the only one, and that's the problem.

In the future, if you want me to respond, reply to my posts or tag me.

 

[blawar]

Tinfoil 8.1.0 on SX OS

I'm having problem dumping NSP

The NSP is installed and it tells me to press R to dump it. I press R and a screen comes up that says its dumping the game

The screen goes away and I go to my dump location and nothing is there

Will look into it.

 

[TunaKetchup]

Cool.

I'm using NxDumpTool in the meantime

 

[dimitriblaiddyd78]

Used the inbuilt Incognito from Tinfoil and it corrupted my emummc. Had to reset my 400 gb sd card from scratch. Be careful before using apps like Tinfoil that don't work properly