Answers.Body: <p>From my understanding, this has a lot more to do with your web server and the cypher suites that are configured than it does with CiviCRM directly.  SSLLabs has a great page on getting all of that set up.</p>
  
  <p><a href="https://www.ssllabs.com/index.html" rel="nofollow">https://www.ssllabs.com/index.html</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-25T22:12:10.150Z
Answers.LastActivityDate: 2016-02-25T22:12:10.150Z
Answers.UserDisplayName: G H
Answers.Body: <p>you can see more details about this at: <a href="https://civicrm.org/blog/yashodha/are-you-ready-for-tls-12-update-cant-escape-it" rel="nofollow noreferrer">https://civicrm.org/blog/yashodha/are-you-ready-for-tls-12-update-cant-escape-it</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-27T03:14:19.913Z
Answers.LastActivityDate: 2018-01-27T03:14:19.913Z
Answers.UserDisplayName: ericG
Body: <p>Lately I have received email stating that a few things are changing in Authorize.net payment. Among a few items (changing urls, longer ids, tls 1.1 force etc) one is:</p>
  
  <blockquote>
    <p><strong>RC4 Cipher Disablement</strong> 
    In an effort to ensure that all of your server-to-server communications with the Authorize.Net platform (both
    transactional and otherwise) maintain the highest levels of security,
    we will be disabling the RC4 cipher suite during the first half of
    2016. A follow-up notification will be sent out once specific dates for the disablement are ready for the sandbox and production
    environments. </p>
    
    <p>For now, if you have a solution that relies on RC4 to communicate with
    our servers, please update it to a current, high-security cipher as
    soon as possible. Please review our API best practices blog post for
    more information.</p>
  </blockquote>
  
  <p>I haven't been able to find anything mentioning rc4 in civicrm authorize.net payment processor. Does anyone know if this relates to CiviCRM?</p>
  
Tags: <civicontribute><contributions><authorize.net>
Title: How does last authorize.net changes refer to CiviCRM
ThreadText: # How does last authorize.net changes refer to CiviCRM
  
  (Asked by: username_0 on 2016-02-23)
  
  Lately I have received email stating that a few things are changing in Authorize.net payment. Among a few items (changing urls, longer ids, tls 1.1 force etc) one is:
  
  > **RC4 Cipher Disablement**
  > In an effort to ensure that all of your server-to-server communications with the Authorize.Net platform (both
  > transactional and otherwise) maintain the highest levels of security,
  > we will be disabling the RC4 cipher suite during the first half of
  > 2016. A follow-up notification will be sent out once specific dates for the disablement are ready for the sandbox and production
  > environments.
  >
  > For now, if you have a solution that relies on RC4 to communicate with
  > our servers, please update it to a current, high-security cipher as
  > soon as possible. Please review our API best practices blog post for
  > more information.
  
  I haven't been able to find anything mentioning rc4 in civicrm authorize.net payment processor. Does anyone know if this relates to CiviCRM?
  
  **Tags:** civicontribute, contributions, authorize.net
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2016-02-25. Score: 2 | Accepted answer
  
  From my understanding, this has a lot more to do with your web server and the cypher suites that are configured than it does with CiviCRM directly. SSLLabs has a great page on getting all of that set up.
  
  <https://www.ssllabs.com/index.html>
  
  
  ---
  
  ### Answer by username_2 on 2018-01-27. Score: 0
  
  you can see more details about this at: <https://civicrm.org/blog/yashodha/are-you-ready-for-tls-12-update-cant-escape-it>
  
  
  ---
  
  