Skip navigation
All Places > Ignite Realtime Blog
1 2 3 Previous Next

Ignite Realtime Blog

243 posts

The Ignite Realtime Community is pleased to announce the 4.0.4 release of Openfire.  Openfire is a cross-platform real-time collaboration server based on the XMPP (Jabber) protocol. This release signifies our ongoing effort to produce a stable 4.0 series release while continuing to work toward a 4.1 release. A changelog of fixes is available and indicates 16 issues resolved.

 

As always, please report issues in the Community Forums and you can download this release from our website.  Here are the sha1sum's for the downloads available.

 

 

Platform
sha1sumFilename
Mac

1d95db39719843ec731ddc69ffb622212b85feb9

openfire_4_0_4.dmg
Windows3d342c6f45abb9fc6aff990cf25d879ee20470edopenfire_4_0_4.exe
Binary (tar.gz)

5b395f2aedfa55e989730ee960a8c6cb7624bd0e

openfire_4_0_4.tar.gz
Binary (zip)

dfb2860197e50858728e2532cd8f21d8f61a6658

openfire_4_0_4.zip
Source (tar.gz)e947ffdf4746d3d0a7efb7cf25d198c05668ab54openfire_src_4_0_4.tar.gz
Source (zip)fbd8e4c143b7c4841fcb231db2c5974d90137b4fopenfire_src_4_0_4
RPM Installer

94d5e0f21f7cbef8d5986e29e3f2f2fc3bec7796

openfire-4.0.4-1.i386.rpm
DEB Installerb16d334a90c86e7b15e9ec44162ec01ca700434dopenfire_4.0.4_all.deb

 

As a reminder, Openfire's source code and development can be found on Github and an active developer discussion occurs within our open_chat@conference.igniterealtime.org groupchat.  Please consider helping out with Openfire's development!  We can use help in about all areas of development, but especially:

  • experienced packaging developers to improve the install/upgrade experience on various platforms
  • developers interested in transitioning Openfire to Maven
  • testing of bamboo generated builds

 

Thank you for your interest in Openfire!

wroot

Spark 2.8.2 Released

Posted by wroot Champion Nov 25, 2016

The Ignite Realtime community has just released Spark 2.8.2 and it can be downloaded from Ignite Realtime: Downloads .

 

This is a regular update. But there is a change, which can affect new users. "Accept all certificates" option on the Adanced menu on the Login screen won't be enabled by default for new users from now on. This option makes Spark automatically accept expired, self-signed and other incorrect TLS certificates. Which makes it less secure. If you are using self-signed certificates, your new users will have to enable this option manually (once). Or you can add this option to a preconfigured spark.properties file, if you distribute it to new users. Old users won't be affected by this (those upgrading straight from 2.7 version will still be affected). We encourage server admins to use certificates from trusted authorities (e.g. Let's Encrypt). This version also includes 4.1.9 update for Smack, which has a fix for a critical security vulnerability.

 

UPDATE (2016/11/29): it looks like Spark is not saving settings on Advanced menu, if a user has never opened it. For such users "Accept all certificates" setting will be disabled after updating to 2.8.2 from any version. They will have to go to Advanced menu and enable it, if they encounter "Unable to verify a certificate" error.

 

Those who are using Client Control plugin will have to update it to version 2.1.0 as Spark 2.8.2 is already modified to work with that version and it will miss many menus and checkboxes if being used with an older version of that plugin. 2.1.0 version requires Openfire 4.0.0 at least. If you are using older version of Openfire and want to keep using Client Control, you might want to hold of updating to Spark 2.8.2.

 

We also would like to mention SparkMeet plugin provided by our long time contributor Dele Olajide. Hopefully we will find a way to bundle this plugin with Spark or provide other options to use it. You can also vote here and tell what you think about it. Initial commit is done and its in Spark's source code sparkmeet plugin - initial release by deleolajide · Pull Request #253 · igniterealtime/Spark · GitHub.

 

For a complete list of changes please check Spark Changelog

 

As usually we encourage new developers to join Spark project and provide patches. Those familiar with Smack can join the development easier, as we are now using the latest stable version (4.1.9). Patches can be attached in the forums or submitted as PRs on GitHub.

 

Here are the contributors to this release (besides myself):

freeseawind · GitHub  contributed new skin for Spark - LittleLuck

Alexander198961 (Aleksander Kovtunenko) · GitHub  fixed the issue with Spark freezing on exit because of a faulty plugin

Michael  added more settings to default.properties and Client Control plugin, fixed showing of an empty Unfiled group and a few other issues

Martini26  updated Polish translation

speedy  fixed an issue with systray icon switching to regular one when it should be DND or Away and a few issues with invisible mode

nicoben (Nico Ben) · GitHub  updated Italian translation

 

Here are sha1 checksums for the downloads:

7a45319a723368b6c830a1c1a7287fb207140b4f spark_2_8_2.dmg

dd9c533868d42fc0ef651d544f463ff1fba5d21c  spark_2_8_2.exe

fb324011e7f1a61b5e793b2c6b1778306bf19102  spark_2_8_2_online.exe

20dbc5940a450ab3176f1dcf4d4dfd01f90b4b06  spark_2_8_2.tar.gz

813e110f6715f7f72af28e2ee90ed2bd9fa11005  spark-2.8.2.rpm

1409189a0877a203ef3fe16410a520056fe214d7  spark-2.8.2.src.rpm

565ff2947b4cca69f73f6818f18d49571db6bf78  spark_2.8.2.deb

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 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.

Lately, I have stared to use Spark client again alongside Skype for Business which I use daily for my professional work. My renewed interest in Spark came initially to have a look at the hard work wroot, guus and the rest of the igniterealtime community had put into Spark 2.8.1 and also to access the chat rooms at igniterealtime, especially the IRF.

 

I use Openfire Meetings myself from time to time and had developed a basic plugin for Spark that allows users to join audio and video conferences hosted by Openfire Meetings. See the documentation for more details. It provides a button from a Multi User Chat (MUC) room or chat window within the Spark client, to open a Chrome window using the same URL as the Jitsi Meet web client. It therefore assumes you have Chrome installed and configured as your default browser. It works, but the user experience is not ideal.

 

I had done some work with Java Chrome Embedded  Framework (java-cef) a while back and decided to use it directly instead of depending on Chrome installed and configured as the default browser. I spent my weekend working on it and this what I have to show for my effort

 

sparkmeet.png

It is a much better user experience than opening a Chrome browser window out of context somewhere else. Like everything in life, there is a price to pay. It does not do screen sharing and does not work on OSX. (don't know how to configure java-cef for OSX). I have tested it at home on my windows win32 desktop and will test it tomorrow at work on my win64 desktop. I would appreciate any feedback from Linux users.

 

The source code is on the Ignite Realtime GitHub repo and PRs are welcome especially to make it work on Macs (OSX)

 

Update

I have given up on java-cef. The lack of current pre-built binaries and missing features like screen share makes it difficult to work with. Our UI expert at work suggested I tried Electron Atom instead. It proved to be very good advice. Whole screen sharing is now available. Desktop sharing and remote control to come later. You will need Openfire Meetings 0.3.28 and above to use it and the pre-built Electron run-time files are available for Windows, Linux and OSX unlike java-cef.. Spark will take a take a minute or two to start after the plugin is deployed. Any feedback on OSX and Linux will be appreciated.

 

I am going to miss the potential of I could do with the tight Java integration, but with Chromedriver, a new world of JavaScript API development with Spark beckons.

A few months ago, I wrote about the relocation of our community. The bits and bolts that power our community have since been migrated, and all is running wel. During that progress, we had a couple of awkward moments along the lines of: "to whom will Jive transfer ownership of the DNS records for Ignite?" We started discussing that topic, and concluded that it would be good to have a legal entity to represent our community.

 

We've been working on a plan ever since, that today, I'd like to share with you. We're planning to start a foundation, the Ignite Realtime Foundation. Its objective: to promote, support and advance development of software in the Ignite Realtime Open Source community.

 

If you're interested in this effort, have questions, or want to contribute in effort or resources, please reach out. We've set up a new chat room at irf@conference.igniterealtime.org that we use for discussions on the subject.

wroot

Spark 2.8.1 Released

Posted by wroot Champion Oct 1, 2016

The Ignite Realtime community has just released Spark 2.8.1 and it can be downloaded from Ignite Realtime: Downloads .

 

This is a bugfix release for 2.8.0, which has introduced a huge overhaul and created a few new issues. Many users had problems with login after upgrading to 2.8.0. This won't change with 2.8.1. It is not a bug, but rather an incorrect setup. Admittedly, this was introduced because of lack of security check in older Spark\Smack versions. But we can't leave Spark blind to bad or forged certificates (in the age of security breaches and moving all the web to TLS). So, if you have this problems, please read Login issues since Spark 2.8.0 . 2.8.1 is introducing an option "Disable certificate hostname verification (not recommended)" in the Advanced settings of the Login screen. If you can't fix your setup or want a temporary workaround, you can use it. But be warned, that you will make yourself (or your users) less secure. 2.8.0 also introduced new setting "Accept all certificates" in the same place. It was enabled by default for those upgrading from 2.7.7. It automatically accepts self-signed and some other incorrect certificates (expired, etc.). This was done to make 2.8.0 backwards compatible, if you were using self-signed certificates provided by Openfire. This setting will stay enabled after 2.8.1 update. But there is a plan to make it disabled by default for new installations in 2.8.2 version.

 

For a complete list of changes please check Spark Changelog

 

As usually we encourage new developers to join Spark project and provide patches. Those familiar with Smack can join the development easier, as we are now using the latest version. Patches can be attached in the forums or submitted as PRs on GitHub.

 

Here are the contributors to this release (besides myself):

nicoben (Nico Ben) · GitHub  updated Italian translation

speedy  added option to login with not matching certificate's hostname, fixed showing incorrect errors when logging in and empty profile fields issue

Alexander198961 (Aleksander Kovtunenko) · GitHub  fixed links opening in KDE environment

Guus der Kinderen  fixed various parts of Spark to behave correctly or log errors

 

Important information for SSO (Single Sign On) users, if they are using SRV records: SSO (Single Sign On) configuration changes since Spark 2.8.0

[SIP phone] SIP plugin is not working since the Smack 4 update.

[Voice Chat] Jingle (PC to PC) calls are not working at this point.

[Linux] Flashing plugin is not working on Linux systems.

 

Here are sha1 checksums for the downloads:

7ab1df8764529b8bfc070b259878470ccbd7640c spark_2_8_1.dmg

bbd029caeb12fc4d9ea6e87b37a5f0377c6a1c29  spark_2_8_1.exe

41b485146393a38966b2eecb832c795b0f0915a8  spark_2_8_1_online.exe

6c68f083d2e6e303e679b614f10536e4563d272c  spark_2_8_1.tar.gz

751721d241d880d9b7772038ec030230b4ccbb38  spark-2.8.1.rpm

c264ccb4e16b401a1814c43342f31a0a3cf36cc6  spark-2.8.1.src.rpm

91a6dfaaf63ca96a5c69b4eb825d2539adffc1b1  spark_2.8.1.deb

wroot

Spark 2.8.0 Released

Posted by wroot Champion Aug 25, 2016

The Ignite Realtime community has just released Spark 2.8.0 and it can be downloaded from Ignite Realtime: Downloads.

 

This is a major release marking the end of support for Java 7 (which has reached the end of life state more than a year ago). Full Spark installers have already been bundled with Java 8 for some time. Online installer won't work with Java 7 starting with 2.8.0 version. We recommend updating to Java 8. Underlying Smack library has been updated to the latest version in this release. Roar plugin has received new popup control options as well.

 

There is a huge list of changes in this version. So this most probably has introduced new issues (though we have tried to catch and fix most of them before the release). Please report in the forums, if you find them. Again, please do not post bug reports in the comments of this blog post.

 

For a complete list of changes please check Spark Changelog

 

As usually we encourage new developers to join Spark project and provide patches. Those familiar with Smack can join the development easier, as we are now on the current version of it (4.1.8 at the moment of this release). Patches can be attached in the forums or submitted as PRs on GitHub.

 

Here are the contributors to this release (besides myself):

Wolf  updated Roar plugin to have separate settings for group chat and keyword matching popups, added system style popups

Alexander198961 · GitHub  added option to save room's password, added URL support to admin's broadcast dialog

Леонід  added Ukrainian translation

nicoben (Nico Ben) · GitHub  updated Italian translation

speedy  fixed failed login process with self-signed certificates, updated Substance skin library, fixed an issue with idle on Windows 10 lock screen

Daryl Herzmann  fixed Debian build

 

We owe Guus der Kinderen  a separate mention. Guus has done a huge job of updating Spark to the current Smack version, which contains a lot of bug fixes, security patches and new features. He has also fixed many other issues along the way. Such as group chat window size issues, room occupants presence management, annoying word wrapping issue with long text lines, SSO/GSSAPI problems, etc.

 

Important information for SSO (Single Sign On) users, if they are using SRV records: SSO (Single Sign On) configuration changes since Spark 2.8.0

 

UPDATE: Important information for those having login issues with 2.8.0: Login issues since Spark 2.8.0

 

[SIP phone] SIP plugin is not working since the Smack 4 update. We hope to have it fixed for 2.8.1.

[Voice Chat] Jingle (PC to PC) calls are not working at this point.

[Linux] Flashing plugin is not working on Linux systems.

 

Here are sha1 checksums for the downloads:

6fa1265e7def8800e0a4356bd1b7d8cf58bb85f8  spark_2_8_0.dmg

741c20d9141c88ecde08d60fbc11145887d32573  spark_2_8_0.exe

b76e36da81469561fdad4a227fa4ad68d792ca7b  spark_2_8_0_online.exe

e2fcdddb4e84f6f1abe9d62a39aa0c7c9e06d814  spark_2_8_0.tar.gz

a772028ba10db2084ea7e2b7b1fb408803c77a5b  spark-2.8.0.rpm

38ca0d9ab5ccd7d61be03b702a0abd5c8939ada5  spark-2.8.0.src.rpm

fba8705d54f49bceb62f19a30348482f9bbeacfb  spark_2_8_0.deb

The Ignite Realtime Community is pleased to announce the 4.0.3 release of Openfire.  Openfire is a cross-platform real-time collaboration server based on the XMPP (Jabber) protocol.  This release signifies our ongoing effort to produce a stable 4.0 series release while continuing to work toward a 4.1 release. A changelog of fixes is available and indicates 14 issues resolved.

 

Note: There was an unfortunate and complicated problem with the distributed 4.0.2 .deb Openfire installer.  If you had troubles with it and reverted to 4.0.1, we hope that you try 4.0.3 now.  See OF-1116 for some more details.  Also, if you are an experienced Debian/Ubuntu packager, we would certainly love your feedback on how the .deb package for Openfire is generated and distributed.

 

Additionally, this update contains an updated truststore. This truststore is used by Openfire to secure remote connections.  If you are using an installer and have manually updated this file in the past, it is likely that the installer will not overwrite your changes with the new truststore.  Please review your resources/security directory after install and rectify differences you may find.

 

As always, please report issues in the Community Forums and you can download this release from our website.  Here are the sha1sum's for the downloads available.

 

Platform
sha1sumFilename
Mac

3dcba5b91d3078618aaff182bb1f0d84be7b9e63

openfire_4_0_3.dmg
Windows690d3b2114b98f45836191f73d242ee9702c6771openfire_4_0_3.exe
Binary (tar.gz)

39b0f04bb6471f9d9aaaeda4fbdf6839a4062a4e

a2222bbef28342553a8ec00500064929dc77029d (updated 19 August 2016)

openfire_4_0_3.tar.gz
Binary (zip)

f65b7ffdf563a6a7deb85594ec1534748a942e6a

170468f366c7cd185b1c987f84e020fb96864f91

openfire_4_0_3.zip
Source (tar.gz)87aa9a17938c3ce9441d61802e669f87fd0e324fopenfire_src_4_0_3.tar.gz
Source (zip)698c598a73dd01cec4037df98190f017dbb19444openfire_src_4_0_3.zip
RPM Installer

70da0a51da40cb955288db977b5d405a49667efc

ad42faaa8da58de463124fa35d0ae0271a20e4bd (updated 19 August 2016)

openfire-4.0.3-1.i386.rpm
DEB Installer5c53afd72cf527edf81915d2aaa0fe68d96b6346openfire_4.0.3_all.deb

 

Update 19 August 2016: A problem was found with the 32bit RPM containing a 64 bit JRE.  This artifact has been refreshed on the website for download. Also Binary (tar.gz) package has been replaced to include the usual binaries.

 

As a reminder, Openfire's source code and development can be found on Github and an active developer discussion occurs within our open_chat@conference.igniterealtime.org groupchat.  Please consider helping out with Openfire's development!  We can use help in about all areas of development, but especially:

  • experienced packaging developers to improve the install/upgrade experience on various platforms
  • developers interested in transitioning Openfire to Maven
  • testing of bamboo generated builds

 

Thank you for your interest in Openfire!

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 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.

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 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

moving-home.jpgPlease be aware that over the next few days, the IgniteRealtime community will be moved to new server environment. As a result, new IP addresses will be used for the XMPP domain, this website and the Atlassian stack (JIRA, Bamboo et al). The community forum (everything under the "community" tab of the website) is not affected by the migration.

 

We plan to move gradually, a few services at a time. The migration will start in the coming few days, and will continue for some days to come. You can expect some downtime, but that should be limited. Watch this space for updates!

 

So, why are we moving in the first place? I've addressed this previously in a thread on the community, from which I'll cross-post the more interesting bits here.

 

Jive Software has expressed their intention to reduce the sponsoring of the hosting of this community. What will be discontinued specifically is all of the Contegix-based hosting, which includes the servers that run the igniterealtime.org website, our Atlassian stack (Bamboo, JIRA), our XMPP domain, and related tooling. The forum functionality that you're using to read this message is based on the Jive cloud, which is different from the Contegix-based hosting. Jive Software has expressed that we're welcome to continue to make use the Jive cloud-based solution for the foreseeable future.

 

After Jive established the community back in 2006, they continued to put in a lot of effort to maintain and support both the people and software. On top of that, they've been incredibly generous in regards to spending money on development and hosting - looking for suitable replacement for the hosting of this community has made us more aware of exactly how generous, too! But we accept that over time, Jive's business has moved away from XMPP and Instant Messaging. Most of our contacts within the company have also moved on by now, which resulted in where we are today - pretty much distinct entities. It's no wonder that Jive re-evaluated their support. We are extremely grateful for all of the time, effort, and money that we received from them in the past. Jive is also actively working to end our cooperation well, offering support and even donation of the existing hardware, as well as plenty of notice. Kudos.

 

After Jive expressed their intentions, we've been actively searching for a new home for our community. We have had some great offers, more than we would have imagined (thank you!). We eventually decided to accept the generous offer from John Atherton, of Surevine Ltd, who have offered to help us by hosting our entire environment in Amazon, as well as support us during and after the migration. I am inviting Surevine to write a posting here to further introduce themselves.

 

As for the migration: over the past few weeks, several of us (both in the community and within Surevine) have been putting in quite some time to prepare for everything. An important part of the move is rebuilding infrastructure that was put in place over a decade ago. This has been an interesting exercise in spelunking...  We've had to make some adjustments left and right, but we feel that we're good to go. Still, we'd like to ask you to be on the lookout for missing functionality. Although we're trying to cover all bases, a lot of nuts and bolts were added over the last few years. We will have missed one or two, or we might have believed some to be non-important while they were not. Feel free to pop into the community chat or leave a message here if you think we missed something!

 

Thanks for your patience while we move IgniteRealtime to its new home.

 

Dele, Guus and myself will be in London for a brainstorming and development sprint on Openfire Meetings.

 

This is in the context of Openfire Meetings within WikiSuite, and we will make improvements, useful to all the community (even if you don't use the Openfire Meetings plugin nor WikiSuite)

 

Here are some examples of things we could be working on: WikiSuite | Openfire Meeting and Jitsi Meet development

 

If interested in participating, please contact me.

 

Best regards,

 

M ;-)

The Ignite Realtime community has just released Spark 2.7.7 and it can be downloaded from Ignite Realtime: Downloads .

 

This is another minor release marking exactly one year since Spark project reboot (yeah, we also like to have Anniversary Update ). There are a few small fixes and updates in this release (as a regression with Idle presence, fix for OTR plugin, etc.). I want to use this chance to look back at the last year. Spark had 7 more releases since the 2.7.0 during that time. 100 tickets have been resolved. Some old patches have been applied (laying around in the forums and the tracker for years). We have also received new patches from around 10 new contributors. Which is great! We see that Spark project is often forked on GitHub, so we hope more developers will forward their patches and new features to the main project. There is also an official Wikipedia page for Spark now (and additional 6 languages linked to it) in hope to increase awareness of this project.

 

Here are the contributors to this release (besides myself):

Alexander198961 · GitHub

speedy

kilida (kilida) · GitHub

rarog · GitHub

 

For a complete list of changes please check Spark Changelog

 

Here are sha1 checksums for the downloads:

0d375c422bd86f9c8ded5484a173256871abaa26  spark_2_7_7.dmg

9f737012121432c20ca7db427051f29cbfca9734  spark_2_7_7.exe

39886c77a4b9821c2a12ea0b7623b9859e62d513  spark_2_7_7_online.exe

c62fe47aa89022b4d784245b833af7893b3e4897  spark_2_7_7.tar.gz

2e23a28d62cd37d6ab4c4a8befd19e765cea3a3b  spark-2.7.7.rpm

5fde7df644950d414bb997f32034a68efeb22cec  spark-2.7.7.src.rpm

 

[Voice Chat] Jingle (PC to PC) calls are not working at this point, but SIP should be improved.

[Linux] Flashing plugin is not working on Linux systems.

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 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.

Thanks  to the sponsorship of Marc Laporte  and the effort of Guus der Kinderen, we have improved the documentation of Openfire Meetings. There is still a lot more work to be done, but we are making good progress. You can find it here. Please have a read if you use this Openfire plugin. The latest version of the plugin can be found here.

Filter Blog

By date: By tag: