teq said:any word from the developers of the homebrew channel about this?littlestevie said:a hash is a sum of the bytes its a version of a checksum.
a signature is a password that everything (sometimes hashes) are signed with.
MD5 sums can be signed to make the signature but MD5 itself isnt anymore then
a glorified Checksum (checksums can be fooled MD5 not so much as it is a sum of
all data that can be worked out independant of the file as well)
MD5 is not cryptography
a signature is
Uh... you're not too familiar with cryptography, are you?
MD5 itself describes an algorithm for producing hashes, which are aptly named MD5 sums.
MD5 sums are: A) hashes(as they're formed from tables), and B) signatures used in cryptography.
They're used as signature keys because they are nice and random. You can't, however, USE MD5 to sign anything. Just being an MD5 hash doesn't make it any more secure. You need to get off YOUR high horse because all you're doing now is spreading misinformation. Read Wikipedia for god sakes and you'd know why you're not making sense.
The problem is that the saves (As you copy them from your SD card) are signed/encrypted. This means that you'd have to decrypt them, make a change, and encrypt them again, otherwise the saves will appear corrupt. Alternative, you could use the Save Extractor/Installer by Waninkoko which will give you unsigned, unencrypted files.cracker said:I don't have a Wii but I had to read this thread out of curiosity of what is going on.
Has anyone tried hex editing the exploited TP save in case it is as simple as an MD5/CRC check? Just change something that you know won't break the exploit -- text.
But yeah I have yet to hear from anyone who has tried this. bushing et. al. are hard at work.
Edit:
QUOTE
ProdigySim said:teq said:any word from the developers of the homebrew channel about this?littlestevie said:a hash is a sum of the bytes its a version of a checksum.
a signature is a password that everything (sometimes hashes) are signed with.
MD5 sums can be signed to make the signature but MD5 itself isnt anymore then
a glorified Checksum (checksums can be fooled MD5 not so much as it is a sum of
all data that can be worked out independant of the file as well)
MD5 is not cryptography
a signature is
Uh... you're not too familiar with cryptography, are you?
MD5 itself describes an algorithm for producing hashes, which are aptly named MD5 sums.
MD5 sums are: A) hashes(as they're formed from tables), and B) signatures used in cryptography.
They're used as signature keys because they are nice and random. You can't, however, USE MD5 to sign anything. Just being an MD5 hash doesn't make it any more secure. You need to get off YOUR high horse because all you're doing now is spreading misinformation. Read Wikipedia for god sakes and you'd know why you're not making sense.
The problem is that the saves (As you copy them from your SD card) are signed/encrypted. This means that you'd have to decrypt them, make a change, and encrypt them again, otherwise the saves will appear corrupt. Alternative, you could use the Save Extractor/Installer by Waninkoko which will give you unsigned, unencrypted files.cracker said:I don't have a Wii but I had to read this thread out of curiosity of what is going on.
Has anyone tried hex editing the exploited TP save in case it is as simple as an MD5/CRC check? Just change something that you know won't break the exploit -- text.
But yeah I have yet to hear from anyone who has tried this. bushing et. al. are hard at work.
Edit:
QUOTE
Topic on #wiidev: Don't update. Don't ask about the update. More info when we've had time to fully analyze it | Stay tuned to http://hackmii.com/2008/06/june-16-wii-update/
It actually just got updated with that link
teq said:littlestevie said:a hash is a sum of the bytes its a version of a checksum.
a signature is a password that everything (sometimes hashes) are signed with.
MD5 sums can be signed to make the signature but MD5 itself isnt anymore then
a glorified Checksum (checksums can be fooled MD5 not so much as it is a sum of
all data that can be worked out independant of the file as well)
MD5 is not cryptography
a signature is
Uh... you're not too familiar with cryptography, are you?
MD5 itself describes an algorithm for producing hashes, which are aptly named MD5 sums.
MD5 sums are: A) hashes(as they're formed from tables), and B) signatures used in cryptography.
ProdigySim said:They're used as signature keys because they are nice and random. You can't, however, USE MD5 to sign anything. Just being an MD5 hash doesn't make it any more secure. You need to get off YOUR high horse because all you're doing now is spreading misinformation. Read Wikipedia for god sakes and you'd know why you're not making sense.
teq said:Maybe I should get all of my information from Wikipedia... then I'd be as smart as you.
You might want to do a little research before making posts: http://www.w3.org/PICS/DSig/RSA-MD5_1_0.html
Edit: And just to clarify, I was not being vague by not specifying that MD5 is a valid signing method through a container/padding.
If I googled to try to justify all of my answers, I'd be as smart as you.
Even in that, MD5 is only used as a checksum/identifier for the signature key. It is doing no part of the signing. It's using an RSA encryption scheme. MD5 would help Nintendo secure saves in no way. Just stop. Please. This doeesn't belong in this thread.
Edit: Bushing has updated his post. I think most people will find this most useful:
QUOTEThe strncmp signing bug has been fixed in IOS30, which is what the system menu uses. (The new signature-checking code is identical to that in IOS37.) This probably means that it will no longer boot Trucha-signed discs, but I have not yet tried it. Early reports on IRC indicate that the Homebrew Channel still works; this is consistent with my understanding that the system menu does not verify the content of already-installed content.
I don’t know why IOS31 was patched.
QUOTE said:Update 1: IOS30 and IOS31 have been changed — specifically, the kernel. The old timestamps read:
$IOSVersion: FFS: 06/08/07 18:10:10 64M $
$IOSVersion: ES: 07/10/07 18:11:26 64M $
$IOSVersion: IOSP: 06/25/07 14:17:16 64M $
The new timestamps read
$IOSVersion: FFS: 06/08/07 18:10:10 64M $
$IOSVersion: ES: 07/10/07 18:11:26 64M $
$IOSVersion: IOSP: 04/03/08 19:37:33 64M $
It’s interesting that Nintendo bothered to update the IOSP timestamp, because the only change I see in IOSP is that the version reported changed (there’s a variable that stores the value “040308?). They’re trying to be clever; the actual bug fix was in ES, where the encryption code lives.
The strncmp signing bug has been fixed in IOS30, which is what the system menu uses. (The new signature-checking code is identical to that in IOS37.) This probably means that it will no longer boot Trucha-signed discs, but I have not yet tried it. Early reports on IRC indicate that the Homebrew Channel still works; this is consistent with my understanding that the system menu does not verify the content of already-installed content.
I don’t know why IOS31 was patched.
At this moment? No. Is it possible? Sure. "Safely" is a matter of opinion but there are various possibilities that should cause no harm if you're aware of what you're doing.sphere9 said:why are we still having this argument
is there anyway to downgrade the firmware safely?
sphere9 said:why are we still having this argument
is there anyway to downgrade the firmware safely?
Definitely not possible. You're just going to have to wait for another save game hack..TakaM said:question:
Is it possible for the homebrew channel to have an update that allows you to put the HBC on an SD card and install it on another Wii that doesn't have TP save hack/modchip/etc?
.TakaM said:question:
Is it possible for the homebrew channel to have an update that allows you to put the HBC on an SD card and install it on another Wii that doesn't have TP save hack/modchip/etc?
teq said:sphere9 said:why are we still having this argument
is there anyway to downgrade the firmware safely?
Currently, the only way is through overwriting the firmware with an earlier image of your firmware...
You're better off using a drivechip.
QUOTE said:Update 2: Okay, now this is just silly. Two functions have been added to the system menu. Guess what they do:
* ipl::utility::ESMisc:eleteSavedata( (unsigned long long, EGG::Heap *))
* ipl::utility::ESMisc::VerifySavedataZD( (unsigned long long, EGG::Heap *))
We Are Not Impressed.
sphere9 said:i don't even know what a drivechip is...
but i know that i don't want to mod my wii :S
jservs7 said:Update #2 from bushing via hackmii:
QUOTE said:Update 2: Okay, now this is just silly. Two functions have been added to the system menu. Guess what they do:
* ipl::utility::ESMisc:eleteSavedata( (unsigned long long, EGG::Heap *))
* ipl::utility::ESMisc::VerifySavedataZD( (unsigned long long, EGG::Heap *))
We Are Not Impressed.
A good chance this might open up even more possibilities.