Log in

View Full Version : editing channel list on PC ?



drumitar
04-30-2017, 03:18 AM
just wanted to know if there is anyway once i save the channel list to the usb, is there a way to edit the channels on pc ? want to delete big blocks of channels that scan in that dont work.

thanks,

nobodyspecial
04-30-2017, 12:29 PM
not possible

jvvh5897
04-30-2017, 07:21 PM
I looked for a channel editor for the Dreamlink t4 and found none. I did find one post of a dumped channel list and looked at it to see what was going on in it and it looks to me that it is encrypted. My guess is that the previous post is right--you can't do anything. Now, we could try to get info to get clear info out of the box if someone wants to work on that then I could help as best as I could, but encryptions can be hard to figure out without access to the code. Might have to dump the flash in creative ways, or get into code to other ways.

jvvh5897
05-01-2017, 07:28 PM
Or you could contact the guys that sell Dreamlink and insist that there needs to be a channel editor for the various models.

If you want to try to figure out something about the lists on your own, then you might want to dump a default/empty channel list to usb and see what size it is compared to a regular list (maybe post both). If you look at the end of a file, you will find what is likely an empty list starting with the ascii sequence "NDF" and going to "END"--that looks like the old ndf information that coolsat coders used and there were ndf editors as part of the coolsat 4000 and 5000/6000 source code releases. I bet if you were to get into the channel lists in the clear for T4 or T5 that you would find something that could be edited with those old ndf editor programs (or you could use python code like I have been for DSS channel lists for coolsat 4000-like boxes).

Odds are that the encryption method for the channel lists is the same seen in the Make2Dream programs--they produce files that you can see similar byte pattern repletion in--the M2D programs use 8 byte key and operate on 8 byte blocks--the T4 M2D and T5 M2D programs only differ in the 8 byte key used (only the order of the bytes used differ in the keys but as far as I can tell they use different bytes for the channel list key--assuming they use the same encryption method and I bet they do).

nobodyspecial
05-01-2017, 09:42 PM
Or you could contact the guys that sell Dreamlink and insist that there needs to be a channel editor for the various models.

If you want to try to figure out something about the lists on your own, then you might want to dump a default/empty channel list to usb and see what size it is compared to a regular list (maybe post both). If you look at the end of a file, you will find what is likely an empty list starting with the ascii sequence "NDF" and going to "END"--that looks like the old ndf information that coolsat coders used and there were ndf editors as part of the coolsat 4000 and 5000/6000 source code releases. I bet if you were to get into the channel lists in the clear for T4 or T5 that you would find something that could be edited with those old ndf editor programs (or you could use python code like I have been for DSS channel lists for coolsat 4000-like boxes).

Odds are that the encryption method for the channel lists is the same seen in the Make2Dream programs--they produce files that you can see similar byte pattern repletion in--the M2D programs use 8 byte key and operate on 8 byte blocks--the T4 M2D and T5 M2D programs only differ in the 8 byte key used (only the order of the bytes used differ in the keys but as far as I can tell they use different bytes for the channel list key--assuming they use the same encryption method and I bet they do).

that wont happen as they are no longer around

jvvh5897
05-02-2017, 05:23 PM
The Kbox models had the same guys behind it as the coolsat and Dreamlink AFAIK--at least looking at the files and their structures--perhaps there was something used in Kbox that could be of use for you guys. No one else is going to help you, you have to do it yourselves.

jvvh5897
05-03-2017, 04:28 PM
Sure enough I found the same encryption tables (S_boxes?) in the KBox 170 factory file. So, now have two examples of encryption and one decrypt routine between that 170 file and the Make2Dream program.
From one M2D program the tables starts are:
0080D0 2A E1 0B 13 3E 6E 32 48-D3 31 08 8C 8F 95 BD D0
...
0081D0 BF 11 6D FA 26 7F F3 C8-9E DD 3F 16 97 BD 08 80

I suspect that the encryption is symmetric and uses the same key for decrypt as encrypt. The sequence of steps for decrypt reverse the order used in encrypt.

Now, the Kbox uses an AR/lh5 compression scheme and I suspect your Dreamlink does too, but there are ways to use the source code or 7-Zip to unpack. All supposing that you can find the 8 byte key to use.

drumitar
05-03-2017, 10:02 PM
thanks for the help, its honestly not a huge deal and probably not worth all the trouble. I was just hoping to delete a chunk of channels that scan in that i dont get. Its no biggie, just throught if there a utility or something easy i would use it. thanks for the info !

jvvh5897
05-04-2017, 06:18 PM
I think it is a big deal. A channel editor is a basic tool for FTA boxes. That the coders for the brand encrypted the list is a bad, bad thing. I've seen the guys using the same tricks for years now and I've had enough of it! I don't know why anyone buys their boxes. (I can see why they put them out though--money)

BTW, I found a kbox_editor file that I'll look at. But I've changed my mind about the T4 example list I found being compressed. I can find an 8 byte sequence that is repeated 2300 times at random spots (well, not random but not all in one group like you see later in the file)--you don't get that with compression.

jvvh5897
05-05-2017, 06:29 PM
Not much luck on the Kbox editor. I did play with the disassembly of the Make2Dream_T4 program some more. Weird way to encrypt! Looks to me like they do 15 rounds of encryption on 4 bytes of the 8 byte block and the same on the other 4 but byte swap the order of the 4 to 1, 3, 0, 2 rather than 0, 1, 2, 3 and for one set they use one 256 byte table and for the other set of 4 use the other 256 byte table (not entirely sure of that though).