you can disable support for the ssl 3.0 protocol on windows by following these steps:
regedit, and then click ok.
|windows server 2003 service pack 2|
|windows server 2003 x64 edition service pack 2|
|windows server 2003 with sp2 for itanium-based systems|
|windows vista service pack 2|
|windows vista x64 edition service pack 2|
|windows server 2008 for 32-bit systems service pack 2|
|windows server 2008 for x64-based systems service pack 2|
|windows server 2008 for itanium-based systems service pack 2|
|windows 7 for 32-bit systems service pack 1|
|windows 7 for x64-based systems service pack 1|
|windows server 2008 r2 for x64-based systems service pack 1|
|windows server 2008 r2 for itanium-based systems service pack 1|
|windows 8 for 32-bit systems|
|windows 8 for x64-based systems|
|windows 8.1 for 32-bit systems|
|windows 8.1 for x64-based systems|
|windows server 2012|
|windows server 2012 r2|
|windows rt 8.1|
|server core installation option|
|windows server 2008 for 32-bit systems service pack 2 (server core installation)|
|windows server 2008 for x64-based systems service pack 2 (server core installation)|
|windows server 2008 r2 for x64-based systems service pack 1 (server core installation)|
|windows server 2012 (server core installation)|
|windows server 2012 r2 (server core installation)|
the ssl protocol 3.0, as used in openssl through 1.0.1i and other products, uses nondeterministic cbc padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, aka the “poodle” issue.
the vulnerability, which is more formally known as cve-2014-0160, allows an attacker to read up to 64 kilobytes of memory per attack on any connected client or server. heartbleed got its name because it is a flaw in openssl’s implementation of the heartbeat extension for the tls and dtls protocols (rfc 6520).
the vulnerability, which is caused by poorly-written code, was discovered on the same day by google and codenomicon security researchers. the researchers quickly realized that an attacker could exploit the bug to exposeencrypted content, usernames, passwords, and private keys for x.509 certificates. because openssl is used by approximately 66% of all activewebsites on the internet, many experts have called heartbleed one of the worst security bugs in the history of the internet.
heartbleed vulnerabilities exist in all versions of openssl released between march 2012 and april 2014, at which time the software defect was corrected and openssl version 1.0.1g was released. to lessen the potential negative effects of heartbleed, openssl.org recommends that enterprises upgrade to the most recent version of openssl and reissue x.509 certificates with new keys.
microsoft is aware of detailed information that has been published describing a new method to exploit a vulnerability in ssl 3.0. this is an industry-wide vulnerability affecting the ssl 3.0 protocol itself and is not specific to the windows operating system. all supported versions of microsoft windows implement this protocol and are affected by this vulnerability. microsoft is not aware of attacks that try to use the reported vulnerability at this time. considering the attack scenario, this vulnerability is not considered high risk to customers.
microsoft is announcing that ssl 3.0 will be disabled in the default configuration of internet explorer and across microsoft online services over the coming months. we recommend customers migrate clients and services to more secure security protocols, such as tls 1.0, tls 1.1 or tls 1.2.
when you're a little too careless about virtualizing your domain controllers, cloning, migrating, backing up and restoring, returning from vacation… Read More
systemd is new service manager for linux. it's a replacement for all previous init systems (sysv/sysvinit & ubuntu's upstart) and… Read More