#openfire — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #openfire, aggregated by home.social.
-
#XMPP #Java: Important news: #IgniteRealtime #Openfire 5.1.0 will support #ChannelBinding (#TLSExporter / #TLSServerEndPoint / #TLSUnique): #SCRAMSHA1PLUS in more #SCRAMSHA1. Maybe #SCRAMSHA256 and #SCRAMSHA256PLUS too. Initial security request here from 2019: https://web.archive.org/web/20201020085731/https://discourse.igniterealtime.org/t/scram-sha-1-and-scram-sha-1-plus-scram-sha-256-plus-supports/84006
-
#XMPP #Java: Important news: #IgniteRealtime #Openfire 5.1.0 will support #ChannelBinding (#TLSExporter / #TLSServerEndPoint / #TLSUnique): #SCRAMSHA1PLUS in more #SCRAMSHA1. Maybe #SCRAMSHA256 and #SCRAMSHA256PLUS too. Initial security request here from 2019: https://web.archive.org/web/20201020085731/https://discourse.igniterealtime.org/t/scram-sha-1-and-scram-sha-1-plus-scram-sha-256-plus-supports/84006
-
#XMPP #Java: Important news: #IgniteRealtime #Openfire 5.1.0 will support #ChannelBinding (#TLSExporter / #TLSServerEndPoint / #TLSUnique): #SCRAMSHA1PLUS in more #SCRAMSHA1. Maybe #SCRAMSHA256 and #SCRAMSHA256PLUS too. Initial security request here from 2019: https://web.archive.org/web/20201020085731/https://discourse.igniterealtime.org/t/scram-sha-1-and-scram-sha-1-plus-scram-sha-256-plus-supports/84006
-
Openfire deployments have been running in the wild for a *long* time.
Some started when Java 5 was current, Docker didn't exist yet, and IPv6 was still "future tech".
As we prepare the Openfire 5.1.0 release, We'd love to hear your stories: What's the oldest Openfire deployment that you still run?
https://discourse.igniterealtime.org/t/what-s-your-oldest-openfire-deployment/96473
-
Openfire deployments have been running in the wild for a *long* time.
Some started when Java 5 was current, Docker didn't exist yet, and IPv6 was still "future tech".
As we prepare the Openfire 5.1.0 release, We'd love to hear your stories: What's the oldest Openfire deployment that you still run?
https://discourse.igniterealtime.org/t/what-s-your-oldest-openfire-deployment/96473
-
Openfire deployments have been running in the wild for a *long* time.
Some started when Java 5 was current, Docker didn't exist yet, and IPv6 was still "future tech".
As we prepare the Openfire 5.1.0 release, We'd love to hear your stories: What's the oldest Openfire deployment that you still run?
https://discourse.igniterealtime.org/t/what-s-your-oldest-openfire-deployment/96473
-
Openfire deployments have been running in the wild for a *long* time.
Some started when Java 5 was current, Docker didn't exist yet, and IPv6 was still "future tech".
As we prepare the Openfire 5.1.0 release, We'd love to hear your stories: What's the oldest Openfire deployment that you still run?
https://discourse.igniterealtime.org/t/what-s-your-oldest-openfire-deployment/96473
-
Openfire deployments have been running in the wild for a *long* time.
Some started when Java 5 was current, Docker didn't exist yet, and IPv6 was still "future tech".
As we prepare the Openfire 5.1.0 release, We'd love to hear your stories: What's the oldest Openfire deployment that you still run?
https://discourse.igniterealtime.org/t/what-s-your-oldest-openfire-deployment/96473
-
Выдохнул....
Разворачиваю #openfire через #Docker, поднимаю XMPP-сервер, открываю порты, пробрасываю наружу — базовая инфраструктура вроде бы в порядке.
5222 доступен извне, 9090 открывается локально, контейнер жив, веб-интерфейс работает. DNS тоже резолвится нормально через KeenDNS.
Но дальше начинается странное: клиенты просто не коннектятся.
Подключение даже не доходит до нормального XMPP-рукопожатия. Нет stream-а, нет STARTTLS-обмена, нет сертификата на уровне сессии. Соединение выглядит так, будто сервер принял TCP, но вообще не стартанул XMPP.
Проверка через openssl s_client показывает:
handshake есть, но ответов от сервера нет — 0 байт в ответ, никакого certificate chain, никакого STARTTLS.
При этом внутри Openfire всё выглядит “живым”: порты слушаются, сервисы подняты, настройки TLS включены, STARTTLS переключается между Optional/Required, но поведение на клиентском порту 5222 не меняется.
И самое раздражающее — это не сеть и не роутинг. Внешний доступ к порту есть, локально всё поднимается, но XMPP-слой как будто не инициализируется вообще.
В итоге получается странный разрыв: инфраструктура есть, сервис отвечает, но протокол не стартует. Клиенту просто нечего “договаривать” — сервер не начинает XMPP stream.
RE: https://shitpost.poridge.club/notes/amet2c24hc -
Выдохнул....
Разворачиваю #openfire через #Docker, поднимаю XMPP-сервер, открываю порты, пробрасываю наружу — базовая инфраструктура вроде бы в порядке.
5222 доступен извне, 9090 открывается локально, контейнер жив, веб-интерфейс работает. DNS тоже резолвится нормально через KeenDNS.
Но дальше начинается странное: клиенты просто не коннектятся.
Подключение даже не доходит до нормального XMPP-рукопожатия. Нет stream-а, нет STARTTLS-обмена, нет сертификата на уровне сессии. Соединение выглядит так, будто сервер принял TCP, но вообще не стартанул XMPP.
Проверка через openssl s_client показывает:
handshake есть, но ответов от сервера нет — 0 байт в ответ, никакого certificate chain, никакого STARTTLS.
При этом внутри Openfire всё выглядит “живым”: порты слушаются, сервисы подняты, настройки TLS включены, STARTTLS переключается между Optional/Required, но поведение на клиентском порту 5222 не меняется.
И самое раздражающее — это не сеть и не роутинг. Внешний доступ к порту есть, локально всё поднимается, но XMPP-слой как будто не инициализируется вообще.
В итоге получается странный разрыв: инфраструктура есть, сервис отвечает, но протокол не стартует. Клиенту просто нечего “договаривать” — сервер не начинает XMPP stream.
RE: https://shitpost.poridge.club/notes/amet2c24hc -
Выдохнул....
Разворачиваю #openfire через #Docker, поднимаю XMPP-сервер, открываю порты, пробрасываю наружу — базовая инфраструктура вроде бы в порядке.
5222 доступен извне, 9090 открывается локально, контейнер жив, веб-интерфейс работает. DNS тоже резолвится нормально через KeenDNS.
Но дальше начинается странное: клиенты просто не коннектятся.
Подключение даже не доходит до нормального XMPP-рукопожатия. Нет stream-а, нет STARTTLS-обмена, нет сертификата на уровне сессии. Соединение выглядит так, будто сервер принял TCP, но вообще не стартанул XMPP.
Проверка через openssl s_client показывает:
handshake есть, но ответов от сервера нет — 0 байт в ответ, никакого certificate chain, никакого STARTTLS.
При этом внутри Openfire всё выглядит “живым”: порты слушаются, сервисы подняты, настройки TLS включены, STARTTLS переключается между Optional/Required, но поведение на клиентском порту 5222 не меняется.
И самое раздражающее — это не сеть и не роутинг. Внешний доступ к порту есть, локально всё поднимается, но XMPP-слой как будто не инициализируется вообще.
В итоге получается странный разрыв: инфраструктура есть, сервис отвечает, но протокол не стартует. Клиенту просто нечего “договаривать” — сервер не начинает XMPP stream.
RE: https://shitpost.poridge.club/notes/amet2c24hc -
We have released Openfire 5.0.5, our open source real-time communications server! This is a maintenance release, bringing some interesting bug fixes and library upgrades. Read more about this release in our blog! https://discourse.igniterealtime.org/t/openfire-5-0-5-release/96468
-
We have released Openfire 5.0.5, our open source real-time communications server! This is a maintenance release, bringing some interesting bug fixes and library upgrades. Read more about this release in our blog! https://discourse.igniterealtime.org/t/openfire-5-0-5-release/96468
-
We have released Openfire 5.0.5, our open source real-time communications server! This is a maintenance release, bringing some interesting bug fixes and library upgrades. Read more about this release in our blog! https://discourse.igniterealtime.org/t/openfire-5-0-5-release/96468
-
We have released Openfire 5.0.5, our open source real-time communications server! This is a maintenance release, bringing some interesting bug fixes and library upgrades. Read more about this release in our blog! https://discourse.igniterealtime.org/t/openfire-5-0-5-release/96468
-
We have released Openfire 5.0.5, our open source real-time communications server! This is a maintenance release, bringing some interesting bug fixes and library upgrades. Read more about this release in our blog! https://discourse.igniterealtime.org/t/openfire-5-0-5-release/96468
-
Take control of your digital sovereignty with Openfire! 🌐
Discover how this open-source, XMPP-based platform for instant messaging, group chat, voice and video calls, and file sharing can secure your data, enhance privacy, and offer unmatched customization. 💬🔐
#DigitalSovereignty #Openfire #DataPrivacy #SecureCommunication
https://www.igniterealtime.org/support/articles/whitepaper_digital_sovereignty.jsp
-
"🚨 Openfire Vulnerability Under Active Exploit: A Gateway to Ransomware and Cryptominers 🚨"
The widely-used Openfire chat server is under siege as hackers exploit a high-severity flaw, CVE-2023-32315, to deploy ransomware and cryptominers. This Java-based open-source XMPP server, boasting 9 million downloads, has become a lucrative target due to an authentication bypass vulnerability in its admin console. Attackers are creating new admin accounts on vulnerable servers, installing malicious Java plugins, and executing commands via HTTP requests. 🛑
The flaw spans across various Openfire versions dating back to 2015. Although patches were released in May 2023, over 3,000 servers remained vulnerable by mid-August 2023. The first known exploitation dates back to June 2023, when a server was ransomed post-exploitation. Attack scenarios include deploying crypto-mining trojans, installing backdoors, and extracting server information. 🕵️
Dr. Web has identified four distinct attack scenarios leveraging this flaw, emphasizing the urgency of applying available security updates. BleepingComputer also reports multiple instances of Openfire servers being encrypted with ransomware, appending a .locked1 extension to files. The ransom demands range from 0.09 to 0.12 bitcoins ($2,300 to $3,500). 🖥️🔓
The threat landscape is evolving, with threat actors not solely targeting Openfire servers but any vulnerable web server. It's a stark reminder for organizations to stay vigilant and ensure their systems are up-to-date with the latest security patches. 🛡️
Source: BleepingComputer by Bill Toulas
Tags: #Openfire #Ransomware #Cryptominers #CyberSecurity #Vulnerability #CVE202332315 #ThreatIntel #InfoSec #PatchManagement #ServerSecurity #DrWeb #BleepingComputer 🌐🔐
-
#XMPP is the gold standard for interoperability. Its ability to connect projects from different creators is unparalleled, making it the go-to choice for seamless communication.
Community member Luke wrote a guide on configuring #Openfire to work with #Slidge.
Slidge is a gateway designed to connect you to chat networks like WhatsApp, Telegram or Matrix. It acts as a bridge, allowing you to interact with your contacts directly from your single, preferred XMPP client.
-
We are exploring support for #MariaDB, #Firebird and #CockroachDB in Openfire. This includes early pull requests and discussion of trade-offs, maintenance cost and real-world demand.
We would love community input before proceeding further.
Is this valuable, or more trouble than it is worth?
-
Epic 2-Day Fishing Adventure: Catching Giant Bass & Making Fish Tacos on a Remote Maine River https://www.diningandcooking.com/2193874/epic-2-day-fishing-adventure-catching-giant-bass-making-fish-tacos-on-a-remote-maine-river/ #adventure #AdventureAngling #American #AmericanRecipes #BassFishing #CampfireCooking #CatchAndCook #CookingCulinary #FishTacos #FishTacosRecipe #FishTacosTilapia #FishingTrip #GiantBass #MaineRiverFishing #MaineWilderness #NaturalBeauty #NatureCamping #OpenFire #OutdoorCooking #RecipeVideos #Recipes
-
This is nice. Hotel room with an open fire!
-
#FOSDEM was absolutely WILD! 😻
🤯🤯🤯 Got a hand-made #XMPP developers post card with a personal mention!
🤯🤯 Got a "Thanks Ge0rG, keep up the good work!" while walking the food mile!
🤯 Met an IRC contact from 25 years ago, @olbohlen ("Apparently I'm the only operator of #OpenFire on #Solaris") and connected him to @guusdk who brought stickers and hugs!
🤯 Accidentally met an IRC contact from 20 years ago
🤯 Accidentally met an #FDroid member iRL
🤯 Met @sven (#fail0verflow) after 20 years
-
#HealthWarning #CO #poisoning for people having any #openfire in the house!
A CO-monitor saves lives!
Early signs of CO poisoning are headache, dizziness, fast heartbeat and glowing cherry-red cheeks. Immediate medical assistance is mandatory, or severe organ/brain damage can happen! CO binds 250x stronger to hemoglobin - the carrier protein in red blood cells - than O2. Hyperbaric O2 (in chamber) or 100% O2 through a mask is necessary to get the CO off the hemoglobin and replace it with O2. -
We at #MPAQ are constantly looking for security holes.
I admin an #OpenFire #XMPP server for example. In the case of this chat program, it has end to end encryption. When I connect with someone (that doesn't necessarily mean another person on our server), we activate #OMEMO #encryption. Even on the server side with admin access, I can NOT see the conversation.
I work with a local newspaper that is Google fanatics. It absolutely pisses me off they use it to store my info like my SSN and I'm always seeing reports that the US Government is given access to that data.
Edward Snowden should be hailed a hero for giving up his citizenship to tell the truth. His book, Permant Record should be read by everyone.
http://search.mpaq.org/books/P/PermanentRecord.pdf -
@micahilbery yes, I self host #OpenFire (@news) and use @monocles on android, and it works nicely. If you want a chat about it, lmk!
-
Years ago, there began a system called #Jabber that has evolved into the #XMPP protocol/network.
I've had a few servers over the years. Our current one uses #OpenFire and I love it for its #encryption. #MPAQ been running it for about 5 years as I watch others trying to create new ones like #Signal and #Matrix, I just can't understand why more people don't use XMPP except for the others being all shiny and new...
Why are people always trying to reinvent the wheel??? Its not controlled by one source like the Fediverse!!!
-
@HeavenlyPossum NIMBY liberal Boomerism will be the death of us all.
-
📢 Pas de LIBERTÉ sans fournisseur ou ressource IT vraiment LIBRES
💯% de vos fournisseurs IT sont PARTENAIRES GAFAMS🇺🇸⚠️
Free-Solutions Sàrl est fournisseur de libertés informatiques depuis 2️⃣0️⃣0️⃣6️⃣
Solutions LIBRES by Free-Solutions
SaaS privés 🇨🇭 #openfire #jitsi #cryptpad pour votre entreprise sur votre domaine name.
#tech #technology #linux #switzerland #privacy #gafam #geekerware #suisse #opensource
❓ Votre serveur : https://www.free-solutions.ch/hosting
🗨️ 🎥Visioconf & Chat https://www.free-solutions.org -
#Openfire 5.0.1 has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://igniterealtime.org/
-
🚀 Openfire 5.0.1 is out! This update fixes several issues found in the 5.0.0 release that we did last week. Check out the blog post for more details: Openfire 5.0.1 Release #Openfire #XMPP https://discourse.igniterealtime.org/t/openfire-5-0-1-release-our-100th-maybe/95667
-
#Openfire 5.0.0 has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://igniterealtime.org/
-
💯🔒💬 MONOCLE📱: ⛔Whatsapp ⛔Teams
Communications sécurisées privées avec Free-Solutions Sàrl
📱Basculez les téléphones mobiles #android de votre entreprise sur un système sécurisé et 100% sous votre contrôleCommuniquez en toute sécurité dans vos entreprises
#tech #technology #opensource #xmpp #openfire #igniterealtime #switzerland #privacy #libre #mobile #chat #geekerware
-
🔥💬 OPENFIRE 5.0.0 Beta : Testeurs et contributeurs WELCOME🍻
Nous sommes maintenant en phase de tests pour le serveur XMPP Openfire nouvelle version 5.0.0
Nouvelle version VisioConférence Jitsi + Openfire pour ceux qui veulent essayer
0 install fonctionne direct
https://vidconf.free-solutions.org
Votre serveur XMPP et Visio privé : https://www.free-solutions.ch/hosting
#tech #technology #switzerland #libre #opensource #xmpp #igniterealtime #openfire #geekerware #libre #opensource -
#Openfire 5.0.0 Beta has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://igniterealtime.org/
-
@lexoyo Il y a un gros concentré de technologies pour faire ça mais pas de XMPP pour une fois....
Ici = Micro capture+voice2text+LLM Mistral+Text to speech, prog C maison.
On fais aussi des bridges LLM/XMPP et voIP, vidconf avec igniterealtime.org et #openfire et plein d'autres trucs. Normal je fais partie de la communauté #igniterealtime depuis longtemps et on innove tout le temps sur pleins de sujets :)
https://toot.igniterealtime.org/ -
🚀 Exciting update! Openfire Pade plugin v1.8.4 now supports AV1 codec! 🎉 While upgrading Jitsi Meet code remains challenging, this release brings improved P2P call performance. 📈 Check it out and consider self-hosted Jitsi Meet for larger groups. 🔗 #Openfire #JitsiMeet #AV1Codec
https://discourse.igniterealtime.org/t/version-1-8-4-of-openfire-pade-plugin-released/95434
-
🤖🚀🇫🇷 #IA Voice #Mistral 28B Small 🤖🚀🇫🇷
🎬 Petite démonstration de #Mistral Small 28B en mode vocal dans une #visioconférence.
👉 Avec les outils et applications visioconférence #jitsi #openfire & #LLM sur AIBorg server by Free-Solutions Sàrl. Et pas mal de technologies #LIBRES.
✅ Reprenez le contrôle, Free-Solutions Sàrl délivre des systèmes d'IA complets HW + SW + Voice#ai #ia #geekerware #tech #linux #technology #suisse #switzerland #it #llm #vidéo #internet #free #solutions #jitsi
-
Hong Kong Directors Seek Global Partners for Action-Disaster Hybrid ‘Open Fire’
#Variety #Asia #Global #MarketsFestivals #News #Haf #HongKongFilmart #OpenFirehttps://variety.com/2025/film/news/open-fire-hong-kong-haf-1236340164/
-
@drq @sam @daniel While XMPP is definitely behind for the team chat use case, as at least in my corner we have focused on private chat, you have some outdated info.
XEP-0313 enables fetching arbitrary messages by specific ID, ID-ranges and time ranges, so links to specific messages should be possible. Messages can be kept as long your database can handle it. Even full text search is implemented in #Openfire according to @guusdk https://logs.xmpp.org/xsf/2022-05-15#2022-05-15-cff31e4b7fc5c30b
-
#Openfire 4.9.2 has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://www.igniterealtime.org/
-
#Openfire 4.9.1 has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://www.igniterealtime.org/
-
#Openfire 4.9.0 has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://www.igniterealtime.org/
-
#Openfire 4.8.3 has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://www.igniterealtime.org/
-
#Openfire 4.8.2 has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://www.igniterealtime.org/
