IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

truststore size & SSL handshake size

  • 1.  truststore size & SSL handshake size

    Posted Fri May 20, 2016 01:26 AM

    Hello,

    We use wM9.7 version and want to know if there is any threshold for SSL handshake size? We have observed that whenever the SSL handshake size increases above 16k bytes, we see SSL errors(SSL handshake failed or trading partners receive error that they are unable to reach our Web servers). I’m trying to find out the relation between the truststore size and SSL handshake. Can anyone help me on this topic.

    Thanks in Advance,
    Victor


    #webMethods
    #Integration-Server-and-ESB


  • 2.  RE: truststore size & SSL handshake size

    Posted Fri May 20, 2016 05:19 PM

    This is the detail about this 16K limit:
    The SSL specification requires fragmentation of data greater than 16k (2^14 = 16384 = 16k) during SSL handshake:
    http://www.ietf.org/rfc/rfc2246.txt (section 6.2.1):
    “The record layer fragments information blocks into TLSPlaintext
    records carrying data in chunks of 2^14 bytes or less. Client message
    boundaries are not preserved in the record layer (i.e., multiple
    client messages of the same ContentType may be coalesced into a
    single TLSPlaintext record, or a single message may be fragmented
    across several records).” What this means is that if any single part of the SSL handshake (ie either party’s x509 certificate, or the server’s TrustedCAsList string, etc) is larger than 16k, fragmentation will occur at one endpoint, and the other endpoint will need to re-assemble/defragment.
    Some old security lib/provider had a bug in their code that it didn’t do this fragmenting/defragmenting properly. Such system will only expect one fragment during the SSL handshake. When the returning message has more than one fragment, it will stop reading the 2nd fragment and throw EOF (end of file) error message.

    if your client is using username/password authentication, you can just open a username/password only port, it won’t return the whole list of trusted CA during handshake, so you won’t have this issue.

    You can also suggest your client to upgrade their system, it’s very old and outdated.


    #Integration-Server-and-ESB
    #webMethods


  • 3.  RE: truststore size & SSL handshake size

    Posted Fri May 20, 2016 05:51 PM

    Now that makes perfect sense! Thanks Tong Wang!


    #webMethods
    #Integration-Server-and-ESB