CiTRUS - Revision history

Xcution: /* UPCOMING */

2012-05-07T15:37:28Z

UPCOMING

← Older revision		Revision as of 19:37, 7 May 2012
Line 73:		Line 73:

	[-] = It seems flags for developer applications may differ from retail application flags, but it is not a big deal as when retail applications can be decrypted I can replace and change my flags to fit retail needs. The generated CXIs would still require an exploit to run on a retail 3DS, however.		[-] = It seems flags for developer applications may differ from retail application flags, but it is not a big deal as when retail applications can be decrypted I can replace and change my flags to fit retail needs. The generated CXIs would still require an exploit to run on a retail 3DS, however.
	The flags are already laid out and valid developer flags, though.		The flags are already laid out and are valid developer flags, though.

	==UPDATES==		==UPDATES==

Xcution: /* UPCOMING */

2012-05-07T15:34:16Z

UPCOMING

← Older revision		Revision as of 19:34, 7 May 2012
Line 69:		Line 69:


	Signatures, Hashes, ExeFS, Extended Header, Flags^, NCCH header, and encryption are now valid. The only thing left now is the RomFS.		Signatures, Hashes, ExeFS, Extended Header, Flags[-], NCCH header, and encryption are now valid. The only thing left now is the RomFS.


	^ = It seems flags for developer applications may differ from retail application flags, but it is not a big deal as when retail applications can be decrypted I can replace and change my flags to fit retail needs. The generated CXIs would still require an exploit to run on a retail 3DS, however.		[-] = It seems flags for developer applications may differ from retail application flags, but it is not a big deal as when retail applications can be decrypted I can replace and change my flags to fit retail needs. The generated CXIs would still require an exploit to run on a retail 3DS, however.
	The flags are already laid out and valid developer flags, though.		The flags are already laid out and valid developer flags, though.

Xcution at 07:40, 7 May 2012

2012-05-07T05:40:43Z

← Older revision		Revision as of 09:40, 7 May 2012
Line 60:		Line 60:


	Well, it's been a fun 7 months.		Well, it's been a fun 7 months so far.

Xcution at 07:40, 7 May 2012

2012-05-07T05:40:12Z

← Older revision		Revision as of 09:40, 7 May 2012
Line 58:		Line 58:

	5/7/2012		5/7/2012


	Well, it's been a fun 7 months.		Well, it's been a fun 7 months.


	Encrypted, proper CXI:		Encrypted, proper CXI:


	http://www.mediafire.com/?hcm1p6fq4x7q14o		http://www.mediafire.com/?hcm1p6fq4x7q14o

	~~Signatures, Hashes, ExeFS, Extended Header, Flags*, NCCH header, and encryption are now valid. The only thing left now is the RomFS.~~

	* = It seems flags for developer applications may differ from retail application flags, but it is not a big deal as when retail applications can be decrypted I can replace and change my flags to fit retail needs. The generated CXIs would still require an exploit to run on a retail 3DS, however.		Signatures, Hashes, ExeFS, Extended Header, Flags^, NCCH header, and encryption are now valid. The only thing left now is the RomFS.


			^ = It seems flags for developer applications may differ from retail application flags, but it is not a big deal as when retail applications can be decrypted I can replace and change my flags to fit retail needs. The generated CXIs would still require an exploit to run on a retail 3DS, however.
	The flags are already laid out and valid developer flags, though.		The flags are already laid out and valid developer flags, though.

Xcution at 07:38, 7 May 2012

2012-05-07T05:38:59Z

← Older revision		Revision as of 09:38, 7 May 2012
Line 57:		Line 57:
	==UPCOMING==		==UPCOMING==

	4/23/2012		5/7/2012

	~~I am not dead! I apologize for my absence. I wanted to have enough evidence this time to make solid and more presentable data~~.		Well, it's been a fun 7 months.

			Encrypted, proper CXI:

	For the past month and a half I have been learning much more and I've been able to successfully compile CXI (CTR eXecutable Images) with accurate raw data. Last time, my CXI was (in all respects) only structurally valid; the data was not so much as valid as I was thinking. This time, however, I've been able to test the raw data and have progressed the output to be a 1:~~1 valid binary. I am working on proper encryption, but for this demo~~/~~progress update it now has correct structure, flags, signatures, and raw materials to be encrypted into a CXI~~. ~~In other words, I've made a valid raw form of CXI for this progress update~~.		http://www.mediafire.com/?hcm1p6fq4x7q14o

			Signatures, Hashes, ExeFS, Extended Header, Flags*, NCCH header, and encryption are now valid. The only thing left now is the RomFS.

	~~For those curious to see that I'm not making blind claims I'll attach a new download~~ for ~~a fully unencrypted (raw)~~, but ~~valid, homebrew CXI :~~		* = It seems flags for developer applications may differ from retail application flags, but it is not a big deal as when retail applications can be decrypted I can replace and change my flags to fit retail needs. The generated CXIs would still require an exploit to run on a retail 3DS, however.
			The flags are already laid out and valid developer flags, though.

	~~http://www.mediafire.com/?9trvb9trt32dhn7~~


	~~I am still working on encrypting~~ it ~~properly, but now~~ I can ~~show valid coding base progress. I've formatted this CXI~~ to ~~outline the CXI structure while being unencrypted~~. ~~You may notice I did not include a logo binary in the ExeFS. This is because I'm not 100% sure if it is legal to distribute that (my guess is not, though) so I'd rather not post that here just~~ to be on ~~the safe side.~~


	~~For now, with the plain region, I will use 1_2_0_200 as the version. This CXI isn't made by the official SDK (it's made through CiTRUS) so that's more of~~ a ~~placeholder version to ensure compatibility and match the plain region data format we see with~~ retail ~~CXI~~.


	~~Now, with this presentation, I am showing valid structure ''~~and'' valid ~~raw (unencrypted) data. I hope to soon figure out how to properly encrypt CXI to use with 3DS software~~.


	==UPDATES==		==UPDATES==

Xcution at 02:15, 24 April 2012

2012-04-24T00:15:46Z

← Older revision		Revision as of 04:15, 24 April 2012
Line 13:		Line 13:
	= Notes from users =		= Notes from users =
	<del>This application may not generate completely perfect files yet.</del>		<del>This application may not generate completely perfect files yet.</del>
	Banner output has been checked. It is proper data if the program is used properly. The same is for the ICN.		Banner output has been checked. It is proper data if the program is used properly. The same goes for the ICN.

	= General information =		= General information =

Xcution at 02:06, 24 April 2012

2012-04-24T00:06:40Z

← Older revision		Revision as of 04:06, 24 April 2012
Line 59:		Line 59:
	4/23/2012		4/23/2012

	I am not dead! I apologize for my absence. I wanted to have enough ~~evidense~~ this time to make solid and more presentable data.		I am not dead! I apologize for my absence. I wanted to have enough evidence this time to make solid and more presentable data.

Xcution at 02:06, 24 April 2012

2012-04-24T00:06:21Z

← Older revision		Revision as of 04:06, 24 April 2012
Line 59:		Line 59:
	4/23/2012		4/23/2012

	I am not dead! I apologize for my absence. I wanted to have enough ~~data~~ this time to make solid and more presentable data.		I am not dead! I apologize for my absence. I wanted to have enough evidense this time to make solid and more presentable data.

Xcution at 02:05, 24 April 2012

2012-04-24T00:05:40Z

← Older revision		Revision as of 04:05, 24 April 2012
Line 72:		Line 72:

	I am still working on encrypting it properly, but now I can show valid coding base progress. I've formatted this CXI to outline the CXI structure while being unencrypted. You may notice I did not include a logo binary in the ExeFS. This is because I'm not 100% sure if it is legal to distribute that (my guess is not, though) so I'd rather not post that here just to be on the safe side.		I am still working on encrypting it properly, but now I can show valid coding base progress. I've formatted this CXI to outline the CXI structure while being unencrypted. You may notice I did not include a logo binary in the ExeFS. This is because I'm not 100% sure if it is legal to distribute that (my guess is not, though) so I'd rather not post that here just to be on the safe side.


			For now, with the plain region, I will use 1_2_0_200 as the version. This CXI isn't made by the official SDK (it's made through CiTRUS) so that's more of a placeholder version to ensure compatibility and match the plain region data format we see with retail CXI.

Xcution at 02:03, 24 April 2012

2012-04-24T00:03:06Z

← Older revision		Revision as of 04:03, 24 April 2012
Line 9:		Line 9:

	= '''IMPORTANT''' =		= '''IMPORTANT''' =
	~~To generate a correct~~ CXI ~~(when supported)~~, ~~proper keys will need to be supplied~~. ~~For developer-unit~~ keys~~, you need to~~ be ~~an official Nintendo 3DS developer, and have access~~ to ~~the official Nintendo 3DS SDK. For retail-unit keys, don~~'t even ~~bother~~.		The CXI generator has not been released yet, please understand it is under development. I apologize for adding in the possibility of using retail RSA keys; they would be so hard for us to get it wouldn't even be funny having them. However, when homebrew is available to this community the output should be usable, as a homebrew loader would not check the signature.

	~~This tool~~ is ~~practically for developer-units only.~~

	~~NOTE: The tool with~~ the ~~CXI creation has~~ not ~~been released yet;~~

	= Notes from users =		= Notes from users =
	This application may not generate completely perfect files yet.		<del>This application may not generate completely perfect files yet.</del>
			Banner output has been checked. It is proper data if the program is used properly. The same is for the ICN.

	= General information =		= General information =
	== Introduction ==		== Introduction ==
	Over the past weeks I have been working on Project CiTRUS (citrus). Currently this tool boasts the capability to output "proper" Nintendo 3DS (CTR) BaNneR and ICoN files using my XBSF format.		Over the past weeks I have been working on Project CiTRUS (citrus). Currently this tool boasts the capability to output proper Nintendo 3DS (CTR) BaNneR and ICoN files using my XBSF format.


Line 41:		Line 37:
	== USE ==		== USE ==

	Since v0.2, a readme is not really necessary anymore. I've included helpful text inside each tab in the CiTRUS window to do things on-the-fly without needing to switch between notepad and CiTRUS.		Since v0.2, a readme is not really necessary anymore. I've included helpful text inside each tab in the CiTRUS window to do things on-the-fly without needing to switch between notepad (or your favourite text editor) and CiTRUS.

	INPUT:		INPUT:
Line 61:		Line 57:
	==UPCOMING==		==UPCOMING==

	3/1/2012 ~~@ 17:02 PST~~		4/23/2012

	~~I am proud to reveal what this upcoming project is today.~~


	~~It has come to my attention that there is no GBATemp Homebrew Bounty. At the time of writing the news above (~3 weeks ago) I was under the impression it would happen again.~~


	Regardless by saying "at" I was implying "by". I will still release this next version, to be dubbed "CiTRUS Ultimate". Currently I do not have an estimate of when the release will be exactly, but I am hoping for sometime next week since I am getting positive results.


	I know, due to the nature of how I am "unknown" to the scene, I may be considered a liar or fraud. To assure you that I am honest with my work I will enclose a download to a work-in-progress 3DS-mode Homebrew ("Hello World") CXI I developed using CiTRUS Ultimate.


	~~http://www~~.~~mediafire~~.~~com/?lnc2o6372iq98cl~~		I am not dead! I apologize for my absence. I wanted to have enough data this time to make solid and more presentable data.


	~~<del>~~I ~~understand some of the misinformed users of gbatemp may think this is developer-~~only ~~but in fact it can be retail signed, provided~~ the ~~right RSA keys~~. ~~In my demo~~, I ~~used~~ a ~~fake RSA key~~. ~~When using~~ this ~~program~~, ~~I provide you an option~~ to ~~specify your own RSA keys for signing. No illegal keys will~~ be ~~provided~~. ~~The~~ CXI ~~is a format used by both retail and developer 3DS's, not just developer!</del>~~		For the past month and a half I have been learning much more and I've been able to successfully compile CXI (CTR eXecutable Images) with accurate raw data. Last time, my CXI was (in all respects) only structurally valid; the data was not so much as valid as I was thinking. This time, however, I've been able to test the raw data and have progressed the output to be a 1:1 valid binary. I am working on proper encryption, but for this demo/progress update it now has correct structure, flags, signatures, and raw materials to be encrypted into a CXI. In other words, I've made a valid raw form of CXI for this progress update.

	~~This tool is practically for developer-units only.~~

	~~<del>Please note~~ that ~~this CXI has~~ not ~~been tested~~ for ~~loading but it has valid structure,~~ a ~~valid ExeFS~~ (~~contains ARM11 code~~, ~~banner~~, ~~icon, and logo) and has been accepted in transformations to other formats. To the best of my knowledge this is very close to a proper~~ CXI~~, if not a proper one already.</del>~~		For those curious to see that I'm not making blind claims I'll attach a new download for a fully unencrypted (raw), but valid, homebrew CXI :

	After some testing between 3DSGuy and I we have discovered a few problems with the test application. The application appears to be properly signed/signable, and it is able to pass Nintendo's validity checks up to 92% of the installation.

	~~In the initial release of this new feature in CiTRUS I will only include very simple options, but if I see users are enjoying this program I will add more to it~~.		http://www.mediafire.com/?9trvb9trt32dhn7


	~~In case some of you wonder~~, this ~~does~~ not ~~have~~ a ~~RomFS~~. I ~~admit~~ I ~~have~~ not ~~delved into~~ that ~~yet~~.		I am still working on encrypting it properly, but now I can show valid coding base progress. I've formatted this CXI to outline the CXI structure while being unencrypted. You may notice I did not include a logo binary in the ExeFS. This is because I'm not 100% sure if it is legal to distribute that (my guess is not, though) so I'd rather not post that here just to be on the safe side.


	I hope to ~~finish fixing the issues~~ soon~~, but it is very close~~ to ~~being able~~ to ~~pass the checks when importing to the Nintendo~~ 3DS~~, making it through a solid 92% of the installation currently~~.		Now, with this presentation, I am showing valid structure ''and'' valid raw (unencrypted) data. I hope to soon figure out how to properly encrypt CXI to use with 3DS software.

	This doesn't mean the CXI fake - this means it not yet proper. There is a big difference between fake and not proper. I wouldn't release more than the concept output of this tool without testing first. The output CXI was a test bed, which wasn't perfected yet and so I will work on perfecting this CXI before releasing this portion of CiTRUS.

	==UPDATES==		==UPDATES==