I Use This!
Activity Not Available


Analyzed 3 months ago. based on code collected 3 months ago.
Posted 18 days ago by igniter...@jiveon.com
The Ignite Realtime community is proud to announce that nearly 2 years after the release of Smack 4.1, the first Release Candidate (RC) of Smack 4.2 has been uploaded to Maven Central. Smack 4.2 marks another milestone in the development of Smack. ... [More] With the availability of the first RC, the API of Smack 4.2 was sealed. This means that now is the ideal time for Smack users to adopt their codebase to the new Smack 4.2 API, and eventually start using Smack 4.2 in the experimental/development branch of their codebase. Please consult the Smack 4.2 Readme and Upgrade Guide for more information.   I'd like to use this post also to draw your attention at a very important topic. The codebase of smack-core and -tcp has grown historically over the past 15 years. This is not an issue per se. Smack was well designed from the beginning, is now modular and not affected by bit rot. But especially on important class, namely XMPPTCPConnection, has come to age. It is based on threads, when it should use NIO. It uses triggers for state changes, when it should be designed as finite state machine. And some more. I know that a lot of people are affected by Smack creating at least 2 threads per connection (instead of using NIO). This all also contributed at some amount to the latest security vulnerability found in Smack (SMACK-739 / CVE 2016-10027).   The only solution to tackle this would be to re-implement the affected code from scratch. But needles to say that this also would require funding, as it is not a simple one weekend task. I hope to have the resource to do this at some point in the future. If you think you can help, or know someone who possibly would be interested support the funding, then please contact me. [Less]
Posted about 2 months ago by igniter...@jiveon.com
A critical security vulnerability has been found in Smack. Please upgrade immediately to Smack 4.1.9. Like all Smack releases with the same major and minor version numbers, 4.1.9 is a drop in replacement for all Smack 4.1 releases. Smack 4.1.9 is ... [More] available on Maven Central.   The Ignite Realtime community would like to thank Sylvain Sarméjeanne for discovering and reporting the vulnerability to security@igniterealtime.org. [Less]
Posted 6 months ago by igniter...@jiveon.com
I've just uploaded Smack 4.1.8 and 4.2.0-beta2 to Maven Central.   Smack 4.1.8 fixes a few minor issues and is expected to be the last release of the 4.1 branch. As always, Smack releases with the same major and minor version numbers are drop in ... [More] replacements. Ideally you just need to change a single variable somewhere in your build system.   Smack 4.2.0-beta2 is the latest beta of Smack's current development branch. Notable additions include support for XEP-0313: Message Archive Management (MAM) and the IoT XEP series. [Less]
Posted 6 months ago by igniter...@jiveon.com
Starting with b91978dcc4ae partial support for the IoT XEPs was added to Smack. The XEPs consists, amongst other XEPs, of XEP-0323: Data XEP-0324: Provisioning XEP-0325: Control XEP-0347: Discovery The XEPs are in experimental state, which means ... [More] changes to them are possible. Smack does currently only support a partial set of the mechanisms specified, especially when it comes to Data and Control. For example only boolean and integer values can be read and written But support for more data types can be easily added.   The IoT API for those XEPs is available in the latest snapshot builds of Smack, which are available via Maven Central's snapshot repository.  A quick start guide can be found here.   The development of the API was sponsored by Clayster. Clayster creates technology to secure trust in the transactions between physical and digital entities, and strives to be that generic foundation for your physical assets digital life. Clayster has an IoT discovery and provisioning platform supporting XEP-0347 and XEP-0324. The platform is available for those who are interested to explore XMPP and IoT further.  If you don't want to run your own infrastructure, Clayster is able to provide an XMPP Server and the discovery/provisioning platform for you. Feel free to reach out to rikard at clayster.com if you are interested to learn more about using XMPP for your next IoT project. www.clayster.com [Less]
Posted 9 months ago by igniter...@jiveon.com
Two new releases of Smack have just been pushed to Maven Central.   Smack 4.1.7 fixes a few bugs. One noteworthy bug is that on certain platforms Smack's setEnabledSSL(Protocols|Ciphers) had no effect. More information about the fixed bugs can be ... [More] found in the Release Notes.   The careful reader may noticed that this is the first beta release of Smack 4.2. Which means that Smack 4.2 just entered the beta phase. My rough timeplan is to release Smack 4.2 in 6 months: starting with 3 months long beta period now, followed by 3 months of release candidates. But as all schedules in the software industry, take it with a grain of salt. [Less]
Posted 12 months ago by igniter...@jiveon.com
I've just released and uploaded Smack 4.1.6 and 4.2.0-alpha3 to Maven Central.   Smack 4.1.6 contains a few important bug fixes for Smack's stable branch: 4.1. The changelog can be found here: Smack Changelog   The third alpha version of Smack's ... [More] upcoming development branch contains a ton of fixes and new features. Adventurous users are encouraged to explore the API improvements. But, as the version name suggests, don't use an alpha version for production deployments. A provisional and incomplete list of Smack 4.2's highlights can be found at Smack 4.2 Readme and Upgrade Guide · igniterealtime/Smack Wiki · GitHub [Less]
Posted about 1 year ago by igniter...@jiveon.com
The Ignite Realtime community is proud to announce the availability of Smack 4.1.5. Like all patch level releases, this release includes some important fixes and users are strongly encouraged to update. Smack 4.1.5 is a API compatible drop-in ... [More] replacement for every release of the Smack 4.1 series. Have a look at the changelog and the git changelog.   Thanks to everyone who contributed to this release by providing bug reports and patches. [Less]
Posted over 1 year ago by igniter...@jiveon.com
I've just published Smack 4.2.0-alpha2 on Maven Central. Everyone who wants to look into which direction Smack is heading, and current Smack users eager to be prepared for the upcoming API changes are invited to test this version out. We are ... [More] awaiting your feedback in the Smack Users forum.   More information about Smack 4.2 can be found in the Smack 4.2 Readme and Upgrade Guide. [Less]
Posted over 1 year ago by igniter...@jiveon.com
The Ignite Realtime community is proud to announce the availability of Smack 4.1.4. This release includes some important fixes. Most notably MultiUserChat's UserStatusListener would not always get triggered in previous releases. Also the JOSN/GCM ... [More] provider did not correctly parse JSON/GCM extensions. Smack 4.1.4 includes fixes for those and addresses a few other bugs. Since it is a patch level release, Smack 4.1.4 can be used as drop-in replacement for any previous version of Smack 4.1. Users are encouraged to update existing projects depending on Smack.   This is also a friendly reminder that Smack 3 has critical security vulnerabilities. Please check if you are affected by those if you are still using Smack 3 and update as soon as possible. [Less]
Posted over 1 year ago by igniter...@jiveon.com
I've just released Smack 4.1.3 to Maven Central. This is a bugfix release which can act as drop-in replacement for any Smack 4.1 version. Users are encouraged to update since Smack 4.1.2 introduced a memory leak in the Roster API which was fixed in 4.1.3.