Na alle verhalen die de ronde gaan over de Portal blocking van infomir ben ik zelf wat research gaan doen en op het onderstaande artikel uitgekomen:
I've spent the last few days digging around with Wireshark + custom firmware to see how this was working, and it turns out it's quite simple and can be removed from all current firmware on all models that I've tested (250/254/256/322/324)
We could, as people currently are, keep changing portal URLs - but this is not sustainable and as the box is phoning home on every boot, is more than likely just making it easier for Infomir to just re-block on the next wave of updates to the blacklist.
At boot the box performs the following:
This means we have two tasks to perform:
Both of theses tasks CAN be done by hand, but the easiest way (especially for larger providers) is to build a custom firmware that users can just load from a USB that will both patch the problem and prevent Infomir from pushing any more automatic updates to that box.
For those comfortable making the change and would rather do it themselves the details are below. If people need them, I can build patched firmware for the boxes that people need, but won't have the time to build and upload them before probably Sunday evening. (Pending recommendations of a good anonymous file host)
To edit the hosts file (/etc/hosts) add the following line
(replace mag324 with the correct model for you):
To patch stbapp, open /usr/local/share/app/stbapp in a HEX editor, search for
and make ANY change to the domain name (without changing the length AT ALL)
Finally to ensure that the dls.backup will be deleted after flashing your custom firmware than add the following line to /mnt/Userfs/data/dls.backup before the line that launches stbapp:
If all the above has been done correctly, then all previously blocked portals will now be accessible again, and no future blocks will have any effect either.
Custom firmware: voor de mag: 250,254,256,322,324
Link Zippy:
Link Mega:
OneDrive:
Custom firmware is ready to download and use
Will preserve portal settings, but disables the block and prevents any remote updates from Infomir's servers.
(Thanks to both
Thank you very much for the Gold, I appreciate it
Source:
Links geupdate.
One drive link toegevoegd.
Voor de admins: Mocht dit niet mogen verwijder vooral me post, het enige wat er eigenlijk instaat is een custom firmware en is volgens mij niet verboden.
I've spent the last few days digging around with Wireshark + custom firmware to see how this was working, and it turns out it's quite simple and can be removed from all current firmware on all models that I've tested (250/254/256/322/324)
We could, as people currently are, keep changing portal URLs - but this is not sustainable and as the box is phoning home on every boot, is more than likely just making it easier for Infomir to just re-block on the next wave of updates to the blacklist.
At boot the box performs the following:
- DNS lookup for NTP server
- Contact all NTP Servers found
- Executes the script /etc/rc.d/rcS.d/S98stbapp (which then launches stbapp - the browser that displays your portal)
- DNS lookup for mag???.dcbs.infomir.com
- Encrypted communication with mag???.dcbs.infomir.com
- Saves result of this communication as
/mnt/Userfs/data/dls.backup - Displays portal selection page
- If portal is blocked, it then loads and displays the error message (which is stored in the javascript for the Inner Portal - so we can edit this if we choose)
- Otherwise load portal as normal
This means we have two tasks to perform:
- Patch stbapp OR the hosts file to block the blacklist server
- Erase dls.backup to prevent cached lookups
Both of theses tasks CAN be done by hand, but the easiest way (especially for larger providers) is to build a custom firmware that users can just load from a USB that will both patch the problem and prevent Infomir from pushing any more automatic updates to that box.
For those comfortable making the change and would rather do it themselves the details are below. If people need them, I can build patched firmware for the boxes that people need, but won't have the time to build and upload them before probably Sunday evening. (Pending recommendations of a good anonymous file host)
To edit the hosts file (/etc/hosts) add the following line
(replace mag324 with the correct model for you):
12.0.0.1 mag324.dcbs.infomir.com
To patch stbapp, open /usr/local/share/app/stbapp in a HEX editor, search for
dcbs.infomir.com
and make ANY change to the domain name (without changing the length AT ALL)
Finally to ensure that the dls.backup will be deleted after flashing your custom firmware than add the following line to /mnt/Userfs/data/dls.backup before the line that launches stbapp:
rm /mnt/Userfs/data/dls.backup
If all the above has been done correctly, then all previously blocked portals will now be accessible again, and no future blocks will have any effect either.
Custom firmware: voor de mag: 250,254,256,322,324
Link Zippy:
Je moet ingelogd zijn om deze link te bekijken.
Link Mega:
Je moet ingelogd zijn om deze link te bekijken.
OneDrive:
Je moet ingelogd zijn om deze link te bekijken.
Custom firmware is ready to download and use
Will preserve portal settings, but disables the block and prevents any remote updates from Infomir's servers.
(Thanks to both
Je moet ingelogd zijn om deze link te bekijken.
and
Je moet ingelogd zijn om deze link te bekijken.
for helping me find blocked portals to test my patches with)Thank you very much for the Gold, I appreciate it
Source:
You must be registered for see medias
Links geupdate.
One drive link toegevoegd.
Voor de admins: Mocht dit niet mogen verwijder vooral me post, het enige wat er eigenlijk instaat is een custom firmware en is volgens mij niet verboden.
Laatst bewerkt: