369 replies to this topic

[pieterg]

the difference is that the dm8k has a pci wlan adapter, which has different requirements.
usb wlan should work 'out of the box'.

[wizard55]

Hi flashed this image 3 days ago and when I do software update it says nothing to upgrade. If there is a new nightly build should I get updates every day ?

Also why when I downloaded et9000 version does it say online update of your Dreambox ?

[halflife]

is it possible to update it913x dvbt drivers for new kernel 3.4.3? I can download online only for kernel 3.3, that is not working, it disconnect usb port after few minutes.
cant use old it913x cause et9000 just stay on booting....

[jooe]

Can't play any flac music file on Vu+Ultimo with OpenPli 3.0 .

Here is a log

Please fix it if possible

action -> OkCancelActions ok
playing 4097:0:0:0:0:0:0:0:0:0:/media/net/DISKSTATION/Brian Simpson - 2010 - South Beach/01. South Beach.flac
eServiceMP3::construct!
eServiceMP3::playbin2 uri=file:///media/net/DISKSTATION/Brian%20Simpson%20-%202010%20-%20South%20Beach/01.%20South%20Beach.flac
eServiceMP3::starting pipeline
gst_element_query_position failed in getPlayPosition
new service started! trying to download cuts!
download failed, no cuesheet interface
resolved to PLAY
gst_element_query_position failed in getPlayPosition
gst_element_query_position failed in getPlayPosition
gst_element_query_position failed in getPlayPosition
gst_element_query_position failed in getPlayPosition
eServiceMP3::state transition NULL -> READY
Gstreamer error: The autoaudiosink element is not working. (4) from playsink0
[__evUpdatedInfo] title 1 of 0 (South Beach)
[__evUpdatedInfo] title 1 of 0 (South Beach)
Gstreamer error: GStreamer encountered a general stream error. (1) from flacparse0

No any response?
Maybe somebody with Vu+Ultimo can test flac playback and post here? Or I'm completely alone with this problem?
Same flac files was tested on DM8000HD and ET9x00 (both boxes with same OpenPli 3.0) and there was no any problem.
Vu+Ultimo was flashed with last OpenPli 3.0 with same no success with flac playback.

[pieterg]

And does it work with 2.1?
If not, it must be the drivers, complain @ vu+

[jooe]

And does it work with 2.1?
If not, it must be the drivers, complain @ vu+

Yes , It was OK on OE2.1

[guirigui]

ET-Webrowser plugin(HbbTV) won't get installed allthough available in the plugin section...(ET6000)
In the wishlist for ET6000 PLI 3 Image, it would be helpfull that default recording paths can be updated so that to stick with the new USB Hdd directories(media/USB/). With PLi 2.1 it's all auto after USB HDD initialzation then reboot...nothing to do...Also, avoiding the disturbing error message at the end of the initialization process would be nice...

Edited by guirigui, 19 July 2012 - 09:15.

[pieterg]

So problem is: why the passwd command doesn't update the /etc/passwd file but only update /etc/shadow file.

I investigated what is going wrong.
Turns out busybox telnetd (using busybox login) does not use /etc/shadow, because /etc/passwd does not contain an 'x' as password field.
When you put an 'x' in /etc/passwd, busybox correctly falls back to /etc/shadow

Since I was already able to set a password with passwd and Openpli 3.0 this is probably a bug coming for a recent release.

At the start of 3.0, we used the busybox 'passwd' command, which probably set the password in /etc/passwd, instead of /etc/shadow.
And when busybox finds a valid (or zero) password in /etc/passwd, it ends up using that instead of /etc/shadow

Now, when I do a clean flash, /etc/passwd correctly contains an 'x' in /etc/passwd, for the root account.
So login, passwd, telnetd, vsftpd, dropbear all use /etc/shadow.
Can you confirm the problem is no longer there, with a clean flash?
(or, if you manually put an 'x' in /etc/passwd for the root account)

There is a difference between how the new passwd and the old (busybox) passwd work.
setting an empty root password (with passwd), /etc/shadow will contain the hash of the empty password, and you will be required to <enter> the password question during login.
If you (manually) remove the 'empty' password hash from /etc/shadow, the behaviour will be the same as before (with 2.1), and login will skip the password question.

[Rob van der Does]

Can you confirm the problem is no longer there, with a clean flash?

I can.

[littlesat]

Do we need to alter autobackup/install... as we now have to backup shadow instead of passwd?

[pieterg]

you need to backup both

[mirecek1965]

After install last version 20.7.2012 cannot tune any program, Astra 23,5, full scan, nothing found. After reflashing with ver. 2.1, all OK. Also cannot normal ftp on 3.0 images.

[MiLo]

Won't having an "x" in /etc/password but still an empty password cause a security hole in dropbear? (SSH).

Current behaviour is that you cannot login through SSH when the root password is empty. This makes it safe to open the SSH port to the internet, because during the time frame where the box isn't configured (new flash, software upgrade), no one is allowed access from the outside.

If dropbear cannot see that the password is (still) empty, it will happily allow anyone access. There are machines on the net probing randomly for just this kind of hole, and you really don't want them to stumble upon your box unawares...

[pieterg]

no, I think that's fine.
Dropbear has shadow support, and it keeps asking for a password (and the empty password field in /etc/shadow does not match the hash of the empty input)
So with the default state after a clean flash, dropbear won't work.

Only when you deliberately 'change' the root password to an empty password, after which /etc/shadow contains the hash of an empty password, dropbear will accept the (empty) password.

[Dimitrij]

About.py
After the upgrade is always written:
Last Upgrade: unavailable

def getImageVersionString():
try:
  st = os.stat('/usr/lib/ipkg/status')
  tm = time.localtime(st.st_mtime)
  if tm.tm_year >= 2011:
   return time.strftime("%b %e %Y %H:%M:%S", tm)
except:
  pass
return _("unavailable")

In Pli 3.0 is not /usr/lib/ipkg/status

Can make a symlink?

[littlesat]

What should it be then....?

[WanWizard]

in 3.0 it's in /var/lib (not sure if it's ipkg or opkg)...

[Dimitrij]

What should it be then....?

ln -s /var/lib/opkg /usr/lib/ipkg

[mirakels]

or let the code first check for /var and the for the /usr location

[Dimitrij]

or let the code first check for /var and the for the /usr location

I just drew your attention to this little bug.
You decide how to fix more precisely .