| |
Results |
|
Dim CM: unable to start desktop client, getting a crash pop-up reporting faulting module name is tls9112d.dll
|
Dim CM: unable to start desktop client, getting a crash pop-up reporting faulting module name is tls 9112d.dll
|
|
|
|
DimCM: 14.4: DMDBA: DMDBA on AIX fails with "0509-130 Symbol resolution failed for /var/serena/dimensions/14.4/cm/lib/libtls13212d.a[tls12d.o]" error
|
DimCM: 14.4: DMDBA: DMDBA on AIX fails with "0509-130 Symbol resolution failed for /var/serena/dimensions/14.4/cm/lib/libtls13212d.a[ tls 12d.o]" error
|
|
|
|
CM 14.1.0.4 web client with SSO gets applet errors
|
The terms SSL and TLS are often used interchangeably or in conjunction with each other ( TLS /SSL), but one is in fact the predecessor of the other — SSL 3.0 served as the basis for TLS 1.0 which, as a result, is sometimes referred to as SSL 3.1. Subsequent versions of TLS — v1.1 and v1.2 are significantly more secure and fix many vulnerabilities present in SSL v3.0 and TLS v1.0.
|
|
|
|
2009r2.x : How works DM_FILE_ENCRYPTION ?
|
To get a more secure encryption it is possible to configure the system to use the SSDP (Secure Standard Dimensions) protocol. Encryption will then be provided using TLS version 3.1 using the following cipher suite: TLS _DHE_RSA_WITH_3DES_EDE_CBC_SHA
|
|
|
|
Dim9: Compression of password sent from Desktop Client to the Dimensions 9.1.3 Server
|
For higher security environments Dimensions CM can be configured to encrypt all network traffic using SSL (see the Secure Sockets Layer Support appendix in the Dimensions CM Administrators Guide). When running over SSL the traffic is encrypted using TLS version 3.1 with the following cipher suite:
|
|
|
|
Dim9: Compression of password sent from desktop client to the Dimensions 9.1.3 server
|
For higher security environments Dimensions CM can be configured to encrypt all network traffic using SSL (see the Secure Sockets Layer Support appendix in the Dimensions CM Administrators Guide). When running over SSL the traffic is encrypted usingg TLS version 3.1 with the following cipher suite:
|
|
|
|
DIM CM: CM Bridge download performance on Windows Server 2008
|
<Connector port="8443" SSLEnabled="true" scheme="https" secure="true" sslProtocol=" TLS " sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1" maxHttpHeaderSize="8192"
|
|
|
|
12.x / Tomcat : what about the Nessus security issues 26928 and 42873
|
ciphers="SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS _RSA_WITH_AES_128_CBC_SHA, TLS _DHE_RSA_WITH_AES_128_CBC_SHA, TLS _DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3 ...
|
|
|
|
DimCM: Tomcat: org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header error shows in the Catalina logfile.
|
This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website's owner.
|
|
|
Mitigating POODLE in Dimensions CM.DOCX
|
When clients initiate a secure connection to a server there is a negotiation step involved where they agree on a protocol to use and potentially an encryption algorithm as well. Most connections between modern clients and servers use TLS instead of the outdated SSL. However, in the name of backward compatibility, both clients and servers allow for protocol downgrade for maximum interoperability.
|
|
|
