Hacking [Release] PlaiCDN: Download and create installable CIAs (or .3ds) with just a title ID and titlekey

[cearp]

You are one of the most condescending narcissists I know. Go back to having your messiah complex. And consider not being a smart ass for once.

who says my name isn't jesus?
be glad you know me. most internet friends don't say that!

 

[dankzegriefer]

who says my name isn't jesus?
be glad you know me. most internet friends don't say that!

Are you TRYING to make people hate you?

 

[Plailect]

that the OP really misunderstands some stuff

Ignore the other guy if he's bothering you, but the only thing I'm misunderstanding is you. I still don't have a clue what your point is, so could you please explain it again?

 

[Xenosaiga]

Barring some oversimplifications, yes that's a decent analogy, but the main thing is that there isn't so much a password to download the games (they're publicly available to anyone) but there is a password to decrypt the game into usable format, which is only given to legit customers.

I know it's a key for decryption. And I over simplified it on purpose!

 

[Plailect]

also, another big problem in this, the decrypted keys which people use with this tool will be incorrect if they are from 'bad' cias.

Which is why it has a "-check" and "-checkbin" function, which downloads the first 274 bytes of the first content file specified in the tmd, then decrypts it with the given titlekey and checks for magic ("NCCH"). If people only use titlekeys checked in this manner, it doesn't matter what's in the generated CIA.

and this program creates those 'bad' cias, so this program is just cycling round this incorrectness, the more people who use this, the more people who will be sharing incorrect title keys.
does anyone see what i mean?

Who cares if people share incorrect titlekeys for some reason? They're easily verifiable with the method I described and implemented, and I'm not about to rewrite makerom just to have it use valid titlekeys when it doesn't matter.

 

[Garro]

Ignore the other guy if he's bothering you, but the only thing I'm misunderstanding is you. I still don't have a clue what your point is, so could you please explain it again?

I'll take cearp is just having a bad day, AFAIK he's usually not that aggressive.

To be fair, I know little to none of how CIA building works, but I know at least the consequences of "bad cias", like, when you try to download a game or an update of a game you installed a CIA of it before, the download freezes at 99% because the decryption key (which I'm not sure it's the same than the titlekey) stored in the console ticket is wrong, this happens when you install a "bad cia" since it associates a wrong key to the ticket when installed. This doesn't affect the game at all but it creates problem with the eShop. I don't know the technicality behind it, but cearp is saying your CIAs have this problem.

To be fair I thought this problem happened only when converting 3ds to cia, but cearp is the author of FunkyCIA which creates correct CIAs, so he probably knows what he's talking about (despite his bad mood).

 

[Plailect]

you still didn't explain why you were sharing 'legit' keys so, i'm not really surprised i guess

What is a "legit key"?

Are you referring to a valid decrypted titlekey used to decrypt NUS contents? Because the reason there is obvious...

they work, but they will interfere with eshop content. but it is a problem for everyone, but it is a problem

You don't need a valid titlekey in the ticket to download updates.

you didn't do your homework?
you think you are correct here?

Yes...
Take a look at this and tell me where exactly it has input for either a ticket or key of any kind.

--------------------- MERGED ---------------------------

I'll take cearp is just having a bad day, AFAIK he's usually not that aggressive.

To be fair, I know little to none of how CIA building works, but I know at least the consequences of "bad cias", like, when you try to download a game or an update of a game you installed a CIA of it before, the download freezes at 99% because the decryption key (which I'm not sure it's the same than the titlekey) stored in the console ticket is wrong, this happens when you install a "bad cia" since it associates a wrong key to the ticket when installed. This doesn't affect the game at all but it creates problem with the eShop. I don't know the technicality behind it, but cearp is saying your CIAs have this problem.

To be fair I thought this problem happened only when converting 3ds to cia, but cearp is the author of FunkyCIA which creates correct CIAs, so he probably knows what he's talking about (despite his bad mood).

You don't need a valid titlekey in the ticket to download updates.

 

[dankzegriefer]

What is a "legit key"?

Are you referring to a valid decrypted titlekey used to decrypt NUS contents? Because the reason there is obvious...



You don't need a valid titlekey in the ticket to download updates.



Yes...
Take a look at this and tell me where exactly it has input for either a ticket or key of any kind.

--------------------- MERGED ---------------------------



You don't need a valid titlekey in the ticket to download updates.

If the titlekey was invalid how would the game run?

 

[Garro]

You don't need a valid titlekey in the ticket to download updates.

Like I said, I don't know the technicality behind it, I just know "bad cia" makes eShop unable to decrypt download and crashes on 99%.

 

[dankzegriefer]

Like I said, I don't know the technicality behind it, I just know "bad cia" makes eShop unable to decrypt download and crashes on 99%.

"Hmmm, someone told me I'm wrong, maybe if I say my incorrect statement again it will become true!"

 

[Garro]

"Hmmm, someone told me I'm wrong, maybe if I say my incorrect statement again it will become true!"

The problem of an eShop download freezing at 99% is a fact, you can always just turn a blind eye and thing everything is all right, it has happened to me after the first Smash update was released (a year ago or so?), I had to lurk a lot to find a solution about this since its a very hard to find topic. And I hope you change your attitude towards those who disagree with you, otherwise 4chan welcomes your kind of replies.

 

[Plailect]

it just comes off as a noob who had an idea, thought it was a good idea, took someone else's script and changed it a bit

no one got mad at me for making FunkyCIA, even though i based it off of the same original script this guy did.

?????????????????????????????????????????????????????????????????????????????????????????????????????

 

[hab]

I have the seeddb how to load and use it?

 

[cearp]

?????????????????????????????????????????????????????????????????????????????????????????????????????

look what i changed, do a diff.
and i think i based my code off of dumptickets, not the cdnto3ds.
there must be a reason why relys was upset at you but not me.

 

[dankzegriefer]

look what i changed, do a diff.
and i think i based my code off of dumptickets, not the cdnto3ds.
there must be a reason why relys was upset at you but not me.

Hey @Relys

 

[DocKlokMan]

There seems to be a lot of confusion. I'm not sure why, but I'll try and put everything I'm seeing down as how I'm interpreting it in the hopes that whoever is misunderstanding whom may see where the misunderstanding is coming from.

This is what I understand so far, PlayCDN will check your decTitleKey.bin file and report either ALL TitleKeys, including invalid ones or you can have it check CDN and only report valid TitleKeys.

You can then use this information for TitleID and TitleKey to download and decrypt eShop titles in order to pass them to MakeROM. MakeROM however does not build the CIA with the included TitleKey, it makes an invalid TitleKey instead, meaning the resulting CIA, when installed will create an invalid TitleKey in that 3DS's ticket.db.

@cearp finds issue with this since they believe it would be better to generate a CIA with a valid TitleKey instead, thus allowing valid TitleKeys to be entered into people's ticket.db. @Plailect doesn't see this as an issue since with CFW it does not matter if the TitleKey is invalid and the issue is with MakeROM. @cearp seems to be implying that their tool FunkyCIA can make these "valid CIA's" using the data in your ticket.db and so should be able to adapt to have a manual TitleKey provided as well.

When titles are legitimately purchased through the eShop they will fail at the 99% downloaded mark if an invalid TitleKey exists in your ticket.db, preventing you from legitimately getting the game. Invalid TitleKeys should not affect updates (and to my experience, does not).

To be honest, I would prefer if the CIA's did have valid TitleKeys just so that if you decide to get the official game from the eShop you can. Also, if the CIA's themselves are shared rather than the TitleKey, anyone who installs it will be able to obtain the TitleKey by running this script.

This is what I've understood, if I've gotten any of it wrong, perhaps that is why there is such a huge misunderstanding going on.

 

[Plailect]

If makerom supported inputting a titlekey during CIA creation then I'd have added it, but it doesn't :/

 

[Plailect]

changed it a bit

changed it a bit

changed it a bit

Mine was completely rewritten to now be GPL compliant, so I owned ALL of the code until a couple people made pull requests today, and yet that's not as good as your's for... what reason?

 

[dankzegriefer]

Mine was completely rewritten to now be GPL compliant, so I owned ALL of the code until a couple people made pull requests today, and yet that's not as good as your's for... what reason?

Well obviously self awareness is in low stock today

 

[shinyquagsire23]

Mine was completely rewritten to now be GPL compliant, so I owned ALL of the code until a couple people made pull requests today, and yet that's not as good as your's for... what reason?

You mean when you switched all the camelcase to snake case so the diff would actually be significant this time?