Beiträge von madman1602

  • LibreELEC (Leia) 9.0.0 RELEASE

    LibreELEC 9.0 (Leia) has finally arrived after a long gestation period. Based upon Kodi v18.0, the Final 9.0 release contains many changes and refinements to user experience and a complete overhaul of the underlying OS core to improve stability and extend hardware support. Kodi v18 also brings new features like Kodi Retroplayer and DRM support that (equipped with an appropriate add-on) allows Kodi to unofficially stream content from services like Netflix and Amazon.
    Settings Add-on:

    • Changeable SSH passwords!
    • Default firewall (iptables) with simple configurations for Home/Public networks
    • Updates are moved to their own menu, other options are cleaned up a little
    • Safe Mode boot when Kodi experiences startup problems


    Changeable SSH passwords and a default firewall configuration have been added to combat the increasing number of HTPC installs that can be found on the public internet. The increase is partly due to simple maths; our userbase has grown so the number of users inappropriately exposing their HTPC to the internet has also grown. The static password for libreelec is present on most/all password dictionary lists so it’s important we start encouraging users to change it (the first-run wizard will prompt when SSH is enabled).

    More people are using VPN services for privacy without realising this exposes SSH/SMB/Web services. To combat this problem we have added simple firewall configurations for Home/Public networks; the Home configuration blocks inbound connections from non-private networks, e.g. traffic from the Internet to the public IP address used with the VPN connection.

    As the Kodi piracy scene continues to decline we have seen an increase in users with outdated add-ons that cause problems during upgrades so “Safe Mode” counts Kodi startup crashes. After five startup failures it intervenes with a default (clean) configuration and prominent warning so users know there is a problem – but still have a working GUI to troubleshoot from.
    Retroplayer:
    Kodi v18 brings initial support for retro gaming and the ability to play hundreds of retro games directly from within Kodi. We provide a large number of emulator cores from our add-on repo, but no games (bring your own) although there are a couple of open source test game add-ons (2048 etc.) in our repo. In this first iteration of Kodi retro gaming support the user interface can be a little confusing and we still need to write-up some HOWTO guides for the wiki. Kodi developers are working on a game database (for Kodi v19) which will make the process of managing and using game ROMs easier in the future.


    DVB Drivers:
    We now offer a larger range of DVB drivers (depending on your platform) to choose from. The “DVB drivers from the latest kernel” option also includes the majority of Hauppage drivers which have been recently upstreamed into the kernel, which is great to see!

    Rockchip:
    Despite the 8.95.1 release number our Rockchip releases remain in an Alpha state with limited support. The Kodi version is updated but there are no significant video/audio improvements to the Rockchip 4.4 kernel codebase – and none planned. Our work on Rockchip support has refocussed onto the Linux 4.20 kernel to use the modern kernel frameworks needed for the next-generation Kodi video pipeline. This work is progressing nicely, but it means the 4.4 codebase “is what it is” until a future kernel bump.

    New Devices:

    Amlogic

    • Khadas VIM(1) – requires a clean install if using current community images
    • Libre Computer Le Potato

    Rockchip

    • 96rocks ROCK960
    • ASUS Tinker Board
    • Firefly ROC-RK3328-CC
    • Khadas Edge
    • PINE64 ROCK64
    • PINE64 RockPro64
    • Popcorn Hour RockBox
    • Popcorn Hour Transformer
    • Radxa ROCK Pi 4
    • Rockchip Sapphire Board
    • Mqmaker MiQi

    If you experience problems, please open an thread at our forum. You can also open an ticket at our issue tracker.
    Downloads
    Click here to go to the download page.

  • LibreELEC (Krypton) v8.2.1 MR

    LibreELEC 8.2.1 is a maintenance release that includes Kodi 17.6. It also resolves a minor time-zone issue after recent daylight saving changes, a resume from suspend issue with the Apple IR driver, and it provides two new SMB client configuration options in Kodi settings. You can now set a minimum SMB protocol version to prevent prevent SMB1 from ever being used, and a ‘legacy security’ option forces weak authentication to resolve issues seen with the USB sharing functions on some older router/NAS devices. If updating to LibreELEC 8.2 for the first time PLEASE READ THE RELEASE NOTES below here before posting issues in the forums as there are disruptive changes to Lirc, Samba, and Tvheadend.
    As Kodi 17.6 has been declared the final Krypton release (no further updates) we also expect LibreELEC 8.2.1 to be the final 8.2 update. The team are now focussed on LibreELEC (Leia) 9.0 development.
    Changes since LibreELEC 8.2.0 include:

    • Fix issues with the Apple IR driver not working after suspend
    • Fix ‘file exists’ errors with SMB connections to Win10 shares
    • Update Samba to 4.6.10
    • Update tz-data to 2017c
    • Update Kodi to 17.6
    • Add SMB client options for minimum SMB protocol
    • Add SMB legacy security option with NTLMv1 and disabled SPNEGO

    See detailed changes on GitHub.
    ** SAMBA / SMB CHANGES **
    LibreELEC 8.2.x includes changes that allow the Kodi SMB client and our embedded Samba server to support SMB2/3 connections; deprecating SMB1 to improve security and performance. This is necessary to cope with changes Microsoft introduced in the Windows 10 ‘Fall Creators Update’ to resolve SMB1 security issues. Please see Microsoft notes here and here and here for an explanation.
    LibreELEC changes are summarised below:

    • The Kodi SMB client now defaults to SMB3 connections but can fail to negotiate SMB3 with old Samba (NAS) versions. New options in Kodi Settings > Services > SMB client > allow max SMB2 or SMB1 to be forced for compatibility with legacy SMB servers, or min SMB2 to be forced to ensure SMB1 is never used.
    • Some router and NAS devices have proprietary SMB1 implementations that do not support NTLMv2 and forcing SMB1 still results in a refused connection. The legacy security option (visible only when SMB1 is the max protocol) can be set for compatibility. This forces weak auth. It should not be set unless needed.
    • The embedded Samba server defaults to SMB2/SMB3 connections. The LibreELEC Settings add-on allows the minimum SMB version to be changed, e.g. to enable SMB1 for compatibility. It also supports GUI configuration of WORKGROUP name and requiring username/password authentication.
    • In other Linux distros Samba clients default to SMB1 for all Samba versions up to v4.7 when the Samba default changes to SMB2. If the installed Samba version of your Linux distro is between v4.1 and v4.6 you can force SMB2/3 connections by adding client min protocol = SMB2 and client max protocol = SMB3 to your smb.conf. Samba versions older than v4.1 do not support SMB2/3 and require the LibreELEC Samba server to be configured for legacy SMB1 support.
    • Samba detects v3 /storage/.config/samba.conf configurations and ignores them to avoid the Samba service failing on startup. If this happens Samba starts with a default v4 configuration. Custom Samba configurations must be manually updated to use the new Samba 4.x template (samba.conf.sample).
    • Kodi “Windows network browsing” needs the Kodi SMB client to support SMB1 and we now default to SMB2/3 connections so SMB browsing no longer works. Windows SMB share sources must now be added using the full server/share path. SMB sources from Samba/NAS devices that support Avahi or ZeroConf can normally be browsed via the “ZeroConf network browsing” alternative.
    • Connection failures to anonymous and guest shares on a Windows server are normally solved by creating a local machine user account and password credential on the server for Kodi to use, then setting read or read-write permissions for that credential to the shares Kodi will access.
    • Connection failures from a Windows client to the embedded Samba server are probably the result of Win10 changes that remove support for guest/anonymous access. Enabling password authentication in the LibreELEC settings add-on and setting username/password credentials should allow access.
    • Local filesystem mounts of a remote SMB filesystem via systemd or autostart.sh now default to SMB2 so connections to SMB1 shares fail unless vers=1.0 is added into the mount command to force SMB1. If using local mounts to USB shares on old router/NAS devices sec=ntlm may also be required.

    ** LIRC CHANGES **
    In LibreELEC 8.0 the Lirc service is enabled when an IR receiver is detected in the system, but it is not started unless used with the lirc_rpi or lirc_xbox drivers or a personal lircd.conf. In LibreELEC 8.2 the Lirc service is enabled and supports all drivers which can result in the service starting and interfering with normal IR operations. If you experience “double button presses” after updating the Lirc service can be disabled in the ‘Services’ tab of the LibreELEC settings add-on. The Lirc service is disabled by default in new installations and must be manually enabled. Thanks to @HiasoffT changes the Lirc service is now configurable using a combination of /storage/.config/lirc_options.conf and lircd.conf – the same approach used in desktop Linux distributions and most howto instructions users find via Google searches.
    ** TVHEADEND CHANGES **
    LibreELEC 8.2 does not provide Tvheadend (Server) 4.0 so the add-on repo has been populated with a dummy 4.0 add-on that Kodi will download then mark as broken. It has been discontinued because it is no longer maintained upstream. Tvheadend 4.2 has been available for some time and has proven to be more stable with better features and hardware support. Unfortunately Tvheadend does not provide an automatic upgrade or configuration export/import process so 4.0 users must perform a new installation of Tvheadend 4.2. This is inconvenient, but there is no other option.
    NB: Existing Tvheadend 4.2 add-on users will see “fail to start” messages after updating to the LibreELEC 8.2.0 release. Once Kodi has started it checks our add-on repo and a new (compatible) version is downloaded and installed. Once the add-on has updated Tvheadend 4.2 will start normally.

    Quelle und Link

  • LibreELEC (Krypton) 8.2.0 RELEASE

    LibreELEC 8.2.0 provides a mid-year bump to improve hardware support on Intel and Raspberry Pi hardware. It also resolves minor support issues on a range of devices and fixes a number of important security issues affecting the core OS reported in recent months. Kodi is bumped to 17.5, and Samba bumps to 4.6 which brings support for SMB2/3 to LibreELEC for the first time. PLEASE READ THE RELEASE NOTES below before posting an issue in the forums as there are disruptive changes to Samba, Lirc and Tvheadend.

    NB: An issue with HEVC playback on Raspberry Pi and Slice hardware was reported during the initial canary period and replacement 8.2.0.1 images with a fix (for those devices only) have now been published.
    Changes since LibreELEC 8.0.2 include:

    • Fix boot-time overwrite of samba.conf.sample to ensure v4 template exists
    • Fix Samba startup failures by detecting/disabling old (v3) samba.conf files
    • Fix NAND install on WeTek Hub/Play 2 after Android Marshmallow updates
    • Fix VMware OVF template, drop OVA .img suffix and force ‘installer’ mode
    • Fix an issue in the embedded getedid script
    • Fix Kodi to support 352KHz and 384KHz audio over S/PDIF
    • Fix clearing of core files from /storage/.cache during Kodi startup
    • Fix vulnerability (CVE-2017-1000250 aka Blueborne pt.1) in BlueZ
    • Fix vulnerability (CVE-2017-1000251 aka Blueborne pt.2) in all kernels except Amlogic 3.10
    • Fix a Python /dev/random issue that caused some Python crypto functions to error
    • Fix to prevent boot-loops when a failed update leaves valid files in /storage/.update
    • Update Amlogic 3.14 kernel to use kernel wireless-regdb on all reference devices
    • Update RPi firmware to solve minor CEC button press issues
    • Update RPi wifi firmware to resolve CVE-2017-9417 (Broadpwn)
    • Update wpa_supplicant to resolve multiple CVE’s (KRACK)
    • Update linux-firmware and misc-firmware packages
    • Update nvidia-legacy driver to 340.104
    • Update nvidia main driver to 384.90
    • Update RTL8192EU driver
    • Update RTL8188EU driver
    • Update RPi kernel to 4.9.59
    • Update Generic kernel to 4.11.8
    • Update from LibreSSL to OpenSSL
    • Update Samba to 4.6.8
    • Update to lirc 0.9.4d
    • Update Kodi to 17.5 (the 17.5.1 release is for Android only)
    • Update kernel to enable SMB2 support (default) and where possible SMB3
    • Update LibreELEC settings add-on to expose more Samba config options
    • Revert Hauppauge DualHD tuner support (back to single-tuner, which works)
    • Add Slice and Slice3 projects
    • Add (merge) Virtual project into Generic
    • Add buildsystem changes to make backports from master easier
    • Add support for the Xiaomi Mi Box Bluetooth remote
    • Add support for Xbox ONE (DVB-C/T/T2) USB tuner
    • Add alsa configuration for the IQAudIO Digi+ on Raspberry Pi devices
    • Add dummy Tvheadend 4.0 add-on to ensure 4.0 is disabled on upgrade

    See detailed changes on GitHub – along with lesser differences from the 8.1.2 BETA release.
    !!! SAMBA / SMB CHANGES !!!
    Samba = server software embedded into LibreELEC images
    SMB = client protocol used for connecting to Windows Server and Samba shares
    LibreELEC 8.2.0 includes changes that allow the Kodi SMB client and our embedded Samba server to support SMB2/3 connections; deprecating SMB1 to improve security and performance. This is necessary to cope with changes Microsoft introduced in the Windows 10 ‘Fall Creators Update’ to resolve SMB1 security issues. Please see Microsoft notes here and here and here for an explanation.
    LibreELEC changes are summarised below:

    • The Kodi SMB client now defaults to SMB3 connections but can fail to negotiate SMB3 with old Samba (NAS) versions. A new option in Kodi Settings > Services > SMB client > allows SMB2 or SMB1 to be forced for compatibility with legacy SMB servers.
    • The embedded Samba server defaults to and supports only SMB2/SMB3 connections. The LibreELEC Settings add-on allows the minimum protocol version to be changed, e.g. to enable SMB1 for compatibility with legacy SMB clients. It also supports GUI configuration of WORKGROUP name.
    • Samba detects v3 /storage/.config/samba.conf configurations and ignores them to avoid the Samba service failing on startup. If this happens Samba starts with a default v4 configuration. Custom Samba configurations must be updated to use the new Samba 4.x base template (samba.conf.sample).
    • Kodi “Windows network browsing” needs the Kodi SMB client to support SMB1 and we now default to SMB2/3 connections so browsing no longer works. Windows SMB share sources must be added using the full server/share path. SMB sources from Samba/NAS devices can normally be browsed via the “ZeroConf network browsing” alternative.
    • Connection failures to anonymous and guest shares on a Windows server are normally solved by creating a local machine user account and password credential on the server for Kodi to use, then setting read or read-write permissions for that credential to the shares Kodi will access.
    • Connection failures from a Windows client to the embedded Samba server are probably the result of Win10 changes that remove support for guest/anonymous access. Enabling password authentication in the LibreELEC settings add-on and setting username/password credentials should restore access.
    • Local filesystem mounts of a remote SMB filesystem via systemd or autostart.sh now default to SMB2 so connections to SMB1 shares fail unless vers=1.0 is added into the mount command to force SMB1.

    SAMBA / SMB CONFIGURATION FILES
    Kodi forum posts commonly refer to Samba configuration files in ~/.smb/smb.conf which is common in other Linux distros but is not correct for LibreELEC and Kodi 17.4 or newer. The embedded Samba server obtains the runtime config from /etc/samba/smb.conf unless /storage/.config/samba.conf custom config is present. The Kodi SMB client configuration is stored in /storage/.kodi/.smb/smb.conf which can be extended with changes in /storage/.kodi/.smb/user.conf if required. nb: Changes to smb.conf in the same location will be overwritten by GUI client changes. If you experience issues with SMB shares (client or server) please post in the forums sharing details of the Windows and Samba versions and a Kodi [definition=12,0]debug[/definition] [definition='1','0']log[/definition].
    !! LIRC CHANGES !!
    In LibreELEC 8.0 the Lirc service is enabled when an IR receiver is detected in the system, but it is not started unless used with the lirc_rpi or lirc_xbox drivers or a personal lircd.conf. In LibreELEC 8.2 the Lirc service is enabled and supports all drivers which can result in the service starting and interfering with normal IR operations. If you experience “double button presses” after updating the Lirc service can be disabled in the ‘Services’ tab of the LibreELEC settings add-on. The Lirc service is disabled in new installations and must be manually enabled. Thanks to @HiasoffT changes the Lirc service is now configurable using a combination of /storage/.config/lirc_options.conf and lircd.conf – the same approach used in desktop Linux distributions and most howto instructions users find via Google searches.
    !! TVHEADEND CHANGES !!
    LibreELEC 8.2 does not provide Tvheadend (Server) 4.0 so the add-on repo has been populated with a dummy 4.0 add-on that Kodi will download then mark as broken. It has been discontinued because it is no longer maintained upstream. Tvheadend 4.2 has been available for some time and has proven to be more stable with better features and hardware support. Unfortunately Tvheadend does not provide an automatic upgrade or configuration export/import process so 4.0 users must perform a new installation of Tvheadend 4.2. This is inconvenient, but there is no other option.
    NB: Existing Tvheadend 4.2 add-on users will see “fail to start” messages after updating to the LibreELEC 8.2.0 release. Once Kodi has started it checks our add-on repo and a new (compatible) version is downloaded and installed. Once the add-on has updated Tvheadend 4.2 will start normally.
    INTEL HBR AUDIO
    Initial patches to resolve the lack of pass-through HBR audio on NUC devices and similar with an internal DP > HDMI convertor were published recently. Testing has shown good results on Linux 4.13+ kernels but issues are seen with older Intel/NUC hardware using the 4.11 kernel used in LibreELEC 8.2. As a result these patches are not suitable for the 8.2.0 release and this minor issue will be resolved with LibreELEC 9.0 in the future.
    AUTO-UPDATE
    Following a number of significant security issues we need to ensure more users run the latest release to benefit from security bug fixes. LibreELEC 8.2.0 changes the default OS update option from manual to auto-update to ensure maintenance updates, e.g. 8.2.0 to 8.2.1 roll-out faster. Major version updates will remain user-initiated and there are no changes to the 24-hour canary period between a release and update files being distributed via auto-update.

    Quelle und Link

  • LibreELEC (Krypton) v8.1.2 BETA

    This is the third beta for our 8.2 release. It addresses minor findings related to the Samba bump: we now detect and avoid invalid Samba v3 configurations, old samba.conf.sample templates are overwritten with the new v4 template, and remote SMB shares are mounted using SMB2 or where possible SMB3. The release also adds support for the Raspberry Pi IQAudIO Digi+ board and a Xiaomi BT remote, and includes security fixes for the Blueborne Linux/BlueZ vulnerability. This is hopefully the final 8.1.x beta release; next will be 8.2.0.
    Changes since LibreELEC 8.1.1 include:

    • Fix boot-time overwrite of samba.conf.sample to ensure v4 template exists
    • Fix Samba startup failures by detecting/disabling old (v3) samba.conf files
    • Fix an issue in the embedded getedid script
    • Fix Kodi to support 352KHz and 384KHz audio over S/PDIF
    • Fix clearing of core files from /storage/.cache during Kodi startup
    • Fix vulnerability (CVE-2017-1000250 aka Blueborne pt.1) in BlueZ
    • Fix vulnerability (CVE-2017-1000251 aka Blueborne pt.2) in all kernels except Amlogic 3.10
    • Fix a Python /dev/random issue that caused some Python crypto functions to error
    • Fix to prevent boot-loops when a failed update leaves valid files in /storage/.update
    • Update Amlogic 3.14 kernel to use kernel wireless-regdb on all reference devices
    • Update RPi firmware to solve minor CEC button press issues
    • Update nvidia-legacy driver to 340.104
    • Update RTL8192EU driver
    • Update Samba to 4.6.8
    • Update kernel to enable SMB2 support (default) and where possible SMB3
    • Add support for the Xiaomi Mi Box Bluetooth remote
    • Add alsa configuration for the IQAudIO Digi+ on Raspberry Pi devices

    See detailed changes on GitHub – along with previous changes for LibreELEC v8.1.0 BETAand LibreELEC v8.1.1 BETA releases.



    !!! SAMBA / SMB CHANGES !!!

    LibreELEC 8.2 includes changes that allow the Kodi SMB client and our embedded Samba server to support SMB2/3 connections; deprecating SMB1 to improve security and performance. This is a disruptive change and many users will need to adapt their use of SMB shares or Samba:

    • The Kodi SMB client now defaults to SMB3 connections but can fail to negotiate SMB3 with old Samba (NAS) versions. A new option in Kodi Settings > Services > SMB client > allows SMB2 or SMB1 to be forced for compatibility with legacy SMB servers.
    • The embedded Samba server defaults to and supports only SMB2/SMB3 connections. The LibreELEC Settings add-on allows the minimum protocol versions to be changed, e.g. to enable SMB1 for compatibility with legacy SMB clients. It also supports GUI configuration of WORKGROUP name.
    • Samba detects v3 /storage/.config/samba.conf configurations and ignores them to avoid the Samba service failing on startup. If this happens Samba starts with a default v4 configuration. Custom Samba configurations must be updated to use the new Samba 4.x base template (samba.conf.sample).
    • Kodi “Windows network browsing” needs the Kodi SMB client to support SMB1 and we now default to SMB2/3 connections so browsing no longer works. Windows SMB shares must be added using the full server/share path. SMB sources from Samba/NAS devices can normally be browsed via the “ZeroConf network browsing” alternative.
    • Connection failures to anonymous and guest shares are normally solved by creating a local machine user account and password credential for Kodi to use, then setting read or read-write permissions for that credential to the shares Kodi will access.

    SAMBA / SMB CONFIGURATION FILES

    Kodi SMB client configuration is stored in /storage/.kodi/.smb/smb.conf which can be extended with changes in /storage/.kodi/.smb/user.conf if required. Posts in the Kodi forum often refer to files in ~/.smb/smb.conf which is not correct for Kodi 17.4 or newer.
    Samba server configuration uses /etc/samba/smb.conf unless /storage/.config/samba.conf custom config is present. Samba will not use ~/.smb/smb.conf which is commonly used in other Linux distributions.
    If you experience issues with SMB shares (client or server) please post in the forums sharing information on the Windows and Samba versions and a Kodi [definition=12,0]debug[/definition] [definition='1','0']log[/definition], and we will do our best to help.
    !! LIRC CHANGES !!
    In LibreELEC 8.0 the Lirc service is enabled when an IR receiver is detected in the system, but it is not started unless used with the lirc_rpi or lirc_xbox drivers or a personal lircd.conf. In LibreELEC 8.2 the Lirc service is enabled and supports all drivers which can result in the service starting and interfering with normal IR operations. If you experience “double button presses” after updating the Lirc service can be disabled in the ‘Services’ tab of the LibreELEC settings add-on. The Lirc service is disabled in new installations and must be manually enabled. Thanks to @HiasoffT changes the Lirc service is now configurable using a combination of /storage/.config/lirc_options.conf and lircd.conf – the same approach used in desktop Linux distributions and most howto instructions users find via Google searches.
    INTEL HBR AUDIO
    In the last week initial patches to resolve the lack of pass-through HBR audio on NUC devices and similar with an internal DP > HDMI convertor were published. Current testing shows good results on Linux 4.13+ kernels but issues are seen with older hardware and the 4.11 kernel used in LibreELEC 8.2. We have provided feedback and testing will continue as patches evolve. We will add a stable fix to an 8.2 maintenance release if possible.
    AUTO-UPDATE
    Following a number of significant security issues we need to ensure more users run the latest release to benefit from security bug fixes. We have changed the default option for auto-update from manual to auto, to ensure minor version updates, e.g. 8.2.0 to 8.2.1 roll-out faster. Major version updates are still user-initiated, e.g. 8.2.0 to a future 9.0.0 release, and users can revert to manual update if preferred. There is no change to the 24-hour canary period between release and files being distributed via auto-update.

    Quelle und Link

  • LibreELEC (Krypton) v8.1.1 BETA

    This is the second BETA of our 8.2 release; a mid-year version bump to enhance hardware support and capabilities. This beta addresses issues in our OVA image, a Broadcom WIFI firmware vulnerability for Raspberry Pi 3 and Zero W users, and MPEG issues seen with some nVidia cards. It also adds support for the inexpensive Xbox ONE (DVB-C/T/T2) USB tuner (about €12 on eBay), and LibreELEC settings gains new options for changing the embedded Samba server Workgroup and adjusting the SMB protocol versions supported for security and SMB share compatibility. Kodi is bumped to 17.4 final.
    Changes since LibreELEC 8.1.0 include:

    • Fix VMware OVF template, drop OVA .img suffix and force ‘installer’ mode
    • Update RPi kernel to 4.9.43
    • Update RPi wifi firmware to resolve CVE-2017-9417 (Broadpwn)
    • Update to Samba 4.6.7
    • Update to Kodi 17.4 final
    • Update nVidia main driver to 384.69
    • Update LibreELEC settings add-on to expose more Samba config options
    • Revert Hauppauge DualHD tuner support (back to single-tuner, which works)
    • Add support for Xbox ONE (DVB-C/T/T2) USB tuner

    See detailed changes on GitHub – and the change summary for LibreELEC v8.1.0 BETA


    !!! SAMBA UPDATE – IMPORTANT !!!


    The fall “Creators Update” for Windows 10 removes SMB1 client/server support and NAS devices now ship with configuration that only supports SMB2/3 – causing problems because all versions of Kodi before 17.4 can only make SMB1 connections. This release includes changes that allow the Kodi SMB client and our embedded Samba server to work with SMB2/3 connections; improving SMB security and performance. However, it is a disruptive change:

    • The Kodi SMB client sometimes fails to negotiate SMB3 with old Samba versions. There is a new option in Kodi Settings > Services > SMB client > that allows SMB2 or SMB1 connections to be forced for compatibility with legacy SMB servers.
    • The embedded Samba server now defaults to minimum SMB2 and maximum SMB3 and the LibreELEC Settings add-on allows the supported SMB protocol versions to be changed for compatibility with legacy clients. It also allows configuration of the WORKGROUP name.
    • Samba 3.x /storage/.config/samba.conf configurations must be updated to use the new Samba 4.x template (samba.conf.sample) as some Samba 3.x configuration is incompatible. The embedded Samba server may fail to start until this is done. If the reason for older changes was workgroup name please delete the file and use the new in-GUI configuration method.
    • Browsing SMB shares via “Windows network browsing” in Kodi requires the browser service on the SMB server. This SMB1 service is removed from Win10 in the creators update and there is no equivalent for SMB2/3 versions of the SMB protocol. When Kodi makes SMB2+ connections (which is now our default) Kodi network browsing to add sources will not work. Windows SMB shares can still be added using the full server/share path. It is still possible to browse non-Windows Samba/NAS devices that advertise SMB shares via ZeroConf (aka Bonjour/Avahi).
    • Connection failures to anonymous and guest shares are solved by creating a new local machine (not Microsoft ID) user and strong password for Kodi to use on the server, then assigning appropriate read or read-write permissions to the shares Kodi will access.


    SAMBA CONFIGURATION FILES


    The active configuration for the Kodi SMB client is stored in /storage/.kodi/.smb/smb.conf which can be extended with personal changes in /storage/.kodi/.smb/user.conf. Posts in the Kodi forum often refer to configuration files in ~/.smb/smb.conf – this location is incorrect for Kodi 17.4 which is modified to use its own ‘internal’ smbclient configuration.
    The active configuration file for the embedded Samba server is /etc/samba/smb.conf unless a personal configuration exists in /storage/.config/samba.conf. Samba is started with an explicit declaration of the config file to use so it will not detect ~/.smb/smb.conf if it exists (this location is used on some other Linux distributions).
    We see frequent forum postings where users attempt to change the Kodi smbclient configuration through the /storage/.config/samba.conf file. This is pointless. The embedded Samba server configuration has no effect on the Samba client connections made by Kodi.
    If you experience issues with SMB shares (client or server) please post in the forums sharing information on the Windows and Samba versions, and a Kodi [definition=12,0]debug[/definition] [definition='1','0']log[/definition], and we will do our best to help.
    !! LIRC CHANGES !!
    In LibreELEC 8.0 the Lirc service is enabled when an IR receiver is detected in the system, but it is not started unless used with the lirc_rpi or lirc_xbox drivers or a personal lircd.conf. In LibreELEC 8.2 the Lirc service supports all drivers. This can result in the service starting and interfering with normal IR operations. If you experience “double button presses” after updating the Lirc service can be disabled in the ‘Services’ tab of the LibreELEC settings add-on. The Lirc service is disabled in new installations and must be manually enabled. Thanks to @HiasoffT changes the Lirc service is now configurable using a combination of /storage/.config/lirc_options.conf and lircd.conf – the same approach as most desktop Linux distributions (and howto instructions users find via Google searches).


    AUTO-UPDATE


    After recent security issues with Kodi and Samba we need to ensure more users are running the latest release to benefit from feature and security bug fixes. To achieve this we have changed the default setting for auto-update from manual to auto. Auto-update provides maintenance updates, e.g. 8.1.0 BETA to 8.1.1 and 8.2.0 and from 8.2.0 to 8.2.1 etc. in the 8.2 release series. Major version updates are still manual (user-initiated) updates, e.g. 8.2.0 to a future 9.0.0 release. Users can revert to manual update in the LibreELEC settings add-on. NB: LibreELEC operates a 24-hour canary period between new release files being available and auto-update being enabled.


    Quelle und weiter Informationen hier entlang

  • LibreELEC USB-SD Creator v1.3

    LibreELEC USB-SD Creator v1.3 is released with support for Brazilian Portuguese and Chinese localisations and minor improvements to existing translations.

    It also adds audible feedback on completion of image download and image writing, and corrects visual sorting for releases with x.x.x.x numbering.

    The Asturian localisation has been tweaked to show an Asturian (not Spanish) flag icon.

    If you would like to see a localisation added in a future release please visit the LibreELEC team page on Transifex to request it and contribute the translated text strings.

    Requesting a new localisation does not automatically translate it!

    NB: Transifex currently shows missing and incomplete translations for Arabic and Romanian.

    Quelle : Libreelec.tv