mendelson OFTP2 opensource b51 released

1
min read
A- A+
read
mendelson opensource OFTP2

Please download the new version at https://mendelson-e-c.com/opensource

What is new

*The OFTP2 extensions according to the OFTP2 Implementation Guideline v3.1 have
been implemented. This includes primarily the following points: TLSv1.3 support,
new Cipher Suite 07 AES_256_CBC RSA_PKCS1_15 SHA3-512
*For incoming requests for data transfer, the following rejection messages have been added:
SFNAREAS='15' (Cipher suite not supported),
SFNAREAS='18' (Compression not allowed)
*The system now supports the additional languages Spanish, Italian, French, and Portuguese. The language can either be
set manually (command line parameter, client settings) or automatically detected by the system if this language
is selected in your OS.
*Most checkboxes have been replaced by toggle switches
*A High Contrast Mode is now available, which can be enabled in the client settings
*The connection graph in the partner management section has been extended with the options "Do not connect" and "Poll"
*Configuration Check: The following checks have been added: Number of file handles, sufficient memory availability
*Certificate Manager: The entire certificate chain of a certificate can now be exported as PEM in one step
*Certificate Manager: When exporting/importing a private key (pkcs#12), the entire certificate chain can now optionally
be exported/imported as well
*Certificate Manager: Private keys can now also be exported as PEM
*Certificate Manager: A check for the Certificate Revocation List (CRL) is now possible

Solved problems

*The expiration time of a transaction was calculated from the creation date - it should have been calculated from the sending date
*Certificate Manager: A CSR could not be generated for EC keys
*Certificate Manager: Some keys were displayed as valid but marked in red
*Certificate Manager: Sometimes certificates could not be deleted even though they were set but not in use
*Certificate Manager: The copy function between certificate managers copied keys but not certificates
*No SFNA was thrown for incoming data transfer requests if the incoming SFID identifier already existed as "VFN VFD VFT"
*Encryption/Signature certificates were not updated for incoming connections. As a result, there were occasional
issues where incoming connections were based on the previous certificate management state after certificate changes

Updated/new software packages

*Update to Bouncycastle v180 (Crypto API)
*Update to Lucene 9.11.0 (indexing of system events)
*Update to MINA 2.2.4 (client-server interface)
*Update to HSQLDB 2.74
*Update to Hikari 6.2.1 (Database pool)
*Update to Batik 1.18 (SVG icons)