From be4bfc5feeb61e97378bee325d36bb74f007fe04 Mon Sep 17 00:00:00 2001 From: Kai Koehne Date: Thu, 7 Apr 2016 09:52:29 +0200 Subject: Doc: Add external-resources.qdoc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Also sanitize some linking, e.g. by referencing to the paper by title, not by link. Change-Id: I95482994ca569001a23a3beb0e3cbe6739f4ed77 Reviewed-by: Leena Miettinen Reviewed-by: Topi Reiniö --- src/websockets/qmaskgenerator.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/websockets/qmaskgenerator.cpp') diff --git a/src/websockets/qmaskgenerator.cpp b/src/websockets/qmaskgenerator.cpp index cc53156..88baab6 100644 --- a/src/websockets/qmaskgenerator.cpp +++ b/src/websockets/qmaskgenerator.cpp @@ -39,11 +39,11 @@ \brief The QMaskGenerator class provides an abstract base for custom 32-bit mask generators. - The WebSockets specification as outlined in \l {http://tools.ietf.org/html/rfc6455}{RFC 6455} + The WebSockets specification as outlined in \l {RFC 6455} requires that all communication from client to server be masked. This is to prevent malicious scripts from attacking badly behaving proxies. For more information about the importance of good masking, - see \l {http://w2spconf.com/2011/papers/websocket.pdf}. + see \l {"Talking to Yourself for Fun and Profit" by Lin-Shung Huang et al}. By default QWebSocket uses the cryptographically insecure qrand() function. The best measure against attacks mentioned in the document above, is to use QWebSocket over a secure connection (\e wss://). -- cgit v1.2.1