Open Realtime.
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.
Open Realtime.
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.
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.
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 ()
- [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 forums. Please do not report bugs by commenting on this blog post!
Here are md5sum's for the released files:
| md5sum | filename |
|---|---|
59d8bd304397850d9b229d800aad3295 | openfire_3_9_3.dmg |
| 872f728b1b2d43407492452c6c323166 | openfire_3_9_3.exe |
| 60823e2ccc79165992f3298971134095 | openfire_3_9_3.tar.gz |
| 1f425ed151762ae689bfab472ce26605 | openfire_3_9_3.zip |
| a5d43cfd91785b269e50814e5cd71b8e | openfire_src_3_9_3.tar.gz |
| 987a494caca5dd770dd3ed38e3f753c8 | openfire_src_3_9_3.zip |
| fe514555792d82f30f0c063f2e11ff9b | JSopenfire-3.9.3-ALL.pkg.gz |
| 742ca4a8b2b971176feb9e8d1ad26e63 | openfire-3.9.3-1.i386.rpm |
| 76a0f776025227799e862955e0f40018 | openfire-3.9.3-1.src.rpm |
| a71be983670491cf280e7ef02315f234 | openfire_3.9.3_all.deb |
The Igniterealtime community and Jitsi.org is proud to release the Jitsi Videobridge plugin for Openfire version 1.3.0 with Openfire 3.9.2. The new version has the latest code from the Jitsi project, fixes a number of issues and implements some requests made from the community
New Features
- New layout and improvements to user experience of ofmeet and jitmeet.
- Username and password protection for the web conferencing applications (ofmeet, jitmeet and candy)
- Support for audio only participants (no webcam).
- Conferencing recording for audio and video separately. Each conference has a single audio recording and a video recording for each participant. Video recording is only available for Windows. Support for video recording on other platforms will be available on a later release.
- Telephone users can join or be invited to the conference as audio only participants
- PDF Presentations can be shared and driven by the presenter.
Fixes, Improvements
- Ofmeet and jitmeet are now auto-configured. Install plugin, restart openfire and go to app home page. You can even use an IP address. Removed config.js. It auto-detects the websockets plugin and uses it when available.
- Screenshare has been improved. Publish.js is no more needed for ofmeet and jitmeet
- Improved the plugin admin web page.
Known issues
- The candy web application has not been touched. It should still work, but could have issues.
- There is an experimental fastpath with video application which uses candy for the agent and some javascript you can add to your web site. Not tested and could have issues.
- There are no user or admin guides. There are also no tutorials or "how to use" videos or blogs. There is a good document by bakko to get most users started, but needs an update.
How to use
Make sure:
- you are using Google Chrome as your web browser
- you have a webcam or at least a sound device installed and ready for use for each user
- you have opened ports 50000 - 60000 (or whatever you configured) on your openfire server
OfMeet
To run the ofmeet video conference application, point your browser at https://your_server:7443/jitsi/apps/ofmeet
Candy
To run the Candy web application with multi-user video, point your browser at https://your_server:7443/jitsi/apps/candy
Spark
To download the Spark plugin, point your browser at https://your_server:7443/jitsi/apps/spark/jitsivideobridge-plugin.jar
JitMeet
To run the jitmeet video conference application, point your browser at https://your_server:7443/jitsi/apps/jitmeet
You will need Google Chrome as your default browser to use the Spark plugin
Finally,
Although jitmeet (Jitsi Meet) and ofmeet (Openfire Meetings) look similar, they are different underneath and are heading in different directions.
Jitsi Meet is for generic XMPP servers and aimed at public internet facing conferencing using services like prezi.org and etherpad.org while Openfire Meetings is for private in-house conferencing where all collaboration applications are integrated into Openfire. For example, Ofmeet uses a PDF viewer which supports in-house corporate powerpoint presentations, while Jitmeet uses prezi.org.
All the source code is now out there on GitHub. Go to Jitsi.org and Igniterealtime.org and start to making improvements
The Igniterealtime Community is pleased to announce that the release of Openfire version 3.9.2 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 contains a large number of fixes (70 Jira issues resolved) aimed at increasing stability, security and XMPP standards compliance. A full changelog can be found here. Some of the highlights of this release are:
[
OF-103] - [MUC] Allow nicknames to be used more than once in the same room by a single user
[
OF-114] - Clearing cache can lock up MUC
[ OF-455] - Some unicode pattern in status message can break the session connection
[ OF-669] - Visually failed first login to Admin Console
[
OF-714] - Add ability to encrypt properties so they are encrypted in the db and do not appear in the admin console.
[ OF-745] - Use TLS-dialback even if that mechanism is not advertised
[ OF-757] - Allow s2s message of subdomain of XMPP domain when no components are found
[
OF-569] - Add deluser adhoc command
[ OF-764] - Group chat history (MUC) should match configuration after server restart
[ OF-771] - MUC service should flush recent history before shutting down
[ OF-125] - Restrict discovery of rooms based on users membership
[ OF-297] - fix: mutual roster deletion problem
[ OF-770] - CVE-2014-2741 Uncontrolled Resource Consumption with XMPP-Layer Compression
[ OF-722] - Openfire should save XEP-0184 delivery receipts as offline message
[ OF-758] - Add support for XEP-0280 "Message Carbons"
This is the first release of Openfire after our migration of code development to Github. We'd encourage interested developers to fork Openfire and send pull requests! It is best for you to create a dedicated branch on your fork to submit the eventual pull request from. Please note that we are not syncing the github repository to the previous openfire subversion repository hosted on igniterealtime.
Here are MD5sums for the downloads available.
| md5sum | Filename |
|---|---|
dba5d987f3473c59546b24312e6bbc23 | JSopenfire-3.9.2-ALL.pkg.gz |
| a215348924c32b5b8aa84bba27355288 | openfire-3.9.2-1.i386.rpm |
| 34a21c2e48ab9358bb187b5f151a3ed4 | openfire-3.9.2-1.src.rpm |
| 6be23cd0822b7dbfab51c663a2df0585 | openfire_3.9.2_all.deb |
| 6539489a7760a8f031e13f53453a3be5 | openfire_3_9_2.dmg |
| 5601aff0fd9b1d8eb1c382013a9f8ea3 | openfire_3_9_2.exe (original with pack issue) |
| ab3fccaf684e478cebd992cf93b6ff2d | openfire_3_9_2.exe (updated) |
| 0b4fab9f9e4834be4e747dc0fc47cff7 | openfire_3_9_2.tar.gz |
| 886d6311429c382ec0655b03d692379f | openfire_3_9_2.zip |
| f3e554025abcb7e9b46a70dfb24caf2c | openfire_src_3_9_2.tar.gz |
| 0fe17ce148e32c8ce934dd152e64c6f8 | openfire_src_3_9_2.zip |
As always, we welcome your feedback, suggestions, tips, hints, questions and other contributions in the Igniterealtime Community Forums. Please do not respond to this blog post with questions.
Recent Discussions
Redeyes in
"Re: Deploying Jersey in an openfire plugin"
everyq in
"[help]In the XIFF example,I get the error 404"
raghvender.m in
"Re: Deploying Jersey in an openfire plugin"
Redeyes in
"Re: Deploying Jersey in an openfire plugin"
raghvender.m in
"Re: Deploying Jersey in an openfire plugin"