Jump to content

Talk:DROWN attack

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Robwahl (talk | contribs) at 23:21, 12 September 2017 (Background required for non technical users: Added). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Expansion

This stub needs a lot of expansion. But at least it's a start. -- Markshale (talk) 00:51, 2 March 2016 (UTC)[reply]

Background required for non technical users

Hello, this article reveals a recent vulnerability causing use of SSL 2.0 to be discouraged by OpenSSL and others. I think the author should include some material for the less technical user. I would include the following points. I would also expand upon significance

In order to preserve confidentiality, sensitive data must be encrypted. One method of encryption is RSA. RSA was considered to be difficult to break but with newer computers which includes GPUs and multicare to quantum computers it was easier to break. When it was invented people were overconfident in the key size and math complexity and used RSA just to setup a secure socket rather than for all data trsnsmission unless AES is used like it is for media streaming. SSL encrypts data at the transport layer and above and dates from the 1990s. It is used with https traffic. It is also used for local network traffic authentication as well as some VPN traffic which allow remote users to access a network. The predictability of short traffic can cause confidentiality issues. SSL uses RSA encryption. With SSL is not a control for who recieves the public key making it ideal for internet use. Knowing the private way is the only way to decrypt it. The DROWN (decrypting RSA with obsolete and weakened eNcryption) "allows attackers to break the encryption and read or steal sensitive communications, including passwords, credit card numbers, trade secrets, and financial data". To mitegate turn off SSL v2 and make sure private keys are not used as public keys.


TLS uses an RSA algorithm of 1024 and 2048 bits and is the successor to SSL TLS and the downgraded SSL uses the same key generated from multiplying two large prime numbers.

Some older devices are not able to do TLS 1.2 and eliminating SSL v2 trades usability for security. Robwahl (talk) 23:18, 12 September 2017 (UTC)[reply]