Eclipse Kura - 5.0.1   - December 2021
-------------------------------------------------------------------------
Description:
This service release of Eclipse Kura fixes the Log4J vulnerabilities CVE-2021-44228, CVE-2021-45046 and CVE-2021-45105 
by updating the Log4J dependencies to 2.17.0. Slf4J has been updated as well to 1.7.32. 


Changes:
  * Target Platform Updates
    * log4j.version=2.17.0
    * slf4j.api.version=1.7.32


Target Environments:
  * Kura is released as pre-compiled binary installers for the following platforms:
    * Raspberry Pi 2/3/4 based on Raspberry Pi OS Buster (32 bits) or Raspberry Pi OS Bullseye (32 bits)
    * Intel Up Squared board running Ubuntu 18  
    * Intel Up Squared board running Centos 7 (Experimental)
    * Rock960 ARM_64 running Ubuntu 16 (NN version only)
  * Kura is also available as a pre-built Docker container for Centos 7 and Alpine  


Known Issues :
  * The intel-up2-centos-7, intel-up2-ubuntu-18 and rock960-ubuntu-16 don't support the Unprivileged Command Service (see #3598)
  * An update to the sslmanagerservice where the pid of the keystoreservice is updated can lead to an error in the following reconnection. 
    The issue impact is limited, if the dataservice reconnect option is enabled.  
  * The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  * Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  * BLE also tested on the Raspberry Pi B with a Broadcom BCM20702 USB dongle and the TI SensorTag. The kernel version was
    "Linux raspberrypi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux".
    Note that on the kernel "Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease)
    (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015" has a bug on
    gatttool and the BLE connection will encounter a failure.
  * WiFi on Raspberry Pi 2 has only been tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  * Hardware watchdog: not implemented on all platforms
  * Only one WAN interface is currently supported. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  * The rock-960-ubuntu-nn does not support chrony features.
  * The rock-960-ubuntu-nn does not support writings to the hardware clock.
  * The rock-960-ubuntu-nn does not support the download of the journald logs.
  * #3176: Modem interface number management
  * #3005: Kura Gets Stuck in Loading View if Services Clicked Too Fast
  * #2843: Access Banner Content All in One Line
  * #2747: No Spacing Between "Wire Components" and Error in Wire Graph
  * #2728: WireGraph Component Description Windows Too Wide
  * #2725: Different Pop-up Windows for Warnings
  * #2702: Error Message For Long Item Names Not Displayed Properly
  * #2696: Component Name Inteferes With Wire Graph Border
  * #2695: Component Names in Wires Not Limited
  * #2410: Deployment handler and URLs with many query parameters
  * #2038: [Kura 3.2.0 QA] Package uninstallation log
  * #1993: Search Domains Are Not Supported
  * #1663: Authentication Issue with Deploy V2
  * #1572: serial modbus has errors on some hardware
  * #1529: OSGI console is not redirected to Eclipse IDE with Kura 3.0
  * #1201: Wifi password incorrectly read from snapshot in Access Point mode
  * #1161: Incorrectly configuring a component can be irreversable.
  * #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  * #1016: ConfigurationServiceImpl creates duplicate instances
  * #797:  Design of ServiceUtil is broken
  * #771:  Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  * #654:  Clean up static initialization around "modem" functionality
  * #645:  Clean up internal dependencies in Kura
  * #522:  [Net] Modem monitor should monitor interfaces, not modems
  * #486:  Build environment broken on Windows
  * #406:  Replace System.get* with calls to SystemService.getProperties
  * #348:  WpaSupplicantConfigReader.getWifiClientConfig() should support cases where key_mgmt scheme is not set
  * #329:  [DEPLOY-V2] Review/refactoring needed
  * #297:  [Status led] What connection instance controls the status led?
  * #253:  Check if bundle contexes correctly unget services after invoking getService
  * #222:  CloudConnectionStatusServiceImpl does not cancel workers on component deactivation


Changelog:
  * 6a27f148f6 - [Backport release-5.0.0] Updated log4j to 2.17.0 (Maiero)
  * 0162a25372 - Preparing for 5.0.1 release (#3716) (Matteo Maiero)
  * f4347753d3 - Updated log4j2 to 2.16.0 (#3713) (Matteo Maiero)
  * 805aad63d4 - Updating log4j version to 2.15.0. (Maiero)
  * 33e5e73170 - Updating Kura 5 for next development round (Maiero)