Quantcast
Channel: Symantec Connect - Endpoint Management - Articles
Viewing all articles
Browse latest Browse all 706

SMP Agent for Mac 8.0 - SSL, TLS, Key Exchange & Cipher Information

$
0
0

The following charts show test results for various configurations of SSL, TLS, Key Exchange and Cipher settings in IIS for SMP Agent for Mac communication with the SMP server. 

While it would be impossible to test every combination, there are several obvious combinations that were tested. The following conditions apply: 

  • All SSL, TLS, Key Exchange and Cipher configuration changes were done using "IIS Crypto 2.0". A reboot of the SMP VM was done after each change. 
  • The SMP virtual machine is running Windows Server 2012 R2 Standard. 
  • The Mac client is running OS X 10.12.1 and the SMP Agent for Mac version 8.0.3311.
  • Communication was tested on the client by running 'aex-refreshpolicies' in the Terminal.app. 

The following table shows test results for when the NS is NOT configured to use SSL. It is HTTP only. The default <servername> certificate is bound to port 443. The client is configured to use HTTPS (the agent will fallback to http):

SSL & TLS   ResultNotes
SSL AllTLS AllKey Exchanges: ALLCiphers: ALLSuccessful 
SSL AllTLS NoneKey Exchanges: ALLCiphers: ALLFailed 
SSL NoneTLS AllKey Exchanges: ALLCiphers: ALLFailed 
SSL AllTLS 1.0Key Exchanges: ALLCiphers: ALLSuccessful 
SSL AllTLS 1.1Key Exchanges: ALLCiphers: ALLSuccessful 
SSL AllTLS 1.2Key Exchanges: ALLCiphers: ALLSuccessful 
SSL 2.0TLS AllKey Exchanges: ALLCiphers: ALLSuccessful 
SSL 2.0TLS 1.0Key Exchanges: ALLCiphers: ALLSuccessful 
SSL 2.0TLS 1.1Key Exchanges: ALLCiphers: ALLFailedSSL 2.0 evidently does not work with TLS 1.1 and 1.2. 
SSL 2.0TLS 1.2Key Exchanges: ALLCiphers: ALLFailedSSL 2.0 evidently does not work with TLS 1.1 and 1.2. 
SSL 3.0TLS AllKey Exchanges: ALLCiphers: ALLSuccessful 
SSL 3.0TLS 1.0Key Exchanges: ALLCiphers: ALLSuccessful 
SSL 3.0TLS 1.1Key Exchanges: ALLCiphers: ALLSuccessful 
SSL 3.0TLS 1.2Key Exchanges: ALLCiphers: ALLSuccessful 
      
Key Exchanges    
SSL AllTLS AllKey Exchanges: NoneCiphers: ALLFailed 
SSL AllTLS AllKey Exchanges:Diffie-Heilman onlyCiphers: ALLSuccessful 
SSL AllTLS AllKey Exchanges:PKCS onlyCiphers: ALLSuccessful 
SSL AllTLS AllKey Exchanges:ECDH onlyCiphers: ALLSuccessful 
      
Ciphers     
SSL AllTLS AllKey Exchanges AllCiphers: NoneSuccessful 

The following table shows test results for when the NS IS configured to require SSL and accept client certificates. The default <servername> certificate is bound to port 443. The client is configured to use HTTPS (the agent will fallback to http):

SSL & TLS   Result 
SSL AllTLS AllKey Exchanges: ALLCiphers: ALLSuccessful 
SSL AllTLS NoneKey Exchanges: ALLCiphers: ALLFailed 
SSL NoneTLS AllKey Exchanges: ALLCiphers: ALLSuccessfulVerified in the registry - no enabled SSL versions. 
SSL AllTLS 1.0Key Exchanges: ALLCiphers: ALLSuccessful 
SSL AllTLS 1.1Key Exchanges: ALLCiphers: ALLSuccessful 
SSL AllTLS 1.2Key Exchanges: ALLCiphers: ALLSuccessful 
SSL 2.0TLS AllKey Exchanges: ALLCiphers: ALLSuccessful 
SSL 2.0TLS 1.0Key Exchanges: ALLCiphers: ALLSuccessful 
SSL 2.0TLS 1.1Key Exchanges: ALLCiphers: ALLFailed 
SSL 2.0TLS 1.2Key Exchanges: ALLCiphers: ALLFailed 
SSL 3.0TLS AllKey Exchanges: ALLCiphers: ALLSuccessful 
SSL 3.0TLS 1.0Key Exchanges: ALLCiphers: ALLSuccessful 
SSL 3.0TLS 1.1Key Exchanges: ALLCiphers: ALLSuccessful 
SSL 3.0TLS 1.2Key Exchanges: ALLCiphers: ALLSuccessful 
      
Key Exchanges    
SSL AllTLS AllKey Exchanges: NoneCiphers: ALLFailed 
SSL AllTLS AllKey Exchanges:Diffie-Heilman onlyCiphers: ALLSuccessful 
SSL AllTLS AllKey Exchanges:PKCS onlyCiphers: ALLSuccessful 
SSL AllTLS AllKey Exchanges:ECDH onlyCiphers: ALLSuccessful 
      
Ciphers     
SSL AllTLS AllKey Exchanges AllCiphers: NoneFailed 

Viewing all articles
Browse latest Browse all 706

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>