X-Road v6.24.0 Release Notes

Owned by Raido Kaju
Oct 14, 2020
12 min read

Release Info

Version number6.24.0
Release date31.08.2020
Supported versions
  • 6.240
  • 6.23.0
  • 6.22.1
Supported platforms

Central Server

  • Ubuntu 18.04 LTS

Configuration Proxy

  • Ubuntu 18.04 LTS

Security Server

  • Ubuntu 18.04 LTS
  • RHEL 7
  • RHEL 8
Official documentationhttps://github.com/nordic-institute/X-Road/tree/master/doc
Source codehttps://github.com/nordic-institute/X-Road/tree/master
Software licenseMIT
On this page:

Changes in This Release

On Ubuntu 18.04 LTS upgrading the Security Server from versions 6.22.1/6.23.0 to version 6.24.0 requires using apt install xroad-securityserver OR apt full-upgrade commands.

On RHEL7 upgrading the Security Server from versions 6.22.1/6.23.0 to version 6.24.0 is done using yum update.

Doing apt upgrade is not enough for this version upgrade since the command does not remove the xroad-jetty and xroad-nginx packages that are removed in the upgrade.

Please note that Security Server direct upgrade from versions < 6.22 to 6.24.0 is not supported. In case you’re running a Security Server version < 6.22, please upgrade to version 6.22.1 or 6.23.0 first, and then from version 6.22.1/6.23.0 to version 6.24.0.

Summary

  • New user interface provides improved user experience (UX) for Security Server administrators.
    • New intuitive user interface makes regular administrative tasks easier and supports streamlining the on-boarding process of new X-Road members.
    • More information related to the new user interface can be found in Appendix 1.
  • Common maintenance and configuration tasks can be automated using the management API.
    • Maintaining and operating multiple Security Servers can be done more efficiently as configuration and maintenance tasks require less manual work.
    • More information about the management API can be found in the Security Server User Guide.
    • The full OpenAPI 3 description of the API is available here.
  • Support for running Security Server on Red Hat Enterprise Linux 8 (RHEL8).
  • Technology updates and decreased technical debt.
  • Updates on operational monitoring protocols that enable monitoring of SOAP and REST services in more consistent manner.
    • N.B.! The updates cause breaking changes in the Operational Monitoring protocols.
  • Better support for using external database services on different platforms (e.g. Amazon Web Services, Microsoft Azure, Google Cloud Platform) for both Central Server and Security Server.
    • N.B.! Major changes in Central Server and Security Server database schemas.
  • Changes in allowed characters in X-Road system identifiers and improved validation of the identifiers.

Completed Issues

Access to the X-Road Backlog and issue details requires signing up for an account. Sign up now and get access to the backlog and issue details immediately.

Issue IDTypeSummary
XRDDEV-17Improvement

Add validation to client certificates expiration date. Before version 6.24.0 the Security Server does not validate the expiration date of a client information system's certificate. Starting from version 6.24.0 the expiration date of client certificates is validated, and in case the certificate is expired, a warning is logged in the proxy log by default. It is also possible to prevent the use of expired client certificates and block message processing in case an expired client certificate is detected. This can be achieved by adding the below configuration in "/etc/xroad/conf.d/local.ini" on Security Server:

/etc/xroad/conf.d/local.ini
[proxy]
enforce-client-is-cert-validity-period-check=true
XRDDEV-59Improvement

Update the date and time format used in the X-Road application logs to be based on the international standard ISO 8601 so that it's consistent. Starting from version 6.24.0 the date and time format used in the X-Road application logs is "yyyy-MM-ddTHH:mm:ss.SSSZ".

Dates in log messages and exceptions use ISO 8601 with timezone. Timestamp formats in file names remain unchanged.

XRDDEV-63FixFix signer-console reporting correctly closed akka connections as erros.
XRDDEV-68FixFix the usage of thread local variables in the Security Server.
XRDDEV-113ImprovementOptimize message log archiving performance. The database query logic used in the archival process was updated to use streaming instead of multiple separate queries.
XRDDEV-125Improvement

Improve the Security Server architecture documentation by adding a description of contracts and responsibilities of different Security Server modules. The information is available in the Security Server Architecture document (ARC-SS).

XRDDEV-142ImprovementAdd DNS name or IP that was used to register the Security Server to the Security Server UI. Starting from version 6.24.0 the DNS name or IP can be viewed in the Security Server UI by taking the mouse cursor over the Security Server name on the top banner.
XRDDEV-261Improvement

Improve Security Server's fault tolerance when internal load balancing is used. After the change requests are no longer being sent to Security Servers with a failing TLS handshake.

The fastest wins connection selection Security Server HA strategy was updated to take successful TLS handshake into account when choosing the winner. Before version 6.24.0 the fastest wins selection worked so that the Security Server that first responded to TCP connect request was selected as the winner. In case TLS handshake failed in a later phase of the message flow, the whole request failed. Starting from version 6.24.0 the fastest wins selection takes TLS handshake into account, and a Security Server with a failing TLS handshake cannot be selected as a winner. For example, a Security Server that is running without a valid authentication certificate or without PIN code being typed, does no longer receive requests from other Security Servers.

XRDDEV-377Improvement

Improve failover for timestamping requests so that failover works also when the TSA certificate is incorrect and/or expired. Before the change failover worked only in case connection to the TSA failed, but starting from version 6.24.0 the failover is done also when connection succeeds, but the TSA response is invalid. After the change timestamping is more robust since all the configured TSAs are tried until a valid response is received. In case any of the configured TSAs is not able to provide a valid response, timestamping fails. However, the failover requires that the Security Server has more than one configured TSA.

XRDDEV-440Improvement

Improve security and configurability by adding a separate database users for Security Server database migrations, so that the normal DB users used by the application cannot update the DB schema. Each Security Server database has its own admin user (by default serverconf_admin, messagelog_admin, opmonitor_admin) and normal DB user (by default serverconf, messagelog, opmonitor).

The migrations user is created on new installs, upgrades are not affected.

XRDDEV-546Improvement

Update operational monitoring implementation and protocols so that separate fields for storing the same metric for SOAP and REST messages are not used. After the change there's a single field for each metric that is used for both SOAP and REST messages.

getSecurityServerOperationalData

Changes in the "getSecurityServerOperationalData" response's "operational-monitoring-data.json.gz" attachment:

  • requestSoapSize → requestSize
  • responseSoapSize → responseSize
  • requestRestSize → requestSize
  • responseRestSize → responseSize
  • serviceType → this new field is returned with possible values WSDL, REST, OPENAPI3
  • soapFaultCode → faultCode
  • soapFaultString → faultString

getSecurityServerHealthData

Changes in the "getSecurityServerHealthData" response:

  • requestMinSoapSize → requestMinSize
  • requestAverageSoapSize → requestAverageSize
  • requestMaxSoapSize → requestMaxSize
  • requestSoapSizeStdDev → requestSizeStdDev
  • responseMinSoapSize → responseMinSize
  • responseAverageSoapSize → responseAverageSize
  • responseMaxSoapSize → responseMaxSize
  • responseSoapSizeStdDev → responseSizeStdDev

JMX

Changes in the JMX metrics:

  • requestSoapSize → requestSize
  • responseSoapSize → responseSize
  • serviceType → this new field is returned with possible values WSDL, REST, OPENAPI3


This is a major update to operational monitoring protocol (0.x → 1.0) which breaks compatibility with the previous version. The protocol is defined in the following documents:

XRDDEV-559New

Add new UI and management API package (xroad-proxy-ui-api) to the Security Server packaging. Remove the old UI package (xroad-jetty) and Nginx package (xroad-nginx) from the packaging.

During the Security Server version upgrade to version 6.24.0 the old UI's TLS key and certificate are migrated to the new UI.

SELinux configuration changes are removed from RHEL installations.

Log files

Removed log files and directories:

  • /var/log/xroad/jetty/jetty.log
  • /var/log/nginx

New log files:

  • /var/log/xroad/proxy_ui_api.log
  • /var/log/xroad/proxy_ui_api_access.log

Services

Removed services:

  • xroad-jetty
  • nginx

New services:

  • xroad-proxy-ui-api
XRDDEV-591New

Add support for returning Security Server generated error messages in different formats (JSON, XML). Starting from version 6.24.0 the Security Server respects "Accept" header value when providing error responses. The formats application/json, application/xml and text/xml are supported, application/json is the default.

Security Server respects the "Accept" header value only when the error response is generated by the Security Server. Error messages originating from service provider's information system are not converted or transformed - they are returned as-is. In other words, the "Accept" header value is not respected when the error response is not generated by the Security Server.

XRDDEV-595ImprovementReplace "-" characters with "_" in ansible scripts to fix deprecation warnings.
XRDDEV-608Fix

Fix a problem that caused WSDL validation to return warnings as errors that cannot be ignored.

WSDL validation may return warnings that can be ignored and errors that cannot be ignored. The problem caused warnings to be interpreted as errors with the result that warnings caused WSDL validation to fail without the possibility to ignore them.

XRDDEV-700Improvement

Optimize serverconf caching and access rights evaluation. Before version 6.24.0 service access rights were fetched from database separately for every incoming request. Starting from version 6.24.0 the access rights are fetched from the database periodically and cached for 60 seconds by default. Therefore, changes in the service access rights not applied immediately, but within 60 seconds from the change.

Access rights and other frequently accessed server configurations are now cached (by default for 60 seconds). Due to this, changes in the access rights are not applied immediately.

XRDDEV-712ImprovementUpdate Ansible scripts to support Ubuntu 18 minimal OS.
XRDDEV-728FixRemove old, unused RHEL7 port forwarding scripts and all references to these scripts from RHEL7 packaging.
XRDDEV-739Improvement

Clarify documentation related to downloading service descriptions.

Updated documentation can be found here, here and here.

XRDDEV-745FixFix a problem that caused rsyslog and nginx configuration changes not to be applied on fresh RHEL install without restarting rsyslogd and nginx.
XRDDEV-747ImprovementImprove configurability by splitting nginx default-xroad.conf so that it can be updated independently for Central Server and Security Server.
XRDDEV-752ImprovementUpdate Akka to version 2.6.
XRDDEV-773New

Update ansible scripts to allow the Central Server to be installed with a remote database.

More information can be found here.

XRDDEV-805Improvement

Improve security and configurability by moving Security Server DB tables to a separate schema instead of using the default "public" schema, so that maintenance does not require super-user rights. The change also enables user defined database names and users which makes it possible to host several databases in the same PostgreSQL cluster (instance). Before version 6.24.0, database names and users were hard-coded which prevented sharing the same PostgreSQL cluster among multiple Security Servers.

When upgrading to version 6.24.0, the serverconf database schema is renamed and the migration requires that installer can access the database using administrative permissions. In case sufficient permissions are not available, the upgrade will fail and some manual steps are needed. The manual steps are documented here.

Please note, that messagelog and opmonitor schemas are not renamed during an upgrade. Instead, new installations will use separate schemas.

(warning) Backups taken from a previous version are not compatible with version 6.24. After a successful upgrade, take a backup of the system configuration.

XRDDEV-807Improvement

Improve security by moving Central Server DB tables to a separate schema instead of using the default "public" schema, so that maintenance does not require super-user rights.

(warning) Backups taken from a previous version are not compatible with version 6.24. After a successful upgrade, take a backup of the system configuration.
(warning) If upgrading a system that still uses central server HA cluster with BDR 1.0, additional manual steps are required:

  • Before the upgrade, take a backup of the system configuration and database.
  • After the upgrade, it is necessary to manually migrate from the public schema to the new mechanism or restoring a configuration backup won't work. The migration causes some downtime.
    • Verify that the database is running on all nodes and that the cluster is fully operational (all nodes see all other nodes and replication is working).

    • Stop xroad-jetty on all cluster nodes.

    • On one cluster node, execute the following command:

      sudo /usr/share/xroad/scripts/rename_public_schema.sh
    • Modify /etc/xroad/db.properties on all nodes as instructed by the script.
    • Start xroad-jetty processes on the cluster nodes.
  • The migration does not delete or modify the contents of the public database schema, so in case of failure one just needs to check that /etc/xroad/db.properties contains the line.
    schema = public
    And start xroad-jetty service. Only database restore functionality is affected, otherwise the cluster continues to function.
XRDDEV-814ImprovementUpdate license in source code file headers.
XRDDEV-822Improvement

Make the Security Server listen to connections from client information systems only on localhost when the Estonian meta package is installed.

Only new installations are affected by the change. Existing installations continue to listen connections on the same interfaces than before the upgrade to version 6.24.0.

To enable connections from outside of localhost on new installations, the default configuration must be overridden in the  "/etc/xroad/conf.d/local.ini" configuration file.

This applies to xroad-securityserver-ee package only. The vanilla version and other country specific versions are not affected.

XRDDEV-825ImprovementRemove the deprecated HTTP GET metaservice interface for fetching WSDL descriptions. Starting from version 6.24.0 the "getWsdl" metaservice is available through the HTTP POST metaservice interface only.
XRDDEV-826Improvement

Add validation of X-Road identifiers for restricted characters when identifiers are added or modified using the Security Server REST management API.

Check the warning listed below for ticket XRDDEV-827 listing new rules that are applied for X-Road identifiers.

XRDDEV-827Improvement

Add validation of X-Road identifiers for restricted characters when identifiers are added or modified on the Central Server, during management request processing on the Central Server and during message processing on the Security Server:

  • Central Server UI validates user inputted identifiers.
  • Management services check that incoming identifiers do not contain invalid characters.
  • Client proxy checks the incoming identifiers in SOAP and REST messages and in case there is a non-conforming identifier creates a warning in application logs.

Restricted characters are:

  • ISO control characters (U+0000 - U+001F, U+007F - U+009F)
  • Zero-width spaces (U+200B, U+FEFF)
  • colon, semicolon, slash, backslash, percent

The restricted characters are applied to the following identifiers:

  • member code
  • subsystem code
  • service code (REST)
  • service code & service version (SOAP)
  • instance id
  • member class
  • security server code
  • central service


If there are invalid identifiers in messages going through the Security Server it may produce lots of warnings in the logs files (depending on the amount of traffic).

XRDDEV-828Improvement

Add support for configuring database super-user name for the Security Server and Central Server.

Before version 6.24.0 the Central Server and Security Server used a hard-coded database super-user "postgres". However, some environments / platforms use other super-user name which made the installation fail. Starting from version 6.24.0 is is possible to configure the database super-user name in xroad.properties file.

XRDDEV-874ImprovementImprove Central Server HA migration guides here and here.
XRDDEV-911NewCreate Security Server installation packages for Red Hat Enterprise Linux 8 (RHEL8).
XRDDEV-913FixFix a problem that caused xroad-opmonitor standalone installation fail on Ubuntu 18.
XRDDEV-925ImprovementImplement ordering of the configured TSA providers on the Security Server so that the same ordering is used by the Security Server management REST API, UI and proxy in message processing. Before version 6.24.0 the ordering of TSA providers wasn't explicitly defined and the ordering may have varied between different Security Server components. Starting from version 6.24.0 all the Security Server components use the same ordering.
XRDDEV-972Improvement

Document manually upgrading the Security Server DB schema to 6.24 in case the automated process fails.

The documentation is available here.

XRDDEV-999FixUpdate Rake version to 13.0.1.
XRDDEV-1010Fix

Fix a problem that caused the operational monitoring getSecurityServerOperationalData response json file to contain responses which were not made by the requesting client. The problem occurred only with result sets exceeding the max-records-in-payload (10000 by default) limit.

XRDDEV-1011ImprovementAdd summary output to HA cluster status check in Central Server system status API. The summary status is presented by the "all_nodes_ok" property, and it's value is true if the status of all nodes is "OK" and false otherwise.
XRDDEV-1017ImprovementMake signer client recover faster from signer connection failures to avoid long hanging connections. When connection is lost, signer client tries to re-establish the connection as soon as possible. Signer client is used by other X-Road modules (e.g., proxy, proxy-ui-api) that need to connect to signer.
XRDDEV-1021FixUpdate jackson-databind version to 2.10.3.
XRDDEV-1123ImprovementRemove unnecessary OCSP fetching of root certificates when Security Server diagnostics information is accessed. Before version 6.24.0 accessing the Security Server diagnostics information caused an error in the signer log, because fetching of root certificates was attempted. Starting from version 6.24.0 accessing the Security Server diagnostics information does not cause false error messages in the logs.
XRDDEV-1156FixImprove security by making rsyslog listen for connections on localhost only by default. Before version 6.24.0 rsyslog listened for connections on all interfaces by default.
XRDDEV-1157ImprovementPublish X-Road release repository sign key on key servers maintained by a trusted third party (SKS key servers) for improved trust. Add X-Road release repository sign key details to installation guides.
XRDDEV-1159Improvement

Improve security by disabling Security Server JMX interfaces by default.

The change affects all existing and new Security Server installations. Before the change, the operational monitoring JMX interface was enabled by default and listened on all available interfaces. After the change, the operational monitoring JMX interface is disabled by default. In case it was utlised, the interface must be manually enabled after the upgrade. Instructions how to enable JMX have been added to the documentation.

Environmental monitoring JMX interface was already disabled by default. Users utilising environmental monitoring JMX interface are not affected by this change.

XRDDEV-1160Improvement

Improve security by auto generating the default password for Central Server database user "centerui" during installation process.

This password is only generated for fresh installations. Upgrades remain unaffected.

XRDDEV-1161ImprovementTurn message body logging off on the Security Server for the Icelandic Security Server meta package ("xroad-securityserver-is").
XRDDEV-1173Improvement

Enable enforcing token PIN policy in the Estonian meta package. After the change the token PIN policy is enforced when "xroad-securityserver-ee" package is installed.

Software token pin is required to be at least 10 ASCII characters from at least tree character classes:

  • lowercase letters
  • uppercase letters
  • digits
  • special characters
XRDDEV-1180ImprovementAdd more detailed instructions on required network configuration in the Security Server installation guides.
XRDDEV-1181FixUpgrade dependencies jackson-databind and cxf-tools-validator.
XRDDEV-1201ImprovementImprove security by unifying file permissions on Security Server RHEL installations. After the change all the X-Road executables are owned by the root user. The xroad user has read and execute permissions.
XRDDEV-1207FixUpdate the Icelandic certificate profile.
XRDDEV-1209NewAdd Security Server meta package ("xroad-securityserver-fo") and certificate profile for the Faroe Islands.
XRDDEV-1281FixRemove an unused secret token from the Central Server's code base.
-NewThe issues related to the new Security Server admin UI and API are listed here.

Issue types: fix (bug fix or technical debt), improvement (improvement to an existing feature), new (a new feature).

New/Updated Dependencies

DependencyOld VersionNew VersionNotes
rake12.0.013.0.1

Fixes

jackson-databind2.9.10.22.10.3

Fixes

akka2.4.202.6.7New logging functionality
spring-boot
2.2.8Added with new UI
spring-framework
5.2.7Added with new UI
spring-boot-starter-security
2.2.8Added with new UI
spring-boot-starter-web
2.2.8Added with new UI
spring-boot-starter-actuator
2.2.8Added with new UI
spring-boot-starter-data-jpa
2.2.8Added with new UI
spring-boot-starter-cache
2.2.8Added with new UI
spring-cloud-starter-sleuth
2.2.2Added with new UI
libpam4j
1.11Added with new UI
commons-compress
1.20Added with new UI
wsdl4j
1.6.3Added with new UI
bucket4j
4.10.0Added with new UI
swagger-parser
2.0.20Added with new UI
openapi-generator
4.2.0Added with new UI
tomcat
9.0.37Added with new UI
hibernate
5.3.10Added with new UI
hikaricp
3.2.0Added with new UI

Contributors

The following developers have contributed to the development of this release version. A contribution means at least one Git commit that is included in the release. The full list of contributors of different X-Road® versions is available here.

GitHub Username
bertvi
carohauta
guycalledguy
iluwatar
jansu76
jhyoty
lakoutan
martensoo
nanndoj
olliru
petkivim
raits
Riippi
samueljon
TJaakkola

Other Notes

Package Repositories

RepositoryURL
Bionic
deb https://artifactory.niis.org/xroad-release-deb bionic-<version> main
RPM / RHEL7
https://artifactory.niis.org/xroad-release-rpm/rhel/7/<version>
RPM / RHEL8
https://artifactory.niis.org/xroad-release-rpm/rhel/8/<version>

Repository Sign Key Details

Download URLhttps://artifactory.niis.org/api/gpg/key/public
Hash935CC5E7FA5397B171749F80D6E3973B
FingerprintA01B FE41 B9D8 EAF4 872F A3F1 FB0D 532C 10F6 EC5B
3rd party key serverSKS key servers

Packages

Bionic

Package

SHA256 checksum

xroad-addon-hwtokens_6.24.0-1.ubuntu18.04_all.deb

81f1a5a0e888342e14d93ef1a8f1ac1f4c10d5869449f6a461925854b9bb747d

xroad-addon-messagelog_6.24.0-1.ubuntu18.04_all.deb

3bd124dafcf162fcb74fbaf19c2a4cfea0b9c69064af14158b32454508ea8440

xroad-addon-metaservices_6.24.0-1.ubuntu18.04_all.deb

b50507a3b040244584fc3001e1f896d92b61c98cc25c229f2302b34e51b3c3c7

xroad-addon-opmonitoring_6.24.0-1.ubuntu18.04_all.deb

53ad4c0469d3cfa0cc9b26d1cd4841401ffce8694df6ad678a614050137d97b2

xroad-addon-proxymonitor_6.24.0-1.ubuntu18.04_all.deb

f610677e53e9d9f46cc051bb7eaecb2af4edda40d7833cdd8afeab35d51a078b

xroad-addon-wsdlvalidator_6.24.0-1.ubuntu18.04_all.deb

41a9b8e8b1c17bfa827ea48453ccbc8c64e1fe548e39d61df62e36a8f850df73

xroad-base_6.24.0-1.ubuntu18.04_amd64.deb

79833e2be41e9bb869874a1dcaafbc62e1cfca2e5996bdfdff299597bee95af4

xroad-autologin_6.24.0-1.ubuntu18.04_all.deb

c80fb2db956f3be8dfe74e8b12afb55a0b41c12f9c7b2b279645f5addb29a1fd

xroad-center_6.24.0-1.ubuntu18.04_all.deb

d51e6c31ccb756c890ebef434b38f2a71f6fc19bf9fd4b9072c23d1dcb0ed204

xroad-centralserver_6.24.0-1.ubuntu18.04_all.deb

8cc1c462e11bf79e9509678c26ff01dac01c24154a86a88ac26b562f4fdf17af

xroad-center-clusterhelper_6.24.0-1.ubuntu18.04_all.deb

7c81cf0f6c8e9e572eca6915bfb57e10678d09381a68235b28e74a7659e0e257

xroad-centralserver-monitoring_6.24.0-1.ubuntu18.04_all.deb

bc27e78360323af43974176e20430081639486ef7fd4698f7f39680d3c85895f

xroad-confclient_6.24.0-1.ubuntu18.04_amd64.deb

f3150b415128adfe8528973a957f92a96c2e1463072554d9f073e7a6597f01d9

xroad-confproxy_6.24.0-1.ubuntu18.04_all.deb

e99060357a23e4ca1f89ced1cd81447ab39595efb45ddb67edd05f1499594767

xroad-jetty9_6.24.0-1.ubuntu18.04_all.deb

d7c8768e1edbca2c33b2e94d424e349c152f89d5ad8771be8490ce3cea3b2cee

xroad-monitor_6.24.0-1.ubuntu18.04_all.deb

a59e39e81536b883553762bec42a96e4f3386931a19bf8e0b18af3aae583f875

xroad-nginx_6.24.0-1.ubuntu18.04_amd64.deb

1fee0b620b28502dc12f8e8764eeb5f4d926fda6f2658c618f0c950d3d2e369f

xroad-opmonitor_6.24.0-1.ubuntu18.04_all.deb

e65d634d9ec15e46020f6bc46eb965e40374f7793c3e02c69d6e38f8927d44a8

xroad-proxy_6.24.0-1.ubuntu18.04_all.deb

59032057bab6251fd0941de458c65cddcc1cffca5eafe4b01318b289cb027574

xroad-proxy-ui-api_6.24.0-1.ubuntu18.04_all.deb

1d564af462aa4c6dd6ef44f9d2a735e86aa09139dbea911bdc413de0160b8e8a

xroad-securityserver_6.24.0-1.ubuntu18.04_all.deb

2f18ecc90166d57b79e92f975d6ac697dbe61c60793c5d099047094adffdfb96

xroad-securityserver-ee_6.24.0-1.ubuntu18.04_all.deb

23f158a4afef6e32a35a89d64f9458852b87d63f9edf8c2361407cbe6fc1c15a

xroad-securityserver-fi_6.24.0-1.ubuntu18.04_all.deb

2ba097c785a39388d353955b3ba0fb15a37cab4ee29ec29648640b39947aee57

xroad-securityserver-fo_6.24.0-1.ubuntu18.04_all.deb

96aa03c36c3e37c736b8f2a1e3ef8292dd45de9878375a4a4fc1a3b892bbcaa8

xroad-securityserver-is_6.24.0-1.ubuntu18.04_all.deb

a892cc62fd59782e14da567b254cb366d85d5b0fd75a84cb8319dc1e85ac96fe

xroad-signer_6.24.0-1.ubuntu18.04_amd64.deb

07fc40aaa60f771f0e4144f9c91128bb1575c87f94e8b7dbf47b373ec238ca45

RPM / RHEL7

Package

SHA256 checksum

xroad-addon-messagelog-6.24.0-1.el7.x86_64.rpm

25f573487e79ed4a554ccd25db1d67e13ae0dc2ce73958441edb8fbac1d11eed

xroad-addon-metaservices-6.24.0-1.el7.x86_64.rpm

ead856386fc07c6546fe010a69381eade470b891eb8733870e691e7e12a6b1b4

xroad-addon-opmonitoring-6.24.0-1.el7.x86_64.rpm

b32af70555fa51f9cd6df6a8da75bd72d306565d5a23d7808e3622866847c2e8

xroad-addon-proxymonitor-6.24.0-1.el7.x86_64.rpm

097c7401c37d88a10f56bfd259b13483cffa1f2b7b5a47deaf8277dac447c4de

xroad-addon-wsdlvalidator-6.24.0-1.el7.x86_64.rpm

efb49e845624823e3e9b9a70aa91d21bb94fe3983eaf576d2df74ed8785eba4a

xroad-autologin-6.24.0-1.el7.noarch.rpm

3bd60ad9d119a343b52c80a9997778461959ba46bfb556f91279f18d7d20e69b

xroad-base-6.24.0-1.el7.x86_64.rpm

587da9d84f0181d1addf67c6d62dce24373df2efc5b184974becead09e4b5628

xroad-common-6.24.0-1.el7.x86_64.rpm

81a929e4c1b0d178fcbfbb7e3439be5be1ae846687c9ddc30b6e68ccaf8c8aab

xroad-confclient-6.24.0-1.el7.x86_64.rpm

1e9848c0aa3be192823560d1498e686d616cd5263976548f4c003badc35d0f63

xroad-jetty9-6.24.0-1.el7.x86_64.rpm

ccfcb6726190b33b690b511252782e1892e2ea889ecdc20aaad259b709e56ccf

xroad-monitor-6.24.0-1.el7.x86_64.rpm

1b49f41fe7ae0716ce246bc458c94ad2ca3777d255b369e814c235eb4bd22d76

xroad-nginx-6.24.0-1.el7.x86_64.rpm

bc868bb9a2bf053c2b9c5b27048a6ef3aa03063d0a20c6eaf10dc6a0bcdf0cd6

xroad-opmonitor-6.24.0-1.el7.x86_64.rpm

a752addde9be9b76e31811fdcb11f11416c135cf3fd61aca754f223a6c7f046b

xroad-proxy-6.24.0-1.el7.x86_64.rpm

7252c68ba26113747dd33ab307c3890a013f200f6c42f72bc50ca485cf025be3

xroad-proxy-ui-api-6.24.0-1.el7.x86_64.rpm

2ea9b78003170314b7b6b2471ef287cd5d4cf3a90b368cd52425afea853b12db

xroad-securityserver-6.24.0-1.el7.noarch.rpm

aeccf0be895fc40c0bf19b84b707b9a8f8d6c81f40310ecb5740a42a6327a5f9

xroad-securityserver-fi-6.24.0-1.el7.noarch.rpm

4aa5b75fbba1b3a3048f4293b7e61069d6b838baf1b8b2ba917d924486053e30

xroad-securityserver-fo-6.24.0-1.el7.noarch.rpm

fa87f602e3cfd39dcf9a75663001c2fae0ca7f4642256139ca8f1295ba3284ff

xroad-securityserver-is-6.24.0-1.el7.noarch.rpm

1e2e5f00a6495f098287f61c3ba6cfc2ff782dcd74e5af6bcd824d50cb1e3ab1

xroad-signer-6.24.0-1.el7.x86_64.rpm

79f639a1a40c3502bc2a05c6cada0f14a4615d4a1c74b105b48041854c118388

RPM / RHEL8

Package

SHA256 checksum

xroad-addon-messagelog-6.24.0-1.el8.x86_64.rpm

8664685211d4e3ef6c14b5aa6be3ccb12b3af8da952f77a0e430ac6f7f279c9c

xroad-addon-metaservices-6.24.0-1.el8.x86_64.rpm

fab2fc0a6ddd6f36879d6b5f040ee67781017fef2ebcbcb05fc738ecfe30e2b2

xroad-addon-opmonitoring-6.24.0-1.el8.x86_64.rpm

fce492254b48d3fe227258887b1606a8b73d567c11f6e7e98ee204ec82c1cb99

xroad-addon-proxymonitor-6.24.0-1.el8.x86_64.rpm

1c10f29a3ac76660accf4c3c7d6b893f919ed16d13d71aee1ab58cd0d4380e06

xroad-addon-wsdlvalidator-6.24.0-1.el8.x86_64.rpm

04c5ccfe1033007819ab507e232658294b8e98fb3d7e51f14a811a81584f6b22

xroad-autologin-6.24.0-1.el8.noarch.rpm

0204a8d4535db5eedf26e419f32f1682558c24135ecfae9d7b716d6866bf10f7

xroad-base-6.24.0-1.el8.x86_64.rpm

d8d1d6ae917dec06e41497b5f34c1a27aa725719cb3e5fa364db6726e6b80c92

xroad-common-6.24.0-1.el8.x86_64.rpm

ce7ffa6e06ce3a296029f02b336cd35eb2a3c5c41c2c8583d1b90bf35c140c82

xroad-confclient-6.24.0-1.el8.x86_64.rpm

a2141550b56ceef38e33ddd6c075115b7f12beb8147be2bdd7a1abe3894813b7

xroad-jetty9-6.24.0-1.el8.x86_64.rpm

3074078a9eb433930faa3fb9b088f8bcf259cff7f8f5620058a04e0a3cbc760f

xroad-monitor-6.24.0-1.el8.x86_64.rpm

d828b4591df5cf40073afa0abceb0e2b09ce6d0605e788965a67cca3afef600e

xroad-nginx-6.24.0-1.el8.x86_64.rpm

a22f396f27176032484d289a5758e30c84cfbfc5651949e54ef50f5feb66bf9d

xroad-opmonitor-6.24.0-1.el8.x86_64.rpm

feb93a646c6b84801bb5e7e6b7c7b8dc86d6c37a8256eab2609fd324e653fea6

xroad-proxy-6.24.0-1.el8.x86_64.rpm

882ff3e49f44382c70a34385f5db4aa876cd5ffa6a5488ff7705b8cd9f0af8fc

xroad-proxy-ui-api-6.24.0-1.el8.x86_64.rpm

f87b39a6f65a0631f326b76dca5d5686fc31f348af4553b5adaf73f291d4b343

xroad-securityserver-6.24.0-1.el8.noarch.rpm

8d90fd1b71e1db22be10440916e75891258817957e9b924f9539c587a85baf47

xroad-securityserver-fi-6.24.0-1.el8.noarch.rpm

987297e6272678e086e1c97e32257efc9a868443bdd50790d5dfe76524a00086

xroad-securityserver-fo-6.24.0-1.el8.noarch.rpm

41f5f7926944d9de2b06299a916f458fbbd31df43102a72f1eb88f3a7bb1242d

xroad-securityserver-is-6.24.0-1.el8.noarch.rpm

a07a3acb1ec528f712f40035ca2e87ac3863dde74e9aebadfcb8a3780e0eb80d

xroad-signer-6.24.0-1.el8.x86_64.rpm

173594e5bdbea8a20b84fcfcc12cee9284fd6ff1b4763fc4c06c898653ecfcb1