-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So a lot of us flipped the encryption required flag for our
Server-to-Server connections yesterday, how did it go? For my self it
went very well, but I also tend to only communicate to other XMPP folks :)
I would love to hear from operators and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yesterday we have enabled encryption required for C2S and S2S to MayPlaces.com.
Initially we had problems, but after doing some tests and adjustments in some
of our systems associated with XMPP, internally everything is going very well.
The problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/01/2014 20:39, Leho Kraav wrote:
I'm also considering OpenFire - something move, because for one crucial
feature OpenFire doesn't support being logged in with multiple
resources. http://issues.igniterealtime.org/browse/OF-103 seems
On Sun, Jan 5, 2014 at 7:52 PM, Waqas Hussain waqa...@gmail.com wrote:
Prosody was the first server to allow multiple resources behind a
single nick (AFAIK, I implemented it in Prosody). I think the ejabberd
folks were looking into implementing that, but not sure what their
progress is.
On Sun, Jan 5, 2014 at 8:21 PM, Peter Saint-Andre stpe...@stpeter.imwrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On my personal server, I too plan to keep the encryption-required
setting in place.
I'm turning it off again, for S2S. C2S I had enabled anyway, but seeing as
it's just
2014-01-05 20:13 skrev Mike Taylor:
I would love to hear from operators and normal users about any results
or issues that were seen or heard about.
I have some friends who do not run properly configured TLS-enabled
servers and have tried to persuade them into fixing it, linking to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/01/2014 21:15, Leho Kraav wrote:
Maybe it's a stale bug status, but logging in with multiple resources
on a single account most *definitely* works on OpenFire - I use it all
the time on my 3.8.2 install, no issues. It even nicely lists the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/05/2014 01:23 PM, Dave Cridland wrote:
On Sun, Jan 5, 2014 at 8:21 PM, Peter Saint-Andre
stpe...@stpeter.imwrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On my personal server, I too plan to keep the
encryption-required setting in
Hi Leho,
On 5 January 2014 20:13, Leho Kraav l...@kraav.com wrote:
Hi all
Looking at the chatme.im thread, it got me curious - does anyone here know
any additional resources for work done on Candy Chat other than the github
forks?
I don't know of any open-source additions to it that aren't
Addition: also servers which didn't have tls properly configured or enabled.
--
*Marco Cirillo*
/LW.Org/LW.Org IM Owner Head Developer/
/Metronome IM Project Mantainer/Developer/
/Jappix Mantainer/Developer/
http://lightwitch.org
smime.p7s
Description: Firma crittografica S/MIME
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/05/2014 03:41 PM, Marco Cirillo wrote:
Il 05/01/2014 20:13, Mike Taylor ha scritto: So a lot of us flipped
the encryption required flag for our Server-to-Server connections
yesterday, how did it go? For my self it went very well, but I also
11 matches
Mail list logo