1 2 3 Previous Next

Ignite Realtime Blog

201 posts
Flow

(a)Smack 4.0.7 released

Posted by Flow Feb 23, 2015

We just released (a)Smack 4.0.7. This is a bugfix only release.

 

It was found that the passed "hostname" argument to the configured HostnameVerifier in Smack 4.0 was server controllable, which could allow a malicious attacker to circumvention hostname verification. Hostname verification is disabled by default in Smack 4.0, but enabled by default in Smack 4.1. The faulty code was long ago removed in the Smack 4.1 branch, so most Smack 4.1 (pre-)releases are not affected.

 

As a reminder: The second release candidate of Smack 4.1 is available. Consider updating when possible, but please refer to the Smack 4.1 Readme and Upgrade Guide · igniterealtime/Smack Wiki · GitHub  first.

Flow

Smack 4.1.0-rc1 released

Posted by Flow Feb 16, 2015

The Ignite Realtime community is happy to announce the first release candidate of the upcoming Smack version 4.1. Smack is an open source XMPP client library written in Java with multi-runtime support. It can be used with Java SE and Android runtimes. If you haven't done already now is the ideal time to grab Smack 4.1.0-rc1 and try it out. A '4.1' branch has been created, that will track the further development of Smack 4.1. The API of Smack 4.1 is now officially stable and will not change in an incompatible way between further 4.1 releases.

 

Smack 4.1.0-rc1 is available via Maven Central.

One of the reasons I got involved with building real-time web based communication applications with messaging, audio and video audio was because it was a stepping stone on my journey to find the holy grail of cooperative real-time web applications. These are web applications can be used in an N:N model (each user can simultaneously interact with all the other users). These type of applications are closer to real-life and are not restricted by the limitations of technology. As humans, we achieve a lot more when we work in teams and as a community . Now, thanks to the excellent work of the active Jitsi and retired Mozilla Labs teams, I have enabled the Openfire Meetings Collaboration API, a platform to explore real-time collaboration.

 

Image1.jpgImage3.jpg

 

Openfire Meetings is an Openfire plugin that combines JItsi Meet, Jitsi Videobridge and TogetherJS to create a web-based platform with unified mutli-user communications (presence, messaging, audio and video) from which real-time collaborative web applications can be developed.

 

Image4.jpgImage5.jpg

 

As each meeting participant can see and hear each other and share digital content in real time, we now have a working environment very close to real-life interaction. As a starting point, I have added the following demo/sample applications. The real power is when proper business applications are used, enabling tasks to be completed cooperatively by a team working together in real-time and not in a queue or by tag-teaming as we currently do today with email, social software and most web based business applications.

 

Co-Browsing

This is the simplest type of application that can be developed. It is a web site that enables joint navigation by all participants in the meeting. It is using the TogetherJS engine to track and show the multiple cursors and administer remote mouse clicks on each page. In the screen-shot above, I am co-browsing the ignite real-time web site which is not completely co-browse friendly as JIve SBS (for security reasons) does not permit it's pages to be loaded in an iframe. Consequently, the community link click does not work.

 

Cooperative Editing

This is a modified version of "woot", a rich-text collaborative editor by kroky. There are tons of stuff on this subject matter. Just look up "google wave". Etherpad is the most popular and mature implementation so far. I found this presentation very informative especially explaining operational transformation and why woot (without operational transformation) is simpler.

 

Cooperative Drawing

This is the TogetherJS drawing sample application. Openfire Meetings automatically saves the contents of each application for each meeting on the server as XMPP private data against each user that creates the content. Next time you have the meeting, the drawing or rich text pad opens at where you left it from the last meeting.

 

Scrum-Board for Post-It Notes

This an adaptation of Ali Asaria's scrumblr application. It is a very visually appealing application with real-time animation and reminds me of my previous life as a multi-user virtual reality applications developer with VRML.

 

I have promised to explain in detail how to use Openfire Meetings and over the coming months I plan to post a few more blogs on this and how to use the collaboration api for those who may be interested in taking this journey with me.

The Ignite Realtime Community is pleased to announce the 1.0.0 release of the REST API plugin for Openfire.  This plugin is being developed by community member Redeyes. This plugin merges and replaces the functionality found in the "MUC Service Plugin" and the REST functionality found in the "User Service Plugin".  This new plugin allows for REST style administration of Openfire.

 

The current feature list, taken from the README file includes:

  • Get overview over all or specific user and to create, update or delete a user
  • Get overview over all user roster entries and to add, update or delete a roster entry
  • Add user to a group and remove a user from a group
  • Lockout or unlock the user (enable / disable)
  • Get overview over all or specific system properties and to create, update or delete system property
  • Get overview over all or specific chat room and to create, update or delete a chat room

 

Please report any issues or feature ideas for this plugin in the Community Forums.

I'd like to thank everyone at FOSDEM 2015 and XMPP Summit for such a nice time and interesting talks. I sure haven't talk to all people at the XMPP Summit, but hope that we'll meet again soon. You can find my slides of my lightning talk "XMPP and Android" at http://geekplace.eu/files/xmpp_and_android.pdf

 

While travelling home from Brussels in the ICE, I was able to prepare and upload beta2 of Smack 4.1. Please update your build setups and report any issues in the forum.

Dave Cridland

Openfire 3.10.0 Beta

Posted by Dave Cridland Jan 21, 2015

Hey everyone,

 

Since I took on the role of Openfire project lead, the Openfire developers have been working amazingly hard across almost every part of the server's code, with a view to making a new release we can all be really proud of.

 

After a huge amount of work, the Openfire team is really excited to announce we've reached a beta state with the 3.10.0 release, available from http://www.igniterealtime.org/downloads/beta.jsp

 

This release aims to improve security and stability over the current 3.9.3 stable release, provides a set of important new protocol extensions, and modernizes the XMPP core protocol support - in short, this is going to be the release we wanted to make.

 

While this is a beta release, we're not recommending it for critical production use; however this is running on igniterealtime.org itself and developer sites, and we'd appreciate people trying it out in non-critical production cases.

 

We're hoping it'll reach full release rapidly, and we'll be welcoming experiences of anyone deploying so we can add that last polish. Having dealt with the last remaining blocking bug, we're expecting this to move to a final stable release within a week or two.

 

Dave.

Flow

Smack 4.1.0-beta1 available

Posted by Flow Jan 14, 2015

The Ignite Realtime community is happy to announce the first beta version of the upcoming Smack version 4.1. Smack is an open source XMPP client library written in Java with multi-runtime support. It can be used with Java SE and Android runtimes. If you haven't done already now is the ideal time to grab Smack 4.1.0-beta1 and try it out. Compared to the alpha versions of 4.1 the API is considered stable and API changes are unlikely to happen.

 

Release highlights include support for XEP-198 Stream Management (disabled per default), improved multi-threading performance, improved MUC API and support for SCRAM SHA-1.

 

Everyone is invited to test beta1 in his projects. The community forum awaits your feedback and bug reports. Although the beta version has proven reliable so far, please only use it productive after intensive testing.

 

An incomplete list of API changes can be found in the Smack 4.1 Readme and Upgrade Guide. Please consult the Readme before using Smack 4.1.

 

As always, Smack 4.1.0-beta1 is available from Maven Central.

Dele Olajide

Openfire JMX Web Console

Posted by Dele Olajide Jan 10, 2015

Don't cha wish your openfire console was hawt like me? Don't cha?

Image2.jpg

Introducing the openfire jmxweb plugin

 

I have been using java-monitor.com's openfire probe for a while now to mange all my openfire servers for a while now and it pretty much works. The plugin and extra JMX mbeans developed by Guus der Kinderen have been very useful for checking the health on the servers. For various reasons which include the work done by Tom Evans to enable JMX for Openfire (Jetty. Mina, Hazelcast) I decided to monitor my openfire servers directly with an open JMX management console instead. I tried both jconsole and jvisualvm, but found them difficult to use with remote servers. I needed a web based console.

 

After a bit of investigation, I first found jolokia and then hawt.io and together, they are hot and spicey...If you want to know more about both jolokia and hwatio, follow the links. As far as openfire is concerned, hawt.io with jolokia are a perfect fit. The plugin design sits well with openfire's plugin architecture enabling hawt.io monitor plugins to be developed independently for openfire plugins, components. Anything server-side that can expose mbeans can be monitored and managed by a hawt.io plugin in html and javascript.

 

I have packaged hawt.io, jolokia and the openfire mbeans from the java-monitor.com probe into a new plugin called jmxweb. It uses the http-bind web service for hawt.io web console and jolokia's REST API. To access openfire's JMX mbeans, enable it with global property "xmp.jmx.enabled". By default, access is secure and only to admin users. Use "xmpp.jmx.secure" to disable.

Image3.jpg

How to use

To access hawt.io, point your browser at http://your-server:7070/hawt.io

To access jolokia rest api from your javascript applications use URL http://your-server:7070/jolokia. Make sure you provide headers for basic authentication.

 

The plugin only works with latest openfire server 3.10 because of changes to mina in 3.10. I might do a backward build for openfire 3.9/3.8 if there is any interest.

 

What next

I plan to release jmxweb on igniterealtime as a new openfire plugin and develop some mbeans for openfire meetings and a hawt.io plugin to manage them later on. It currently lacks the ability to accumulate jmx data on a central server like java-monitor.com over a period of time to analyse and I will look at implementing a push and store feature much later on.

 

Update

I have attached the jar file for jmxweb plugin that will work with openfire server 3.9.3 and possibly below. Use at your own risk.

 

Update 2

JmxWeb plugin now available as an Openfire plugin for version 3.10 and above

A discussion space at igniterealtime has also been created.

Greetings all.  Baring any significant community protest, the subversion server for Igniterealtime will be shutdown on 1 January 2015.  All of the active and still relevant repositories have been migrated (with commit histories hopefully in-tact) to our Github presence.

 

The following Ignite subversion repositories were not migrated due to them likely no longer being relevant

  • kraken
  • transports
  • wildfire

 

Some of the migrated repositories to Github have not seen development in a number of years.  We are certainly interested to hear of any community members that may wish to revitalize any of these projects:

 

When the subversion service is shutdown, a copy of the repos will be maintained offline in case anything comes up in the future necessitating its revival.   Github has been an awesome platform to collaborate on for our active projects that migrated a number of months ago.  Hopefully this change helps breathe some life into the older Igniterealtime projects!

Dele Olajide

Openfire Meetings

Posted by Dele Olajide Nov 30, 2014

Ignite Realtime is pleased to announce "Openfire Meeting", a new plugin for Openfire that continues the development of the ofmeet web application which was part of the deprecated Jitsi-videobridge plugin.

 

PLEASE NOTE - You will need latest Openfire 3.10.0 to use this plugin. Use a nightly build or wait for the imminent official release.

ofmeet1.png

 

Openfire Meetings is a complete standalone plugin powered by Jitsi Videobridge. It does not depend on any other plugins

 

ofmeet3.png

 

The front-end we application is a combination of Candy and Jitsi Meet and enables the following features

  • Openfire user authentication directly from web browser for both Candy and Jitsi Meet
  • Audio, Video and Telephone (SIP) conferencing directly with Jitsi Meet and from Candy
  • Desktop sharing (screen and applications) using the Openfire Meeting Chrome extension
  • Fastpath user agent with audio and video using the Candy and Jitsi Meet web applications. It also requires Fastpath plugin to be installed.
  • Configuration directly from Openfire admin web pages.

 

ofmeet2.png

How to use

Jitsi Meet - https://your-server.com:7443/ofmeet

Candy - https://your-server.com:7443/ofmeet/candy.html

 

ofmeet5.png

Discussion place is in the community plugins, here

The Jitsi project is to introduce a new plugin for openfire called JitsiMeet which is an easy to deploy and configure version of their JItsi Meet OpenSource (MIT) WebRTC JavaScript application that uses Jitsi Videobridge to provide high quality, scalable video conferences. The new JitsiMeet plugin for Openfire will be supported here at igniterealtime by the Jitsi project directly. This is good news for all of us here at igniterealtime.

 

So, what happens to the old jitsivideobridge plugin?

 

The old jitsivideobridge plugin has been deprecated and removed from igniterealtime. The embedded ofmeet and candy webrtc conferencing applications will re-appear in some future plugin later on. Watch this space.....

Flow

Smack 4.1.0-alpha1 available

Posted by Flow Sep 13, 2014

After months of hard work it's at the time to release the first alpha version of Smack 4.1, the open source Java XMPP client library, for testing purposes.

 

Smack 4.1 marks a milestone in the development history of Smack, as it's the first version that runs native on Android. This means that aSmack is no longer required and will be phased out in the future. Future aSmack releases will be solely form the stable 4.0 branch.

 

Together with support for Android, Smack 4.1 also adds support for XEP-198 "Stream Management" in smack-tcp. XMPP connections with enabled Stream Management provide acknowledgments of sent stanzas (and acknowledges received stanzas to the server) and allow transparent stream resumption in case of a network outage (for example because of a WiFi ↔ GSM switch on Android).

 

Smack 4.1.0-alpha1 is now available from Maven Central and we would welcome interested and adventurous users to try this early alpha release and provide feedback. For more information about using Smack 4.1 and how to include it in your Android project, consult the "Smack 4.1 Readme and Upgrade Guide".

Flow

(a)Smack 4.0.0 released

Posted by Flow Jun 8, 2014

5 months after the relase of Smack 3.4.1 the Ignite Realtime developer community is proud to annouce the first release of Smack 4, which marks a milestone in the development history of Smack. Smack has undergone a major overhaul and refactoring, including moving from Ant to Gradle and from SVN to git.

 

Smack 4 also includes security related fixes. Users are encouraged to update  as soon as possible.

 

Many people have helped to develop this release. We especially would like to thank

 

- Ryan Sleevi of the Google Chrome Security Team for reporting a security flaw in ServerTrustManager (SMACK-410)

- Thijs Alkemad for reporting a security flaw regarding IQ spoofing (SMACK-533, SMACk-538)

- Lars Noschinski for fixing the IQ spoofing flaws and adding support for roster versioning (SMACK-399)

- Jens Offenbach for helping making Smack an OSGi bundle (SMACK-343)

 

Since the API has changed in Smack 4, make sure to read the "Smack 4.0 Readme and Upgrade Guide".  A full changelog can be found in JIRA.

Flow

(a)Smack 4.0.0-rc2 released

Posted by Flow May 25, 2014

Six weeks after the release of the first Release Candidate (-rc1) of Smack 4, the Ignite Realtime Community is proud to announce the release of the second and likely final Release Candidate.

 

Smack 4.0.0-rc2 contains many improvements and bug fixes. The API underwent some major changes and is considered stable. Now is the perfect time to test (a)Smack 4.0 if you haven't already. Smack is available from Maven Central (direct link). aSmack can be obtained from http://asmack.freakempire.de/4.0.0-rc2/

 

Make sure to read the upgrade guide and the previous blog post about Smack 4.

The Ignite Realtime Community is pleased to announce that Openfire version 3.9.3 is available for download!

 

Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache license. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). Openfire is incredibly easy to setup and administer, but offers rock-solid security and performance.

 

This release corrects the regressions found with the 3.9.2 release, which include:

 

  • [OF-782] - Wrong URL generated for editing groups with space in the names
  • [OF-783] - Apply encryption to secure properties during setup (updating openfire backended by LDAP would fail)
  • [OF-787] - TLS server to server connections are not working with 3.9.2
  • [OF-791] - Joining new MUC room results in a 404 error
  • The initial 3.9.2 release had a packaging problem with the windows installer.

 

A full changelog can be found here.

 

We'd invite interested developers to fork our github repository and contribute pull requests with your fixes.  Ongoing discussions are happening in the community forums about the future of Openfire development.  Please join in if you are interested!

 

Please report bugs with this release in the community forumsPlease do not report bugs by commenting on this blog post!

 

Here are md5sum's for the released files:

 

md5sumfilename

59d8bd304397850d9b229d800aad3295

openfire_3_9_3.dmg
872f728b1b2d43407492452c6c323166openfire_3_9_3.exe
60823e2ccc79165992f3298971134095openfire_3_9_3.tar.gz
1f425ed151762ae689bfab472ce26605openfire_3_9_3.zip
a5d43cfd91785b269e50814e5cd71b8eopenfire_src_3_9_3.tar.gz
987a494caca5dd770dd3ed38e3f753c8openfire_src_3_9_3.zip
fe514555792d82f30f0c063f2e11ff9bJSopenfire-3.9.3-ALL.pkg.gz
742ca4a8b2b971176feb9e8d1ad26e63openfire-3.9.3-1.i386.rpm
76a0f776025227799e862955e0f40018openfire-3.9.3-1.src.rpm
a71be983670491cf280e7ef02315f234openfire_3.9.3_all.deb

Filter Blog

By date:
By tag: