[Sblim-commit] jsr48-client/src/org/sblim/cimclient WBEMConfigurationProperties.java, 1.17.2.35, 1.17.2.36

[Dave B. <bla...@us...>]

Update of /cvsroot/sblim/jsr48-client/src/org/sblim/cimclient
In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv26938/src/org/sblim/cimclient

Modified Files:
      Tag: Experimental
	WBEMConfigurationProperties.java 
Log Message:
2618 Need to add property to disable weak cipher suites for the secure indication

Index: WBEMConfigurationProperties.java
===================================================================
RCS file: /cvsroot/sblim/jsr48-client/src/org/sblim/cimclient/WBEMConfigurationProperties.java,v
retrieving revision 1.17.2.35
retrieving revision 1.17.2.36
diff -u -d -r1.17.2.35 -r1.17.2.36
--- WBEMConfigurationProperties.java	17 Jan 2013 14:28:15 -0000	1.17.2.35
+++ WBEMConfigurationProperties.java	5 Mar 2013 15:31:06 -0000	1.17.2.36
@@ -43,6 +43,7 @@
  * 3536399    2012-08-25  hellerda     Add client/listener peer authentication properties
  * 3572993    2012-10-01  blaschke-oss parseDouble("2.2250738585072012e-308") DoS vulnerability
  * 3598613    2013-01-11  blaschke-oss different data type in cim instance and cim object path
+ *    2618    2013-02-27  blaschke-oss Need to add property to disable weak cipher suites for the secure indication
  */
 package org.sblim.cimclient;
 
@@ -530,6 +531,17 @@
 	public static final String SSL_LISTENER_PEER_VERIFICATION = "sblim.wbem.sslListenerPeerVerification";
 
 	/**
+	 * The comma-separated list of cipher suites that are to be disabled when
+	 * connecting via an SSL socket. In general, this is the list of cipher
+	 * suites considered "too weak" for use in a particular environment.<br />
+	 * <br />
+	 * Type: <code>String</code><br />
+	 * Recognition: <code>On initialization of a new client/listener</code><br />
+	 * Default: <code>none</code><br />
+	 */
+	public static final String SSL_CIPHER_SUITES_TO_DISABLE = "sblim.wbem.sslCipherSuitesToDisable";
+
+	/**
 	 * Specifies the XML parser for parsing CIM-XML responses.<br />
 	 * The SAX parser is the default choice since it is fast, resource saving
 	 * and interoperable. The streaming algorithm of the PULL parser uses the