You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by Rafael Schloming <rh...@apache.org> on 2015/04/03 05:48:53 UTC
[ANNOUNCE] Qpid Proton 0.9 released
Hi Everyone,
Qpid Proton 0.9 is now officially available. You can find it here:
http://qpid.apache.org/releases/qpid-proton-0.9/index.html
In addition to numerous bug fixes and improvements, the 0.9 release
includes a new reactive API that makes it significantly easier to integrate
AMQP into an existing application, or to build custom AMQP applications
from scratch.
The release also includes a number of fixes and/or enhancements resulting
in API changes, some of these are noted below:
- pn_buffer_t is no longer public API
- pn_bytes_t.bytes is renamed to pn_bytes_t.start
- pn_sasl_{client|server}() is replaced by pn_transport_set_server() and
client being the default.
There is also an important Windows SSL/TLS functionality change:
The Proton SSL/TLS module for 0.8 using the native Microsoft SChannel
libraries was not configurable and successful handshakes resulted
solely from having the appropriate CA certificate in the official
Windows Trusted Root CA store. It is now possible to specify
alternate trusted root CA databases and to turn off certificate
checking altogether, using the same Proton API conventions as for
OpenSSL on Posix systems.
In particular, Proton applications in Windows will not check server
certificates at all in 0.9 unless the capability is explicitly enabled
using the pn_ssl_domain_set_trusted_ca_db() function. To use the
system Trusted Root CA store:
pn_ssl_domain_set_trusted_ca_db(d, "sys:root")
Or to use a file based PKCS#12 certificate store:
pn_ssl_domain_set_trusted_ca_db(d, "mycerts.p12")
For more information, see the detailed release notes posted on the release
page at the URL above.
--Rafael
Re: [ANNOUNCE] Qpid Proton 0.9 released
Posted by Mike Kienenberger <mk...@gmail.com>.
Congratulations on your release!
I recommend that you include a short description of what Qpid Proton
is or does as the first paragraph of your release announcements. Your
release announcement is an opportunity to market your project to
others who have never heard of Qpid Proton and may not even know what
Qpid is or does.
Note: I am not subscribed to "proton@qpid.apache.org" and no response
is necessary.
On Thu, Apr 2, 2015 at 11:48 PM, Rafael Schloming <rh...@apache.org> wrote:
> Hi Everyone,
>
> Qpid Proton 0.9 is now officially available. You can find it here:
>
> http://qpid.apache.org/releases/qpid-proton-0.9/index.html
>
> In addition to numerous bug fixes and improvements, the 0.9 release includes
> a new reactive API that makes it significantly easier to integrate AMQP into
> an existing application, or to build custom AMQP applications from scratch.
>
> The release also includes a number of fixes and/or enhancements resulting in
> API changes, some of these are noted below:
>
> - pn_buffer_t is no longer public API
> - pn_bytes_t.bytes is renamed to pn_bytes_t.start
> - pn_sasl_{client|server}() is replaced by pn_transport_set_server() and
> client being the default.
>
> There is also an important Windows SSL/TLS functionality change:
>
> The Proton SSL/TLS module for 0.8 using the native Microsoft SChannel
> libraries was not configurable and successful handshakes resulted
> solely from having the appropriate CA certificate in the official
> Windows Trusted Root CA store. It is now possible to specify
> alternate trusted root CA databases and to turn off certificate
> checking altogether, using the same Proton API conventions as for
> OpenSSL on Posix systems.
>
> In particular, Proton applications in Windows will not check server
> certificates at all in 0.9 unless the capability is explicitly enabled
> using the pn_ssl_domain_set_trusted_ca_db() function. To use the
> system Trusted Root CA store:
>
> pn_ssl_domain_set_trusted_ca_db(d, "sys:root")
>
> Or to use a file based PKCS#12 certificate store:
>
> pn_ssl_domain_set_trusted_ca_db(d, "mycerts.p12")
>
> For more information, see the detailed release notes posted on the release
> page at the URL above.
>
> --Rafael
Re: [ANNOUNCE] Qpid Proton 0.9 released
Posted by Chris Richardson <cr...@fourc.eu>.
Something seems to have gone a little awry with the release page in 0.9 -
most links under the "Documentation" section here
http://qpid.apache.org/components/messenger/index.html
appear to be broken (0.8 equivalents are ok)
(eg:
http://qpid.apache.org/releases/qpid-proton-0.9/protocol-engine/c/api/messenger_8h.html
)
I minor oversight I'm sure ;)
Chris
On 3 April 2015 at 04:48, Rafael Schloming <rh...@apache.org> wrote:
> Hi Everyone,
>
> Qpid Proton 0.9 is now officially available. You can find it here:
>
> http://qpid.apache.org/releases/qpid-proton-0.9/index.html
>
> In addition to numerous bug fixes and improvements, the 0.9 release
> includes a new reactive API that makes it significantly easier to integrate
> AMQP into an existing application, or to build custom AMQP applications
> from scratch.
>
> The release also includes a number of fixes and/or enhancements resulting
> in API changes, some of these are noted below:
>
> - pn_buffer_t is no longer public API
> - pn_bytes_t.bytes is renamed to pn_bytes_t.start
> - pn_sasl_{client|server}() is replaced by pn_transport_set_server() and
> client being the default.
>
> There is also an important Windows SSL/TLS functionality change:
>
> The Proton SSL/TLS module for 0.8 using the native Microsoft SChannel
> libraries was not configurable and successful handshakes resulted
> solely from having the appropriate CA certificate in the official
> Windows Trusted Root CA store. It is now possible to specify
> alternate trusted root CA databases and to turn off certificate
> checking altogether, using the same Proton API conventions as for
> OpenSSL on Posix systems.
>
> In particular, Proton applications in Windows will not check server
> certificates at all in 0.9 unless the capability is explicitly enabled
> using the pn_ssl_domain_set_trusted_ca_db() function. To use the
> system Trusted Root CA store:
>
> pn_ssl_domain_set_trusted_ca_db(d, "sys:root")
>
> Or to use a file based PKCS#12 certificate store:
>
> pn_ssl_domain_set_trusted_ca_db(d, "mycerts.p12")
>
> For more information, see the detailed release notes posted on the release
> page at the URL above.
>
> --Rafael
>
--
*Chris Richardson*, System Architect
cr@fourc.eu
*FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norwaywww.fourc.eu
<http://www.fourc.eu/>*
*Follow us on LinkedIn <http://bit.ly/fourcli>, Facebook
<http://bit.ly/fourcfb>, Google+ <http://bit.ly/fourcgp> and Twitter
<http://bit.ly/fourctw>!*