Changes between Version 6 and Version 7 of heartbleed


Ignore:
Timestamp:
Apr 9, 2014, 10:28:20 AM (7 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • heartbleed

    v6 v7  
    1414During the period in which our servers were vulnerable it was possible for someone who can access your traffic to compromise the key that encrypts that traffic. If your key was compromised, then fixing the bug is not enough: you'll need to generate a new key and get a new x509 certificate.
    1515
     16''' Action Summary '''
     17
     18What should I do?
     19
     20 * All May First/People Link members are encouraged to change your passwords by going to this web site: https://members.mayfirst.org/changepass
     21 * Please be careful of phishing attacks! Please do not enter your password into any site that does not have the lock icon (or starts with https) and ends with mayfirst.org.
     22 * If you have a web site that uses https and you have purchased a certificate, please [wiki:faq/security/get-certificate generate a new key and obtain a new certificate].
    1623'''Questions'''
    1724
     
    2633''Do I have to generate a new key?''
    2734
    28 No. It's your choice and you may decide that it's not worth the effort. The vulnerability allowed an attacker to read the memory used by the web server. If nobody attempted to exploit the server your web site is running on during the period in which the server was vulnerable, then there is no reason to generate a new key or be worried about compromised data. On the other hand, if someone attempted to exploit ''any'' web site on your server (even if it's not your own web site), then your data may have been compromised.
     35We strongly recomment that you do. However, it's your choice and you may decide that it's not worth the effort. The vulnerability allowed an attacker to read the memory used by the web server. If nobody attempted to exploit the server your web site is running on during the period in which the server was vulnerable, then there is no reason to generate a new key or be worried about compromised data. On the other hand, if someone attempted to exploit ''any'' web site on your server (even if it's not your own web site), then your data may have been compromised. It is trivial to write a simple program to scan web sites for this vulnerability and it's likely that some people knew about the problem prior to it becoming public.
    2936
    3037'''Additional Information and Notes'''