Uploaded image for project: 'Qpid Proton'
  1. Qpid Proton
  2. PROTON-992

Proton's use of Cyrus SASL is not thread-safe - short term fix

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • proton-0.10
    • proton-0.13.0
    • proton-c
    • None

    Description

      Documentation for the Cyrus SASL library says that the library is believed to be thread-safe only if the code that uses it meets several requirements.

      The requirements are:

      • you supply mutex functions (see sasl_set_mutex())
      • you make no libsasl calls until sasl_client/server_init() completes
      • no libsasl calls are made after sasl_done() is begun
      • when using GSSAPI, you use a thread-safe GSS / Kerberos 5 library.

      It says explicitly that that sasl_set* calls are not thread safe, since they set global state.

      The proton library makes calls to sasl_set* functions in :
      pni_init_client()
      pni_init_server(), and
      pni_process_init()

      Since those are internal functions, there is no way for code that uses Proton to lock around those calls.

      I think proton needs a new API call to let applications call sasl_set_mutex(). Or something.

      We probably also need other protections to meet the other requirements specified in the Cyrus documentation (and quoted above).

      Attachments

        Issue Links

          Activity

            People

              astitcher Andrew Stitcher
              mgoulish Michael Goulish
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: