I had a quick look at the Arinc eFlyBook and I noticed that by 99.9% it uses the same software as the iLiad. In fact, the only difference is in /etc/er_registry.txt.

---

iRex iLiad:
[USER_APPLICATIONS]
uaIDList=BROWSER;XPDF;APABIMOBI;IMAGEVIEWER;SETUP; PROFILES;EBA

Arinc eFlyBook:
[USER_APPLICATIONS]
uaIDList=BROWSER;XPDF;APABIMOBI;IMAGEVIEWER;SETUP; PROFILES;ARINC;EBA

[ARINC]
category=viewer
arguments=
exec=/media/card/arinc/bin/ereader_mapviewer
xResourceName=arinc
channel=13
extensions=ari;ARI

---

The eFlyBook adds an extra menu item to start the Arinc Mapviewer application. What's interesting: the viewer is started from an external media location... :juggle:

The eFlyBook adds an extra menu item to start the Arinc Mapviewer application. What's interesting: the viewer is started from an external media location... :juggle:

Funny, you are telling that Arinc users are able to start any script they wish by just putting bash instead of the arincviewer in the external media and naming xxx.ari to the script. It is not fair!!! I hope at least they will be overcharged :angry:

well, the eFlyBook is another market.

But you're right, this isn't fair :(

Unless you fake the MAC of your iLiad to one that's internally listed as a FlyBook on iDS; then you would download the FlyBook firmware and the rest should be easy ;-)

I can throw in a list of valid FlyBook MAC addresses... faking it would be another issue though. Perhaps through injection with Ettercap.

I believe we would need MAC adresses and logins.

Changing the MAC adress during a Man-in-the-middle-attack should be possible - but i have no experience with ettercap.

Note that arinc users will receive the updates of Arinc coming from/for the external media. So perhaps even a different update application could be called.

I thought so too first. But it appears only the map software is being supplied by Arinc; eFlyBook users still use iDS to update their reader.

But I find it very encouraging that at least some of us can run virtually *any* app just by this extra little entry in the registry file.

I believe we would need MAC adresses and logins.
I think the way iDS works is by locking the type of your reader to its MAC address. So your existing login should work; only the MAC address needs to be registered as one for the eFlyBook.

Changing the MAC adress during a Man-in-the-middle-attack should be possible - but i have no experience with ettercap.
Yeah, but it's not trivial. When the reader connects with iDS, it transmits its MAC address through the headers as 64-bit extended identifier ("eserver-eui64"). So basically you would have to intercept the headers and replace the EUI64.