Disable SSH/Samba and don't install pirate add-ons, then your device is isolated from the network and there is no need to waste your time trying install anti-malware tools. Even if something generic did compromise a device it would need to be compiled specifically for LE with knowledge of our OS and it's major quirks (like all the normal install-to location being uncompressed from a read-only file on boot into a virtual filesystem).
Posts by chewitt
-
-
It will be useful.
-
Lots of progress on RK generally but I'm not aware of anyone taking an interest in RK3229, only the better spec RK3328, RK3288 and RK3399.
-
There are two ways to achieve this. If you add 'ssh' to kernel boot params it is forced on permanently. You will find the GUI option to disable is then hidden because permanently means permanently. If you patch the default value in the LE settings add-on code you can change the default without compromising the ability to later turn it off, which is a good thing for security.
-
I don't know enough about pi firmware internals to make a proper comment, but I doubt the "lightning bolts" appear until things are booted, so power issues during boot itself may not be on-screen visible. Also, from past experience, iIf it smells like a power problem, it is probably a power problem.
-
Make sure you use the RPi2 image (RPi2/3) not the RPi (RPi0/1) image.
-
Look at the systemd mount example(s) in /storage/.config/system.d/ and create a boot-time mount for the NAS share, then configure TVH server to use the local mount point for that remote share, e.g. /storage/recordings.
-
it is possible to use ipsec vpn (freeswan, strongswan or libreswan) on a libreelec box (wetek)?
Not by default because we don't build the Linux kernel with ipsec config and we don't build connman with ipsec support - because ipsec is almost never used outside of corporate VPN environments so it's not a target for our 'domestic' user audience. If you understand the moving parts of an ipsec implementation it's probably not too hard to create a custom image with appropriate changes; but there are no guides or instructions on the topic so it's down to you to experiment and figure it out.
-
With LibreELEC you have root access by default, so you dont need 'sudo'
What is a solution???
^ well, that's the answer to the question. Just remove the 'sudo' prefix to commands you're trying to use.
-
8.2.3 auto update won't happen because it has not been enabled on the back end .. oversight on a team members part
-
Search in this forum for the imx6 release that vpeter ships with an older kernel and try that.
-
You need to create a build-system package that downloads the driver sources, compiles them, and then installs them to the image. We can probably give more hints if you point out the upstream sources for the driver.
-
Use the autoexec.py function in Kodi to run a Python script. You can control the OS and Kodi from there.
-
It should work, but probably with some caveats due to the much older 3.10 kernel in use. If you read the compatibility matrix for Lakka we should be broadly in the same ballpark as LE/Lakka share a common foundation.
-
Clear the cached keys for PuTTY?
-
Just import the Generic image OVA into vmware Mirror List and then you don't need to carry any hardware apart from your laptop.
-
-
PRi3 bluetooth and wireless are known to be a little under par. You already found the solution.
