SUSE SLES15 Security Update : rmt-server (SUSE-SU-2020:3036-1)


This update for rmt-server fixes the following issues : Update to version 2.6.5: Solved potential bug of SCC repository URLs changing over time. RMT now self heals by removing the previous invalid repository and creating the correct one. Add web server settings to /etc/rmt.conf: Now it's possible to configure the minimum and maximum threads count as well the number of web server workers to be booted through /etc/rmt.conf. Instead of using an MD5 of URLs for custom repository friendly_ids, RMT now builds an ID from the name. Fix RMT file caching based on timestamps: Previously, RMT sent GET requests with the header 'If-Modified-Since' to a repository server and if the response had a 304 (Not Modified), it would copy a file from the local cache instead of downloading. However, if the local file timestamp accidentally changed to a date newer than the one on the repository server, RMT would have an outdated file, which caused some errors. Now, RMT makes HEAD requests to the repositories servers and inspect the 'Last-Modified' header to decide whether to download a file or copy it from cache, by comparing the equalness of timestamps. Fixed an issue where relative paths supplied to `rmt-cli import repos` caused the command to fail. Friendlier IDs for custom repositories: In an effort to simplify the handling of SCC and custom repositories, RMT now has friendly IDs. For SCC repositories, it's the same SCC ID as before. For custom repositories, it can either be user provided or RMT generated (MD5 of the provided URL). Benefits : - `rmt-cli mirror repositories` now works for custom repositories. - Custom repository IDs can be the same across RMT instances. - No more confusing 'SCC ID' vs 'ID' in `rmt-cli` output. Deprecation Warnings : - RMT now uses a different ID for custom repositories than before. RMT still supports that old ID, but it's recommended to start using the new ID to ensure future compatibility. Updated rails and puma dependencies for security fixes. Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.