$30 off During Our Annual Pro Sale. View Details »

The first few milliseconds of HTTPS - phpnz14

Joshua Thijssen
August 28, 2014
140

The first few milliseconds of HTTPS - phpnz14

Joshua Thijssen

August 28, 2014
Tweet

Transcript

  1. The first 200 milliseconds of HTTPS
    1
    Joshua Thijssen
    jaytaph

    View Slide

  2. 2

    View Slide

  3. ➡ What’s happening in the first 200+
    milliseconds in a initial HTTPS connection.
    2

    View Slide

  4. ➡ What’s happening in the first 200+
    milliseconds in a initial HTTPS connection.
    ➡ Give tips and hints on hardening your setup.
    2

    View Slide

  5. ➡ What’s happening in the first 200+
    milliseconds in a initial HTTPS connection.
    ➡ Give tips and hints on hardening your setup.
    ➡ Give you insights in new and upcoming
    technologies.
    2

    View Slide

  6. ➡ What’s happening in the first 200+
    milliseconds in a initial HTTPS connection.
    ➡ Give tips and hints on hardening your setup.
    ➡ Give you insights in new and upcoming
    technologies.
    ➡ Show you things to you (probably) didn’t
    knew.
    2

    View Slide

  7. This talk is inspired by
    a blogpost from Jeff Moser
    http://www.moserware.com/2009/06/first-few-milliseconds-of-https.html
    Unknown fact!
    3

    View Slide

  8. HTTPS ==
    HTTP on top of TLS
    4

    View Slide

  9. Transport Layer Security
    (TLS)
    5

    View Slide

  10. Secure Socket Layer
    (SSL)
    6
    A short and scary history

    View Slide

  11. then
    now
    7

    View Slide

  12. then
    now
    SSL 1.0
    Vaporware
    1994
    7

    View Slide

  13. then
    now
    feb
    1995
    SSL 2.0
    Not-so-secure-socket-layer
    SSL 1.0
    Vaporware
    1994
    7

    View Slide

  14. then
    now
    feb
    1995
    SSL 2.0
    Not-so-secure-socket-layer
    jun
    1996
    SSL 3.0
    Something stable!
    SSL 1.0
    Vaporware
    1994
    7

    View Slide

  15. then
    now
    feb
    1995
    SSL 2.0
    Not-so-secure-socket-layer
    jun
    1996
    SSL 3.0
    Something stable!
    jan
    1999
    TLS 1.0
    SSL 3.1
    SSL 1.0
    Vaporware
    1994
    7

    View Slide

  16. then
    now
    feb
    1995
    SSL 2.0
    Not-so-secure-socket-layer
    jun
    1996
    SSL 3.0
    Something stable!
    jan
    1999
    TLS 1.0
    SSL 3.1
    apr
    2006
    TLS 1.1
    SSL 1.0
    Vaporware
    1994
    7

    View Slide

  17. then
    now
    feb
    1995
    SSL 2.0
    Not-so-secure-socket-layer
    jun
    1996
    SSL 3.0
    Something stable!
    jan
    1999
    TLS 1.0
    SSL 3.1
    apr
    2006
    TLS 1.1
    TLS 1.2
    aug
    2008
    SSL 1.0
    Vaporware
    1994
    7

    View Slide

  18. https://www.trustworthyinternet.org/ssl-pulse/
    25,7%
    99,6% 99,3%
    18,2% 20,7%
    SSL 2.0 SSL 3.0 TLS 1.0 TLS 1.1 TLS 1.2
    8
    November 2013

    View Slide

  19. https://www.trustworthyinternet.org/ssl-pulse/
    25,7%
    99,6% 99,3%
    18,2% 20,7%
    SSL 2.0 SSL 3.0 TLS 1.0 TLS 1.1 TLS 1.2
    8
    20,5%
    98,5% 99,3%
    38,4% 40,8%
    SSL 2.0 SSL 3.0 TLS 1.0 TLS 1.1 TLS 1.2
    November 2013 Aug 2014

    View Slide

  20. RFC 5246
    (TLS v1.2)
    9

    View Slide

  21. 10
    Record Layer

    View Slide

  22. 10
    Record Layer
    Type Version Length

    View Slide

  23. 10
    Record Layer
    Type Version Length
    Protocol

    View Slide

  24. 10
    Record Layer
    Type Version Length
    Protocol
    Protocol
    Protocol

    View Slide

  25. 10
    Record Layer
    Type Version Length
    Protocol
    Protocol
    Protocol
    Record Layer
    Type Version Length
    Protocol

    View Slide

  26. ➡ Handshake protocol records
    ➡ Setup communication
    ➡ Change Cipher Spec protocol records
    ➡ Change communication
    ➡ Alert protocol records
    ➡ Errors
    ➡ Application Data protocol records
    ➡ Actual data transfers
    11

    View Slide

  27. 12
    https://github.com/vincentbernat/rfc5077/blob/master/ssl-handshake.svg

    View Slide

  28. Attention:
    (live)
    wiresharking
    up ahead
    13

    View Slide

  29. 14

    View Slide

  30. 15

    View Slide

  31. Generating
    randomness is HARD
    16

    View Slide

  32. entropy
    (uncertainty)
    17

    View Slide

  33. TIME is NOT random
    thus not a very good
    entropy source
    18

    View Slide

  34. PHP is bad
    when it comes to
    entropy
    19
    Unknown fact!

    View Slide

  35. srand(microtime())
    20
    Unknown fact!

    View Slide

  36. rand()
    mt_rand()
    uniqid()
    21

    View Slide

  37. 22

    View Slide

  38. openssl_pseudo_random_bytes()
    22

    View Slide

  39. openssl_pseudo_random_bytes()
    read from /dev/(u)random
    22

    View Slide

  40. openssl_pseudo_random_bytes()
    read from /dev/(u)random
    Use a HRNG
    22

    View Slide

  41. openssl_pseudo_random_bytes()
    read from /dev/(u)random
    Use a HRNG
    “A million random digits”
    22

    View Slide

  42. openssl_pseudo_random_bytes()
    read from /dev/(u)random
    Use a HRNG
    “A million random digits”
    https://github.com/ircmaxell/RandomLib
    22

    View Slide

  43. 23

    View Slide

  44. TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
    24

    View Slide

  45. TLS
    ECDHE_ECDSA
    WITH
    AES_128_GCM
    SHA256
    25

    View Slide

  46. TLS
    ECDHE_ECDSA
    WITH
    AES_128_GCM
    SHA256
    Cipher for exchanging
    key information
    25

    View Slide

  47. TLS
    ECDHE_ECDSA
    WITH
    AES_128_GCM
    SHA256
    Cipher for exchanging
    key information
    Cipher for
    authenticating key
    information
    25

    View Slide

  48. TLS
    ECDHE_ECDSA
    WITH
    AES_128_GCM
    SHA256
    Cipher for exchanging
    key information
    Cipher for
    authenticating key
    information
    Actual cipher (and
    length) used for
    communication
    25

    View Slide

  49. TLS
    ECDHE_ECDSA
    WITH
    AES_128_GCM
    SHA256
    Cipher for exchanging
    key information
    Cipher for
    authenticating key
    information
    Hash algo for message
    authenticating
    Actual cipher (and
    length) used for
    communication
    25

    View Slide

  50. TLS_RSA_WITH_AES_256_CBC_SHA256
    26

    View Slide

  51. TLS_NULL_WITH_NULL_NULL
    27

    View Slide

  52. Client gives cipher options,
    Server ultimately decides on cipher!
    28

    View Slide

  53. THIS IS WHY YOU SHOULD ALWAYS
    CONFIGURE YOUR CIPHERS
    ON YOUR WEB SERVER!
    29
    Unknown fact!

    View Slide

  54. SSLProtocol all -SSLv2 -SSLv3
    SSLHonorCipherOrder on
    SSLCipherSuite "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 \
    EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 \
    EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS"
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_prefer_server_ciphers on;
    ssl_ciphers "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 \
    EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 \
    EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS";
    Apache
    Nginx
    30
    https://community.qualys.com/blogs/securitylabs/2013/08/05/configuring-apache-nginx-and-openssl-for-forward-secrecy

    View Slide

  55. https://www.ssllabs.com/ssltest/
    31

    View Slide

  56. 32

    View Slide

  57. 33

    View Slide

  58. 34

    View Slide

  59. 35

    View Slide

  60. 36

    View Slide

  61. 37

    View Slide

  62. 38
    New Zealand,

    View Slide

  63. 39

    View Slide

  64. 40
    ➡ SNI (Server Name Indication)
    ➡ Extension 0x0000
    ➡ Pretty much every decent browser /
    server.
    ➡ IE6, Win XP, Blackberry, Android 2.x
    ➡ So no worries!

    View Slide

  65. 41

    View Slide

  66. 42

    View Slide

  67. What an SSL certificate is NOT:
    43
    ➡ SSL certificate (but a X.509 certificate)
    ➡ Automatically secure
    ➡ Automatically trustworthy
    ➡ In any way better self-signed certificates
    ➡ Cheap

    View Slide

  68. What an SSL certificate is:
    44
    ➡ The best way (but not perfect) to prove authenticity
    ➡ A way to bootstrap encrypted communication
    ➡ Misleading
    ➡ (Too) Expensive

    View Slide

  69. 45

    View Slide

  70. 45
    ➡ X.509 Certificate

    View Slide

  71. 45
    ➡ X.509 Certificate
    ➡ Owner info (who is this owner)

    View Slide

  72. 45
    ➡ X.509 Certificate
    ➡ Owner info (who is this owner)
    ➡ Domain info (for which domain(s) is
    this certificate valid)

    View Slide

  73. 45
    ➡ X.509 Certificate
    ➡ Owner info (who is this owner)
    ➡ Domain info (for which domain(s) is
    this certificate valid)
    ➡ Expiry info (from when to when is this
    certificate valid)

    View Slide

  74. 46
    yourdomain.com

    View Slide

  75. 46
    yourdomain.com
    Intermediate
    CA

    View Slide

  76. 46
    yourdomain.com
    Intermediate
    CA

    View Slide

  77. 46
    yourdomain.com
    Root
    CA
    Intermediate
    CA

    View Slide

  78. 46
    yourdomain.com
    Root
    CA
    Intermediate
    CA

    View Slide

  79. 46
    yourdomain.com
    Root
    CA
    Intermediate
    CA

    View Slide

  80. 47
    IMPLIED TRU$T

    View Slide

  81. ➡ (Root) Certificate Authorities
    ➡ They are built into your browser / OS
    and you will automatically trust them.
    48

    View Slide

  82. 49
    wget http://mxr.mozilla.org/mozilla-central/source/security/nss/lib/ckfw/builtins/certdata.txt\?raw\=1 -O - -q | grep Issuer | sort | uniq | wc -l

    View Slide

  83. 49
    wget http://mxr.mozilla.org/mozilla-central/source/security/nss/lib/ckfw/builtins/certdata.txt\?raw\=1 -O - -q | grep Issuer | sort | uniq | wc -l
    181
    And rising...

    View Slide

  84. 50

    View Slide

  85. 50
    ➡ X.509 certificates are used to authenticate
    the server.

    View Slide

  86. 50
    ➡ X.509 certificates are used to authenticate
    the server.
    ➡ Servers can ask clients to authenticate
    themselves as well.

    View Slide

  87. 50
    ➡ X.509 certificates are used to authenticate
    the server.
    ➡ Servers can ask clients to authenticate
    themselves as well.
    ➡ APIs

    View Slide

  88. 51

    View Slide

  89. 52

    View Slide

  90. 53
    Generating secrets:

    View Slide

  91. 53
    pre master secret server rand
    client rand
    Generating secrets:
    + +

    View Slide

  92. 53
    pre master secret server rand
    client rand
    master secret
    Generating secrets:
    + +

    View Slide

  93. 53
    pre master secret server rand
    client rand
    master secret
    master secret server rand client rand
    Generating secrets:
    + +
    +
    +

    View Slide

  94. 53
    pre master secret server rand
    client rand
    master secret
    master secret server rand client rand
    key buffer
    Generating secrets:
    + +
    +
    +

    View Slide

  95. 53
    pre master secret server rand
    client rand
    master secret
    client MAC client KEY client IV server MAC server KEY server IV
    master secret server rand client rand
    key buffer
    Generating secrets:
    + +
    +
    +

    View Slide

  96. https://github.com/jaytaph/TLS-decoder
    54
    http://www.adayinthelifeof.nl/2013/12/30/decoding-tls-with-php/
    Try it yourself, php style:

    View Slide

  97. 55

    View Slide

  98. 56

    View Slide

  99. 57

    View Slide

  100. 58

    View Slide

  101. 59
    Wireshark CAN decrypt your HTTPS traffic
    Unknown fact!
    SSLKEYLOGFILE
    https://isc.sans.edu/forums/diary/Psst+Your+Browser+Knows+All+Your+Secrets+/16415

    View Slide

  102. 60
    launchctl setenv SSLKEYLOGFILE /tmp/keylog.secret
    on a mac:

    View Slide

  103. 61

    View Slide

  104. ➡ TLS has overhead in computation and
    transfers. But definitely worth it.
    ➡ Google likes it.
    ➡ Some ciphersuites are better, but slower.
    ➡ Speed / Security compromise
    ➡ (try: “openssl speed”)
    62

    View Slide

  105. Are we safe yet?
    63

    View Slide

  106. euh,.. no :/
    64

    View Slide

  107. 65
    PRE MASTER
    SECRET

    View Slide

  108. What if somebody*
    got hold of the site
    private key?
    66

    View Slide

  109. 67

    View Slide

  110. 68

    View Slide

  111. 69

    View Slide

  112. 70

    View Slide

  113. (PERFECT)
    FORWARDING
    SECRECY
    71

    View Slide

  114. Compromising the
    pre-master secret does
    not compromise our
    communication.
    72

    View Slide

  115. PFS:
    Can’t compromise
    other keys with a
    compromised key.
    73

    View Slide

  116. Unfortunately..
    74

    View Slide

  117. 75
    PFS needs server
    AND browser support

    View Slide

  118. 76
    http://news.netcraft.com/archives/2013/06/25/ssl-intercepted-today-decrypted-tomorrow.html

    View Slide

  119. 77
    http://news.netcraft.com/archives/2013/06/25/ssl-intercepted-today-decrypted-tomorrow.html

    View Slide

  120. Update your cipher
    suite list and place
    PFS ciphers at the top
    78

    View Slide

  121. But beware:
    heavy computations
    79

    View Slide

  122. 80
    SSL Test
    https://www.ssllabs.com/ssltest/

    View Slide

  123. -ETOOMUCHINFO
    81

    View Slide

  124. 82
    https://www.ssllabs.com/projects/best-practices/index.html

    View Slide

  125. http://farm1.static.flickr.com/73/163450213_18478d3aa6_d.jpg 83

    View Slide

  126. 84
    Find me on twitter: @jaytaph
    Find me for development and training: www.noxlogic.nl
    Find me on email: [email protected]
    Find me for blogs: www.adayinthelifeof.nl

    View Slide