CVE-2020-5247

In Puma (RubyGem) before 4.3.2 and 3.12.3, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. CR, LF or/r, /n) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting.

While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS).

This is related to CVE-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server.

This has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters.

In Puma (RubyGem) before 4.3.2 and before 3.12.3, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. CR, LF or/r, /n) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting. While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS). This is related to CVE-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server. This has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters.

In Puma (RubyGem) before 4.3.2 and before 3.12.3, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. CR, LF or/r, /n) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting. While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS). This is related to CVE-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server. This has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters.

In Puma (RubyGem) before 4.3.2 and before 3.12.3, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. CR, LF or/r, /n) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting. While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS). This is related to CVE-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server. This has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters.

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.

This update was imported from the SUSE:SLE-15-SP2:Update update project.

This update for rmt-server fixes the following issues:

• 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.

• Version 2.6.4

• 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.

• Version 2.6.3

• Instead of using an MD5 of URLs for custom repository friendly_ids, RMT now builds an ID from the name.

• Version 2.6.2

• 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.

• Version 2.6.1

• Fixed an issue where relative paths supplied to rmt-cli import repos caused the command to fail.

• Version 2.6.0

• 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.

• Version 2.5.20

• Updated rails from 6.0.3.2 to 6.0.3.3:

  • actionview (CVE-2020-15169)

• Version 2.5.19

• RMT now has the ability to remove local systems with the command rmt-cli systems remove.

• Version 2.5.18

• Fixed exit code for rmt-cli mirror and its subcommands. Now it exits with 1 whenever an error occurs during mirroring

• Improved message logging for rtm-cli mirror. Instead of logging an error when it occurs, the command summarize all errors at the end of execution. Now log messages have colors to better identify failure/success.

• Version 2.5.17

• RMT no longer provides the installer updates repository to systems via its zypper service. This repository is used during the installation process, as it provides an up-to-date installation experience, but it has no use on an already installed system.

• Version 2.5.16

• Updated RMT's rails and puma dependencies.

  • puma (CVE-2020-11076, CVE-2020-11077, CVE-2020-5249, CVE-2020-5247 CVE-2019-16770)
  • actionpack (CVE-2020-8185, CVE-2020-8164, CVE-2020-8166)
  • actionview (CVE-2020-8167, CVE-2020-5267, CVE-2019-5418, CVE-2019-5419)
  • activesupport (CVE-2020-8165)
  • railties (CVE-2019-5420)

• Version 2.5.15

• RMT now checks if repositories are fully mirrored during the activation process. Previously, RMT only checked if the repositories were enabled to be mirrored, but not that they were actually mirrored. In this case, RMTs were not able to provide the repository data which systems assumed it had.

• Version 2.5.14

• Enable 'Installer-Updates' repositories by default

• Fixed deprecation warning when thor encountered an error. Also, instead of returning 0 for thor errors, rmt-cli will return 1 instead.

• Version 2.5.13

• Added rmt-cli repos clean command to remove locally mirrored files of repositories which are not marked to be mirrored.

• Previously, RMT didn't track…

This update for ansible, crowbar-core, crowbar-ha, crowbar-openstack, etcd, flannel, grafana, keepalived, kibana, memcached, monasca-installer, openstack-dashboard-theme-SUSE, openstack-manila, openstack-neutron-fwaas, openstack-nova, openstack-tempest, python-Django, python-Pillow, python-psql2mysql, python-psutil, python-py, python-pysaml2, python-waitress, rabbitmq-server, release-notes-suse-openstack-cloud, zookeeper fixes the following issues:

Security fixes included ins this update:

ansible

• CVE-2019-3828: Fixed a path traversal in the fetch module (bsc#1126503).

grafana

• CVE-2020-13379: Fixed an incorrect access control issue which could lead to information leaks or denial of service (bsc#1172409).
• CVE-2020-12052: Fixed an cross site scripting vulnerability related to the annotation popup (bsc#1170657).

kibana

• CVE-2020-10743: Fixed a clickjacking vulnerability (bsc#1171909).

memcached (to version 1.5.17)

• CVE-2019-15026: Fixed a stack-based buffer over-read in conn_to_str()n (bsc#1149110).
• CVE-2019-11596: Fixed a denial of service in the 'lru' command (bsc#1133817)
• CVE-2018-1000115: Disabled UDP by default to reduce DDoS amplification attacks (bsc#1083903).

python-Django

• CVE-2020-13254: Fixed a data leakage via malformed memcached keys (bsc#1172167).
• CVE-2020-13596: Fixed a cross site scripting vulnerability related to the admin parameters of the ForeignKeyRawIdWidget (bsc#1172166).
• Fixed a regression with the fix for CVE-2019-3498 (bsc#1161349).

python-Pillow

• CVE-2019-16865: Fixed a denial of service with specially crafted image files (bsc#1153191).
• CVE-2020-5312: Fixed a buffer overflow in the PCX P mode (bsc#1160152).
• CVE-2020-5313: Fixed a buffer overflow related to FLI (bsc#1160153).
• CVE-2019-19911: Fixed a denial of service in FpxImagePlugin.py (bsc#1160192).

python-pysaml2

• CVE-2020-5390: Fixed an issue with the verification of signatures in SAML documents (bsc#1160851)
• CVE-2017-1000246: Fixed an issue with weak encryption data, caused by initialization vector reuse(bsc#1068612).

python-waitress (to version 1.4.3)

• CVE-2019-16785: Fixed HTTP request smuggling through LF vs CRLF handling (bsc#1161088).
• CVE-2019-16786: Fixed HTTP request smuggling through invalid Transfer-Encoding (bsc#1161089).
• CVE-2019-16789: Fixed HTTP Request Smuggling through invalid whitespace characters (bsc#1160790).
• CVE-2019-16792: Fixed HTTP Request Smuggling through Content-Length header handling (bsc#1161670).

rubygem-activeresource

• CVE-2020-8151: Fixed information disclosure issue through specially crafted requests (bsc#1171560)

rubygem-json-1_7

• CVE-2020-10663: Fixed Unsafe Object Creation Vulnerability in JSON (bsc#1167244)

rubygem-puma

• CVE-2020-11077: Fixed HTTP Request Smuggling through proxy (bsc#1172175)
• CVE-2020-11076: Fixed HTTP Request smuggling through invalid Transfer-Encoding header.
• CVE-2020-5247: Fixed HTTP Response Splitting through newline characters handling (bsc#1165402)

zookeeper:

• CVE-2019-0201: Fixed an information disclosure related to getACL() (bsc#1135773).

Non security fixes included in this update:

Changes in ansible:

• Add 0001-Disallow-use-of-remote-home-directories-containing-..patch (bsc#1126503, CVE-2019-3828)

Changes in crowbar-core:

• Update to version 4.0+git.1580209654.1d112d31f:
  • network: start OVS before wickedd (SOC-11067)

Changes in crowbar-ha:

• Update to version 4.0+git.1585316203.d6ad2c8:
  • [4.0] add ssl termination on haproxy (bsc#1149535)

Changes in crowbar-openstack:

• Update to version 4.0+git.1589804581.9972163f0:

  • [4.0] magnum: fix check for image/flavor (SOC-11251)

• Update to version 4.0+git.1589647351.ccfd9481f:

  • [4.0] trove: fix rabbitmq connection URL (SOC-11286)

• Update to version 4.0+git.1589458214.9f765aa08:

  • [4.0] Fix create magnum k8s image and flavor (SOC-11251)

• Update to version 4.0+git.1588271860.131fc8cc1:

  • run keystone_register on cluster founder only when HA (SOC-11248)
  • nova: run…

This update for ardana-ansible, ardana-barbican, ardana-db, ardana-monasca, ardana-mq, ardana-neutron, ardana-octavia, ardana-tempest, crowbar-core, crowbar-ha, crowbar-openstack, documentation-suse-openstack-cloud, memcached, openstack-manila, openstack-neutron, openstack-nova, pdns, python-amqp, rubygem-puma, zookeeper contains the following fixes:

Security fix for rubygem-puma:

• CVE-2020-5247: Fixed an issue where the newlines in headers according to Rack spec were not split (bsc#1165402)

Security fix for openstack-manila:

• CVE-2020-9543: Fixed an issue where an attacker could view, update, delete, or share resources that do not

Security fixes for memcached:

• CVE-2019-15026: Fixed a stack-based buffer over-read in conn_to_str() in memcached.c (bsc#1149110).
• CVE-2019-11596: Fixed NULL pointer dereference in process_lru_command() in memcached.c (bsc#1133817).

Security fixes for pdns:

• CVE-2019-3871: Fixed a denial of service with the HTTP remote backend when the attacker can send crafted DNS queries (bsc#1129734).
• CVE-2018-10851: Fixed a denial of service via crafted zone record (bnc#1114157).
• CVE-2018-14626: Fixed a denial of service by hiding DNSSEC records using a crafted DNS query (bsc#1114169).

Security fixes for zookeeper:

• CVE-2019-0201: Fixed an information disclosure in the ACL handling (bsc#1135773).
• CVE-2017-5637: Fixed incorrect input validation with wchp/wchc four letter words (bsc#1040519).

Changes in ardana-ansible:

• Update to version 8.0+git.1583432621.24fa60e:
  • Upgrade pre-checks in Cloud 8 and Cloud 9 (SOC-10300)

Changes in ardana-barbican:

• Update to version 8.0+git.1585152761.8ef3d61:
  • monitor ardana-node-cert (SOC-10873)

Changes in ardana-db:

• Update to version 8.0+git.1583944923.03cca6c:
  • monitor MySQL TLS certificate (SOC-10873)

Changes in ardana-monasca:

• Update to version 8.0+git.1583944894.38f023a:
  • Add certificate file check alarm (SOC-10873)

Changes in ardana-mq:

• Update to version 8.0+git.1583944811.dc14403:
  • monitor RabbitMQ TLS certificate (SOC-10873)

Changes in ardana-neutron:

• Update to version 8.0+git.1584715262.e4ea620:
  • Add symlink for neutron-fwaas.json.j2 (bsc#1166290)

Changes in ardana-octavia:

• Update to version 8.0+git.1585171918.418f5cf:

  • Reconfigure monitor if needed (SOC-10873)

• Update to version 8.0+git.1585168661.135c735:

  • fix Octavia client cert redeploy (SOC-10873)

• Update to version 8.0+git.1585152502.f15907a:

  • monitor Octavia client certificate (SOC-10873)

Changes in ardana-tempest:

• Update to version 8.0+git.1585311051.6ab5488:
  • Enable port-security feature in tempest(SOC-11027)

Changes in crowbar-core:

• Update to version 5.0+git.1585575551.16781d00d:

  • upgrade: Point to config dir instead of config file (SOC-11171)
  • upgrade: Do not call neutron-evacuate-lbaasv2-agent with use_crm (SOC-11171)

• Update to version 5.0+git.1585316726.670746c8c:

  • upgrade: Fix systemd unit listing (trivial)

• Update to version 5.0+git.1585213241.46f12f9be:

  • upgrade: Remove the assignement of crowbar-upgrade role (SOC-11166)

• Update to version 5.0+git.1585118470.eed9020de:

  • Update the default value of OS version (trivial)
  • Ignore CVE-2020-5267 in CI (bsc#1167240)
  • Ignore CVE-2020-10663 in CI (bsc#1167244)

• Update to version 5.0+git.1583911121.d6b4b4b1a:

  • ses: Make SES UI safe for unknown options (trivial)
  • ses: Use cinder user for nova (SOC-11119)
  • ses: Added helper for populating cinder volumes (SOC-11117)
  • ses: Add ses cookbook (SOC-11114)
  • ses: Configuration upload (SOC-11115)

• Update to version 5.0+git.1583309007.e3a8b81e9:

  • Ignore CVE-2020-8130 in CI (bsc#1164804)
  • Ignore CVE-2020-5247 (bsc#1165402)

Changes in crowbar-ha:

• Update to version 5.0+git.1585316176.344190f:
  • add ssl termination on haproxy (bsc#1149535)

Changes in crowbar-openstack:

• Update to version 5.0+git.1585304226.2164b7895:

  • nova: Fix migration numbers (trivial)

• Update to version…

This update for ardana-ansible, ardana-barbican, ardana-cluster, ardana-db, ardana-designate, ardana-input-model, ardana-logging, ardana-monasca, ardana-mq, ardana-neutron, ardana-octavia, ardana-osconfig, ardana-tempest, ardana-tls, crowbar-core, crowbar-ha, crowbar-openstack, memcached, openstack-ceilometer, openstack-cinder, openstack-designate, openstack-heat, openstack-ironic, openstack-ironic-image, openstack-manila, openstack-neutron, openstack-nova, openstack-octavia, openstack-octavia-amphora-image, python-cinderclient, python-glanceclient, python-ironic-lib, python-ironicclient, python-keystonemiddleware, python-manila-tempest-plugin, python-novaclient, python-octaviaclient, python-openstackclient, python-os-brick, python-oslo.config, python-oslo.rootwrap, python-oslo.utils, python-swiftclient, python-watcherclient, release-notes-suse-openstack-cloud, rubygem-crowbar-client, rubygem-puma, zookeeper contains the following fixes:

Security fixes for memcached:

• CVE-2019-15026: Fixed a stack-based buffer over-read in conn_to_str() (bsc#1149110).
• CVE-2019-11596: Fixed a denial of service when parsing crafted lru command messages in process_lru_comma() (bsc#1133817).

Security fixes for zookeeper:

• CVE-2019-0201: Fixed a information disclosure vulnerability related to getACL() (bsc#1135773).

Changes in rubygem-crowbar-client:

• Update to 3.9.2
  • Enable SES commands in Cloud8 (SOC-11122)

Changes in rubygem-puma:

• Add CVE-2020-5247.patch (bsc#1165402) 'Fixes a problem where we were not splitting newlines in headers according to Rack spec' The patch is reduced compared to the upstream version, which was patching also the parts that are not implemented in our old Puma version. This applies to unit test as well.

Changes in ardana-ansible:

• Update to version 9.0+git.1587034359.a12678b:

  • Include SLE 12 SP3 LTSS repos in list of managed repos (SOC-11223)

• Update to version 9.0+git.1586793433.f7bbf1b:

  • Ensure rabbitmq-server not running during dist-upgrade (SOC-11083)

• Update to version 9.0+git.1586521995.f709c73:

  • Upgrade packages before _osconfig-upgrade.yml (SOC-11149)

• Update to version 9.0+git.1584135277.f4d488a:

  • Serialise the _ardana-update-base.yml zypper actions (SOC-11083)

• Update to version 9.0+git.1583518616.d4eb33f:

  • Upgrade pre-checks in Cloud 8 and Cloud 9 (SOC-10300)

Changes in ardana-barbican:

• Update to version 9.0+git.1583953599.cd723bb:
  • monitor ardana-node-cert (SOC-10873)

Changes in ardana-cluster:

• Update to version 9.0+git.1585653734.c1fe3b2:
  • Use bool filter to ensure valid boolean evaluation (SOC-11192)

Changes in ardana-db:

• Update to version 9.0+git.1586543314.6b6aa20:

  • Improve boostrap error handling (SOC-11207)

• Update to version 9.0+git.1583946648.0892bab:

  • monitor MySQL TLS certificate (SOC-10873)

• Update to version 9.0+git.1583527362.d9e9436:

  • fix mysql output and root password update (SOC-11152)

Changes in ardana-designate:

• Update to version 9.0+git.1583445435.4bd1793:
  • Designate zone/pool to worker/producer migration (SOC-10095)

Changes in ardana-input-model:

• Update to version 9.0+git.1584632190.9541c56:
  • add port neutron security extension to CI models (SOC-11027)

Changes in ardana-logging:

• Update to version 9.0+git.1585929695.f35b591:
  • Fix YAMLLoadWarning: calling yaml.load() without Loader (bsc#1168593)

Changes in ardana-monasca:

• Update to version 9.0+git.1586769889.d43d736:

  • Retry systemctl status for auto-restarting services (SOC-11210)

• Update to version 9.0+git.1583359379.b92a013:

  • Add certificate file check alarm (SOC-10873)

Changes in ardana-mq:

• Update to version 9.0+git.1586350749.a463fd2:

  • Actually fail if sync HA queues retries exceeded (SOC-11083)

• Update to version 9.0+git.1583428243.c1a72a8:

  • monitor RabbitMQ TLS certificate (SOC-10873)

Changes in ardana-neutron:

• Update to version 9.0+git.1587667603.507fb50:

  • Add network.target 'After' option (bsc#1169770)

• Update…

This update for rubygem-puma fixes the following issues:

• Add patches for disabling TLSv1.0 and TLSv1.1 (jsc#SLE-6965):
• Add CVE-2020-11077.patch (bsc#1172175, CVE-2020-11077)
• Add CVE-2020-11076.patch (bsc#1172176, CVE-2020-11076)
• Add CVE-2020-5247.patch (bsc#1165402) 'Fixes a problem where we were not splitting newlines in headers according to Rack spec' The patch is reduced compared to the upstream version, which was patching also the parts that are not implemented in our old Puma version. This applies to unit test as well.
• Add CVE-2019-16770.patch (bsc#1158675, SOC-10999, CVE-2019-16770) This patch fixes a DoS vulnerability a malicious client could use to block a large amount of threads.

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.

This update for rmt-server fixes the following issues:

• 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.

• Version 2.6.4

• 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.

• Version 2.6.3

• Instead of using an MD5 of URLs for custom repository friendly_ids, RMT now builds an ID from the name.

• Version 2.6.2

• 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.

• Version 2.6.1

• Fixed an issue where relative paths supplied to rmt-cli import repos caused the command to fail.

• Version 2.6.0

• 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.

• Version 2.5.20

• Updated rails from 6.0.3.2 to 6.0.3.3:

  • actionview (CVE-2020-15169)

• Version 2.5.19

• RMT now has the ability to remove local systems with the command rmt-cli systems remove.

• Version 2.5.18

• Fixed exit code for rmt-cli mirror and its subcommands. Now it exits with 1 whenever an error occurrs during mirroring

• Improved message logging for rtm-cli mirror. Instead of logging an error when it occurs, the command summarize all errors at the end of execution. Now log messages have colors to better identify failure/success.

• Version 2.5.17

• RMT no longer provides the installer updates repository to systems via its zypper service. This repository is used during the installation process, as it provides an up-to-date installation experience, but it has no use on an already installed system.

• Version 2.5.16

• Updated RMT's rails and puma dependencies.

  • puma (CVE-2020-11076, CVE-2020-11077, CVE-2020-5249, CVE-2020-5247 CVE-2019-16770)
  • actionpack (CVE-2020-8185, CVE-2020-8164, CVE-2020-8166)
  • actionview (CVE-2020-8167, CVE-2020-5267, CVE-2019-5418, CVE-2019-5419)
  • activesupport (CVE-2020-8165)
  • railties (CVE-2019-5420)

• Version 2.5.15

• RMT now checks if repositories are fully mirrored during the activation process. Previously, RMT only checked if the repositories were enabled to be mirrored, but not that they were actually mirrored. In this case, RMTs were not able to provide the repository data which systems assumed it had.

• Version 2.5.14

• Enable 'Installer-Updates' repositories by default

• Fixed deprecation warning when thor encountered an error. Also, instead of returning 0 for thor errors, rmt-cli will return 1 instead.

• Version 2.5.13

• Added rmt-cli repos clean command to remove locally mirrored files of repositories which are not marked to be mirrored.

• Previously, RMT didn't track…

This update for rmt-server fixes the following issues:

• 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.

• Version 2.6.4

• 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.

• Version 2.6.3

• Instead of using an MD5 of URLs for custom repository friendly_ids, RMT now builds an ID from the name.

• Version 2.6.2

• 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.

• Version 2.6.1

• Fixed an issue where relative paths supplied to rmt-cli import repos caused the command to fail.

• Version 2.6.0

• 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.

• Version 2.5.20

• Updated rails from 6.0.3.2 to 6.0.3.3:

  • actionview (CVE-2020-15169)

• Version 2.5.19

• RMT now has the ability to remove local systems with the command rmt-cli systems remove.

• Version 2.5.18

• Fixed exit code for rmt-cli mirror and its subcommands. Now it exits with 1 whenever an error occurs during mirroring

• Improved message logging for rtm-cli mirror. Instead of logging an error when it occurs, the command summarize all errors at the end of execution. Now log messages have colors to better identify failure/success.

• Version 2.5.17

• RMT no longer provides the installer updates repository to systems via its zypper service. This repository is used during the installation process, as it provides an up-to-date installation experience, but it has no use on an already installed system.

• Version 2.5.16

• Updated RMT's rails and puma dependencies.

  • puma (CVE-2020-11076, CVE-2020-11077, CVE-2020-5249, CVE-2020-5247 CVE-2019-16770)
  • actionpack (CVE-2020-8185, CVE-2020-8164, CVE-2020-8166)
  • actionview (CVE-2020-8167, CVE-2020-5267, CVE-2019-5418, CVE-2019-5419)
  • activesupport (CVE-2020-8165)
  • railties (CVE-2019-5420)

• Version 2.5.15

• RMT now checks if repositories are fully mirrored during the activation process. Previously, RMT only checked if the repositories were enabled to be mirrored, but not that they were actually mirrored. In this case, RMTs were not able to provide the repository data which systems assumed it had.

• Version 2.5.14

• Enable 'Installer-Updates' repositories by default

• Fixed deprecation warning when thor encountered an error. Also, instead of returning 0 for thor errors, rmt-cli will return 1 instead.

• Version 2.5.13

• Added rmt-cli repos clean command to remove locally mirrored files of repositories which are not marked to be mirrored.

• Previously, RMT didn't track…