Page History

The Qpid Proton C transport code is responsible for receiving and sending all the protocol bytes into and out of the Proton-C engine. It encapsulates all the protocol processing. Effectively turning the wire level protocol into more abstract AMQP model state changes and vice versa turning AMQP model state changes into wire level protocol to send.

...

The biggest functional changes happen in the SASL layer code where the API has largely changed, very little backwards compatibility has been kept, because it is fairly clear that very few (if any) people have been using the current API to implement their own SASL mechanisms. If this turns out to be untrue, then we could add some further measure of backwards compatibility as required.

Functions Removed

• void pn_sasl_client(pn_sasl_t *sasl)

• void pn_sasl_server(pn_sasl_t *sasl)

These functions have been deprecated 

• pn_sasl_state_t pn_sasl_state(pn_sasl_t *sasl)

• size_t pn_sasl_pending(pn_sasl_t *sasl)

• ssize_t pn_sasl_recv(pn_sasl_t *sasl, char *bytes, size_t size)

• ssize_t pn_sasl_send(pn_sasl_t *sasl, const char *bytes, size_t size)

• pn_sasl_outcome_t pn_sasl_outcome(pn_sasl_t *sasl)

   

• void pn_sasl_mechanisms(pn_sasl_t *sasl, const char *mechanisms)

• const char *pn_sasl_remote_mechanisms(pn_sasl_t *sasl)

• void pn_sasl_plain(pn_sasl_t *sasl, const char *username, const char *password)

Functions Added

Transport

Functions Added

...

• All of the SSL encryption possibilities have some use and all could be used to authenticate the server for the client to avoid "man-in-the-middle" attacks.
• The right 2 columns correspond to an encrypted connection
• The bottom 2 rows correspond to an authenticated connection
  

ssize_t pn_sasl_send(pn_sasl_t *sasl, const char *bytes, size_t size)