One question, though: Is it possible to encrypt the password with MD5 or something? For security reasons..
The client needs the password as-is, hashing it isn't possible.
Btw. MD5 is far from being secure, so better forget about it.
One question, though: Is it possible to encrypt the password with MD5 or something? For security reasons..
The client needs the password as-is, hashing it isn't possible.
Btw. MD5 is far from being secure, so better forget about it.
The RPI is designed as an always-on device, as such it has no power management hardware. With additional hardware you can add an reset/power switch, but AFAIK there is nothing with CEC support, only IR based.
but not so easy to use, and Kodi can integrate that feature
So why are you asking here instead of the the Kodi developers?
Someone setup the Pipplware repository and created the Kodi/LibreElec V16 package.
You need to understand that LibreELEC is an operating system designed to run Kodi, but the LE developers are not the Kodi developers. Any Kodi packages you install on a different operating system have nothing to do with LibreELEC.
I think you don't understand, LibreELEC is a complete operating system that's developed to run Kodi. But the LE developers are not the Kodi developers, so it's highly unlikely that they will start to provide Kodi packages for other operating systems, like the one running on your TV.
If you are looking for Kodi packages you'll have to talk to the Kodi developers at Kodi Community Forum.
Could it be anything else??
Try the RPi1 image, just to be sure.
Ive tried looking everywhere!!
Get glasses: LibreELEC
Options for the Realtek 8192cu driver won't change a thing on a Broadcom based Wifi chipset.
@OP
Just posting that you get an error without telling what exactly the error message says is quite useless, better yet provide full logs and not only snippets.
Backup - Official Kodi Wiki search in the Kodi forums, and your likely to find more information.
It's hard to say how that correlates to the number of SSH exposed systems there are without actually self-scanning for them (and I'm not Brian Krebs) but from the number of SMB systems I believe the number is not statistically significant enough to represent a worthwhile/economic opportunity for the actors who perpetrate these attacks; they are normally looking for "low hanging fruit" that provide much larger device counts.
Well, I'm owning/running a dedicated server in a data center and among other things I log failed ssh access credentials. The root/openelec combination shows up quite regularly. The root/libreelec combination has appeared a few times in the last 2 months, so there is at least one tool out there that has it in it's database as a combination to try.
1) Is there a potential for a device running vanilla LibreElec to become co-opted into a botnet via default passwords?
2) How much vulnerability does the system have with a malicious addon installed, how much control is an addon allowed?
3) What are best practices for the platform?
1) If it's not behind a router/firewall, or ssh/http ports are forwarded to it: very high.
2) and 3) see Warning - Be aware what additional add-ons you install | Kodi | Open Source Home Theater Software
It really doesn't matter, as everything running on LE is already running as the root user. So a privilege-escalation vulnerability doesn't change a thing here.