Ice password loss causing ice access failure

[grampus]

quite regularly either one or both my devices lose touch with the Ice server when update and download scheduled.
And the Ice logs shows the errors below.
When going to the ice login entry, I find that the password field is cleared and is blank
The fix is just to go down to the login screen and enter my password in again.
The Ice app then works correctly'
This problem has been apparent on a number of software releases, for some months
S/w version current on both my devices is 19.3 20200927
IceTV version is 20191013
There is also another iteration of "the disappearing password"
After doing a SETUP>software manger>create backup, I have also noticed if I go back to the Ice function I have found that the field has been cleared and requires entry again
The password I use is numeric 6 digits long.

[prl]

I also find that occasionally IceTV refuses to accept the current access token (generated when you log in - it's not your password).

I've never been able to work out exactly why it happens, though I think that if you restore an old settings backup, it may load an access token that is no longer valid.

Try asking on the IceTV forum: Daniel Hall@IceTV may have an idea.

[grampus]

Thanks.
ill see if I ca start a dialogue.

[IanL-S]

OK, I had this happen recently - did not notice until I scanned the recordings with FileZilla; then checked timers with Openwebif and saw no timers listed. Something to keep an eye on. Fortunately easily fixed if you are able to access the T2.

Ian

[IanL-S]

This is starting to be an almost daily occurrence with my T2s and V2. Rarely happens with the U4.

I can see how it could happen after doing a USB firmware installation followed by retrieving stored setting, particularly if you fail to create a backup immediately before doing the update. With the spate of online updates recently frequently after the reboot the login details have vanished. I have also seen it happen when a uint freeze and I have had to cut the power supply. I could well be wrong, but I'm sure on at least one occasion it happened after doing a reboot.

The current version of the IceTV plugin is 20201118, so it has been in place for 9 months, which as far as I am concerned rules out the problem being with the plugin. The U4 is on a different IceTV account to the T2s and V2, so there is a remote possibility that that may be a factor.

If only there was a way of instigating the login process remotely my life would be much simpler!

Ian

[MrQuade]

I can see how it could happen after doing a USB firmware installation followed by retrieving stored setting, particularly if you fail to create a backup immediately before doing the update.

Do the IceTV login credentials get written to the config file immediately, or only get flushed to disk on a restart?
Just wondering if the process would be to input the login details, reboot, and THEN perform a settings backup.

prl should be able to confirm or deny that config-write speculation though.

If only there was a way of instigating the login process remotely my life would be much simpler!

OpenWebIf.

[Grumpy_Geoff]

If only there was a way of instigating the login process remotely my life would be much simpler!

You can use a sequence of (Telnet) command-line calls to the OpenWebif web server to emulate remote control presses.
Example, assuming the password prompt is already open, and you want to enter the string "The_pwd123"

Code: Select all

# send key/button "8" 5 times to go through sequence tuv8T -
wget -q -O - 'http://localhost/web/remotecontrol?command=9'
wget -q -O - 'http://localhost/web/remotecontrol?command=9'
wget -q -O - 'http://localhost/web/remotecontrol?command=9'
wget -q -O - 'http://localhost/web/remotecontrol?command=9'
wget -q -O - 'http://localhost/web/remotecontrol?command=9'

# send key/button "4" 2 times to go through sequence gh -
wget -q -O - 'http://localhost/web/remotecontrol?command=5'
wget -q -O - 'http://localhost/web/remotecontrol?command=5'

# send key/button "3" 2 times to go through sequence de -
wget -q -O - 'http://localhost/web/remotecontrol?command=4'
wget -q -O - 'http://localhost/web/remotecontrol?command=4'

# send key/button "1" 8 times to go through sequence ' '1.:;/-_ -
wget -q -O - 'http://localhost/web/remotecontrol?command=2'
wget -q -O - 'http://localhost/web/remotecontrol?command=2'
wget -q -O - 'http://localhost/web/remotecontrol?command=2'
wget -q -O - 'http://localhost/web/remotecontrol?command=2'
wget -q -O - 'http://localhost/web/remotecontrol?command=2'
wget -q -O - 'http://localhost/web/remotecontrol?command=2'
wget -q -O - 'http://localhost/web/remotecontrol?command=2'
wget -q -O - 'http://localhost/web/remotecontrol?command=2'

# send key/button "7" 1 time to get p -
wget -q -O - 'http://localhost/web/remotecontrol?command=8'

# send key/button "9" 1 time to get w -
wget -q -O - 'http://localhost/web/remotecontrol?command=10'

# send key/button "3" 1 time to get d -
wget -q -O - 'http://localhost/web/remotecontrol?command=4'

I don't profess to know the intricacies of the RC models, but the codes are defined in remote.html in a sub-directory of /usr/share/enigma2/rc_models -

Code: Select all

root@beyonwizt2:/usr/share/enigma2/rc_models# ls -al
drwxr-xr-x   11 root     root           736 Nov 15  2020 .
drwxr-xr-x   12 root     root          2520 Aug 24 11:35 ..
drwxr-xr-x    2 root     root           368 Aug 24 11:35 ini0
drwxr-xr-x    2 root     root           368 Aug 24 11:35 ini1
drwxr-xr-x    2 root     root           368 Aug 24 11:35 ini2
drwxr-xr-x    2 root     root           368 Aug 24 11:35 ini3
drwxr-xr-x    2 root     root           368 Aug 24 11:35 ini4
drwxr-xr-x    2 root     root           368 Aug 24 11:35 ini5
drwxr-xr-x    2 root     root           368 Aug 24 11:35 ini6
drwxr-xr-x    2 root     root           368 Aug 24 11:35 ini7
drwxr-xr-x    2 root     root           368 Aug 24 11:35 ini8
root@beyonwizt2:/usr/share/enigma2/rc_models# cd ini0
root@beyonwizt2:/usr/share/enigma2/rc_models/ini0# ls -altr
drwxr-xr-x   11 root     root           736 Nov 15  2020 ..
-rw-r--r--    1 root     root          3825 Aug 23 22:54 remote.html
-rw-r--r--    1 root     root          1512 Aug 23 22:54 rcpositions.xml
-rw-r--r--    1 root     root         12969 Aug 23 22:54 rc.png
drwxr-xr-x    2 root     root           368 Aug 24 11:35 .
root@beyonwizt2:/usr/share/enigma2/rc_models/ini0#

You may have to view the relevant "rc.png" to determine the model.

Example, first few key definitions (I'm using a screenshot as the forum won't let me post the HTML)

RC_button_codes.png (30.23 KiB) Viewed 1755 times

[adoxa]

I haven't tested it, but presumably ?command=84&type=ascii&rcu=keyboard would send a T. A simple one-liner to get the ASCII values (something more fancy could probably do the whole thing): python -c "print [ord(x) for x in 'The_pwd123']".

[Grumpy_Geoff]

I haven't tested it, but presumably ?command=84&type=ascii&rcu=keyboard would send a T. A simple one-liner to get the ASCII values (something more fancy could probably do the whole thing): python -c "print [ord(x) for x in 'The_pwd123']".

Even better!

[prl]

I can see how it could happen after doing a USB firmware installation followed by retrieving stored setting, particularly if you fail to create a backup immediately before doing the update.

Do the IceTV login credentials get written to the config file immediately, or only get flushed to disk on a restart?
Just wondering if the process would be to input the login details, reboot, and THEN perform a settings backup.

prl should be able to confirm or deny that config-write speculation though

Login credentials get saved immediately a response is received from an IceTV login. This will save the login credential to the settings file.

It certainly appears that restoring an old login credential from a saved settings file can result in having an out-of-date login credential that won't be accepted by the IceTV server.

If you use IceTV, you should always do a settings save immediately before doing a USB update and settings restore, not just to make sure that you retain the current login credential, but also to make sure that the timer list that you restore is the one that the IceTV server thinks you have.

But I occasionally get IceTV login failures for reasons that I can't explain.

[adoxa]

Assuming ascii works, here's a script that should enter any string: ./owif-text.sh 'The_pwd123'.

Code: Select all

#!/bin/sh
for key in `python -c "print ' '.join(str(ord(x)) for x in '$1')"`; do
  wget -q -O - "http://localhost/web/remotecontrol?command=$key&type=ascii&rcu=keyboard"
done

[IanL-S]

Thanks everyone for the responses. Much to consider. Will investigate and if I find anything of interest I will report back.

Ian

[Grumpy_Geoff]

Assuming ascii works, here's a script that should enter any string: ./owif-text.sh 'The_pwd123'.

I couldn't get that command variation to work. It issued the command with the response being valid, but the char wasn't shown -

Code: Select all

        <e2resulttext>RC command '84' has been issued</e2resulttext>

[grampus]

Peter wrote

But I occasionally get IceTV login failures for reasons that I can't explain.
Peter

I'll just throw a few extras in here.
I have both a T3 and a U4,
But only the U4 will show this symptom
I have been doing online updates for the last few months.
On each occasion after the save settings, update, restore settings, reboot, I will generally come up with anything up to 3 separate symptoms.

1: lose the USB tuner as seen in Menu>information>devices (shows only the 3 onboard tuners.) 2: >network shows that link is up, but internet is down.
3: Ice TV log shows that I have lost connection with errors .

I have done a number of things through the months to recover, eg reconfigure the network, redo the Ice Tv setup.

The only thing that I am comfortable to say resolves the issue, is to put the U4 into shutdown via the power menu.
Dwell a pause of 10 marching paces or hum happy birthday a number of times, well about 30 seconds anyway.
Power up again, after all that the only thing that is required is to redo the IceTV login as the "token" has been cleared.

Occasionally overnight I find that I lose touch with Ice in a similar fashion. The fix for me is still the same. I.E shutdown, power up, and redo the Ice setup.
I'm not overly bothered by all this, as I seem to be able to use the above fix every time.

One test I tried was while everything was OK, I did a Menu>software Manager>Create backup.
This results in losing my Ice Tv login, and requires setup again.

[adoxa]

Assuming ascii works, here's a script that should enter any string: ./owif-text.sh 'The_pwd123'.

I couldn't get that command variation to work. It issued the command with the response being valid, but the char wasn't shown -

Ah, bugger, that's now how it works. The ASCII character comes from the event itself (when you press the key), which then sends KEY_ASCII (510) to the action map. We'd have to do a bit of mucking about to make it work, probably not worth the effort. An alternative approach could be to type it in once, capture those presses, then inject them back.

[Grumpy_Geoff]

Here's a script that uses the SMS-style button presses to send a string.
Give it an input string to "type it out" on either the SMS-style text entry field or the virtual keyboard.
There's a few characters that are missing from the available SMS-style buttons (e.g. <>\^).
Edit - Ugh, upon re-reading, I should have written that sentence better. What I meant is -
The SMS-style buttons have less characters available compared to the virtual keyboard, missing <>\^{}[].

Execute it with - ./owif_key_send.sh 'The_pwd123'

I can't show the code as Sucuri doesn't like some of it.
The script is attached as a zipped file because the forum software gives an error, so you'll need to unzip it.