7.x backdoor hash

[azitnay]

Has anyone ever posted the backdoor hash for 7.x? I haven't seen it anywhere, and it's definitely changed since 4.x.

I'd love to be able to find it myself, but I'm not sure I'm quite that advanced.

Drew

[compwiz312]

1. Why would you need it? Unless you have a supercomputer, I don't think you can crack it.

2. This is not the proper forum for this kind of question.

[mrblack51]

1. Why would you need it? Unless you have a supercomputer, I don't think you can crack it

the cheasy way to deal with backdoors is to modify the hash by doing a byte search on the hard disk image, then replacing it with a known hash.

[azitnay]

1. Why would you need it? Unless you have a supercomputer, I don't think you can crack it.

I realize that there's no way I can crack it, but as another poster stated, I'd like to be able to hexedit the MFS partitions to change it to a known hash and thus be able to enable backdoors. I did it on 4.x, but I haven't seen the 7.x hash posted anywhere.

2. This is not the proper forum for this kind of question.

Sorry for the inconvenience... As you can tell from my post count, I'm new to this particular forum. Would "Series 2 Support" have been more of a proper forum? At first glance, I thought it was for issues with "supported" TiVo features, but now that I look at its threads, that's obviously not the case.

As an aside, I figured I'd do my best to try to find it myself. The only thing I could think to try was to search partitions 10 and 12 of a 7.x MFS Tools backup I have for [0-9A-Z]{40}\0. Unfortunately, I ended up with 1,148 different strings :). Most occurred twice, so I can't even really glean anything from the number of occurrences. So, trial and error is out of the question, with that many strings (BTW, the old 4.x hash was one of the 1,148, but I already tried replacing that, and it didn't work, so I'm assuming it's just left over from 4.x and that the hash has indeed changed).

As I said in my original post, I'd love to be able to help myself here, but I'm out of things to try at the moment.

Drew

[azitnay]

the cheasy way to deal with backdoors is to modify the hash by doing a byte search on the hard disk image, then replacing it with a known hash.

Call it cheesy if you must, but assuming the hash is known, it's a lot faster to take 10 minutes and replace it via hexedit than it would be to monte your TiVo, if this is all you truly want.

Now, since I don't really know of a way to find the hash easily without shell access, I guess I can't bash the monte method too much :). It's just a bit much for me. Perhaps if I had a "workshop-only" TiVo...

Drew

[mrblack51]

Call it cheesy if you must, but assuming the hash is known, it's a lot faster to take 10 minutes and replace it via hexedit than it would be to monte your TiVo, if this is all you truly want.

Now, since I don't really know of a way to find the hash easily without shell access, I guess I can't bash the monte method too much :). It's just a bit much for me. Perhaps if I had a "workshop-only" TiVo...

Drew

that method is truely cheesy. lets face it, this board is for tivo hacking. we want bash, then add whatever utils you like to do whatever you want. TCF is more of a tivo enthusiast site - they dont want to hack their boxes very much, and virtually no dev goes on there (there is some, but not a whole lot anymore). the known and standard method for enabling backdoors is to get bash and then apply a tivoapp patch. hash searching is for people who dont want to hack their box. course, backdoors really dont give you all that much extra anyway. eh, to each their own.

in some essense, if you dont want to get bash on your box, then when it comes to backdoors the answer is "enjoy your stock tivo"