Ignite Realtime is the community site for the users and developers of Jive Software's open source Real Time Communications projects. Your involvement is helping to change the open RTC landscape.
For over a decade, the Jive Software collaborative software has provided our community with a feature rich home for forums, documents, blog posts, and other things. Due to decreased involvement by Jive in Ignite Realtime, sale of Jive Software to Aurea, and other issues "clouding" the future of our Jive cloud instance of this forum, it is time to migrate content to a new platform.
You can find some technical details on the work being done within our Jira instance: INFRA-12
The intention is to make this current forum instance go into a read-only state very soon (next day or so). This will allow for some time to double check the fidelity of the content migration as more users test things out. Hopefully there are no show-stopping bugs with the Discourse instance that would cause us to revert back
Account details were migrated to the Discourse instance, but there was not a one-to-one conversion of usernames due to some issues I won't expound upon here. Your email address did directly translate, so when you first attempt to log into Discourse, you will need to reset your password by providing a valid email address used by the current forum instance. We also plan to support Google Authenticator usage, so you can simply use your google account to log in. If you have any doubts that the current account information is correct with regards to your email address, please feel free to directly email me firstname.lastname@example.org or stop by our web-based group-chat.
Once you have initially logged in, you should be able to update your account settings and change your username to whatever you wish to use for future logins.
The plan is to setup a transparent HTTP forwarding of most legacy community website URIs into the proper location within Discourse. So our migration should not break the web
Indeed, there are some issues to be worked out yet with exactly how we will handle blogs, etc within Discourse. If you are a Discourse expert and want to help out, certainly let us know! There will be a period of whack-a-mole as we workout how this update impacts users and our software, for example the feed of content found on the Openfire Admin Console.
Please let us know your thoughts, this is certainly the time to make changes. Something may be currently setup in a matter that is just the default or something that just hasn't been looked into yet. I certainly do not consider myself an expert with Discourse, with this being my first instance setup!
I would like to thank Alameyo, wroot, Flow, benjamin and others for their help with getting Discourse up and running. And of course, a big thanks to Surevine for their current sponsorship of Ignite Realtime's Amazon Web Services presence.
I am very thankful to Jive Software for their more than generous support of Ignite Realtime over the years. While the amount of source code written by Jive over the past few years has stopped for Ignite projects, their financial support of Ignite Realtime's servers and internet hosting remained steadfast. Speaking for Matt Tucker here, I believe his vision was for Ignite Realtime to mature and become more self sustaining. Recently, a major step toward that goal was taken with the establishment of the Ignite Realtime Foundation and our migration to Amazon Web Services.
Thank you for reading this and your patience as issues are worked out with this migration.
Update 21 September 2016 13:00 GMT: New account registration and new content creation has been disabled for these forums. Please do start using the new system
I've tagged and released Smack 4.2.1 to Maven Central. We decided to omit the smack-omemo* in this release packages as the API is not yet stable. Paul is currently working on encrypted Jingle Transports as part of his GSOC project which also involves OMEMO, and we probably will make some API changes to the existing OMEMO API because of that. As always daily snapshot builds are available from igniterealtime.org/repo.
The Ignite Realtime Community is proud to announce the 4.1.5 release of Openfire. This release signifies our continuing effort to produce stable 4.1 series releases while work continues on the next major release. A changelog denoting 18 resolved issues is available and you can download the release builds from our website. There was one change that we decided not to ship with this release. Work was done to produce 64bit windows installers, but complications exist when you attempt to upgrade previously installed 32bit versions. We hope to iron out those issues prior to releasing 4.1.6 or even 4.2.0, depending on which comes first If testing this functionality interests you, please stop by our chatroom and let us know!
Important to know: Openfire now automatically installs the service. On the last step of the installer you will have an option whether to start it or not (it will also open the browser pointing to Admin Console, if you chose to start it). You shouldn't run the launcher, if the service is started. Documentation is updated accordingly. If you already have older service running, stop it before upgrading.
The following table denotes release artifact sha1sums and some github download statistics for the 4.1.4 release of that particular file.
|OS||sha1sum||Filename||Version 4.1.4 Downloads|
|Linux RPM (32bit JRE)||b3d7b9672d480f767eb83161d892a40fcb9d2e8b||openfire-4.1.5-1.i686.rpm||2,624|
|Linux RPM (No JRE)||d283b5095042a986bbb75338bc22ed7d8ee2847d||openfire-4.1.5-1.noarch.rpm||2,095|
|Linux RPM (64bit JRE)||1d0f4d40e7a56d8f097addb53258f3d30cd091f5||openfire-4.1.5-1.x86_64.rpm||7,598|
As a reminder, our development of Openfire happens on Github and we have an active MUC development chat hosted at email@example.com. We are always looking for more folks to pitch in with testing, fixing bugs, and development of new features. Please consider helping out!
As always, please report any issues in the Community Forums and thanks for using Openfire!
This blogpost doubles as a GSoC update, as well as a version release blog post.
I have the honour to announce the upcoming release of Smack! Version 4.2.1 brings among bug fixes and additional features like Explicit Message Encryption (XEP-0380) and Message Processing Hints (XEP-0334) support for OMEMO Multi-End-Message-and-Object encryption (XEP-0384). The OMEMO protocol was developed by Andreas Straub for the Conversations messenger (also as a Google Summer of Code project) in 2015. Since then it got quite popular and drew a lot of attention for XMPP in the media. My hope is that my efforts to develop an easy to use Smack module will result in an even broader adoption.
The new Smack release is available from the Maven snapshot repository.
OMEMO is a protocol for multi-end to multi-end encrypted communication, which utilizes the so called Double Ratchet algorithm. It fulfills amongst the basic requirements of encrypted communication (confidentiality, authenticity and integrity) also the properties of deniability and forward secrecy as well as future secrecy. Smacks implementation brings support for encrypted single and group chats including identity management and session renegotiation.
Current implementations (as well as this one) are based upon the libsignal library developed by OpenWhisperSystems for their popular Signal (formerly TextSecure) messenger. Smack's OMEMO support is structured in two modules. There is smack-omemo (APL licensed), which contains the logic specified in the XEP, as well as some basic cryptographic code. The other module smack-omemo-signal (GPLv3 licensed) implements some abstract methods defined by smack-omemo and encapsulates all function calls to libsignal.
Currently smack-omemo-signal is the only module available that implements the double ratchet functionality, but there has been a lot of discussion on the XMPP Standards Foundations mailing list regarding the use of alternative (more permissively licensed) libraries for OMEMO (like for example Olm, a double ratchet implementation from our friends over at the [matrix] project). So once there is a new specification that enables the use of other libraries, it should be pretty easy to write another module for smack-omemo enabling OMEMO support for clients that are not GPLv3 compatible as well.
Smack’s OMEMO modules are my first bigger contribution to a free software project and started as part of my bachelors thesis. I’m quite happy with the outcome
That was a lot of talking about OMEMO. Now comes the second functioning of this blog post, my GSoC update.
My project of implementing Jingle File Transfer (XEP-0234) for Smack is going relatively well. I'm stuck at some points where there are ambiguities in the XEP or things I don't know yet, but most of the time I find another construction site where I can continue my work. Currently I'm implementing stanza providers and elements needed for file transfer. Along the way I steadily create Junit tests to keep the code coverage at a high level. Already it pays off when there are fiddly changes in the element structure. I already got file transfer over Jingle IBB working.
It’s a real pleasure to learn all the tools I never used before like code coverage reports or mocking and I think Flow does a good job introducing me to them one by one.
That’s all for now. Happy hacking
The Ignite Realtime Community is proud to announce the 4.1.4 release of Openfire. This release signifies our continued effort to have a stable 4.1 release series while work progresses on the next major release. A changelog exists denoting our 14 resolved issues and you can download the release builds from our website. The following table contains a reference of release build files, their associated sha1sums and the number of times the previous release for that build type was downloaded.
|OS||sha1sum||Filename||Version 4.1.3 Downloads|
|Linux RPM (32bit JRE)||8846cd55047d9871ef9357568e0c1a9f43c41652||openfire-4.1.4-1.i686.rpm||3,293|
|Linux RPM (No JRE)||61a89afb66d74d523addbd238bf0c008ffada8aa||openfire-4.1.4-1.noarch.rpm||2,249|
|Linux RPM (64bit JRE)||8f370c7e9dfe530f7d05d93122ca72b9b563c92c||openfire-4.1.4-1.x86_64.rpm||12,142|
As a reminder, our development of Openfire happens on Github and we have an active MUC development chat hosted at firstname.lastname@example.org. We are always looking for more folks interested in helping out, so please consider pitching in!
As always, please report any issues in the Community Forums and thanks for using Openfire!