-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/06/2014 06:31 PM, Matthew Wild wrote:
> Also note that SSLv3 hasn't been shown to be any less secure than
> TLSv1 (in fact they are essentially the same), but TLSv1 is still
> very widely used. Therefore there is no security reason to disable
>
On 1/6/2014, 8:31 PM, Matthew Wild wrote:
> I believe the best thing we can do for now is to fix and update the
> clients, rather than just cutting them off on the server-side. It
> shouldn't be that hard...
That makes sense, thanks for the quick reply.
On 1/6/2014, 8:31 PM, Matthew Wild wrote:
>
Hi,
On 7 January 2014 01:16, Justin Bull wrote:
> Hello,
>
> It has come to my attention that I should alert this list to an open
> PR I have for ejabberd:
>
> https://github.com/processone/ejabberd/pull/124
>
> It's a simple PR targeting their 2.1.x branch (the version
> jabber.ccc.de was runnin
Hello,
It has come to my attention that I should alert this list to an open
PR I have for ejabberd:
https://github.com/processone/ejabberd/pull/124
It's a simple PR targeting their 2.1.x branch (the version
jabber.ccc.de was running at the time the PR was authored) removing
SSLv3 as an available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
Despite the lack of configurability comfort, I've transitioned from Openfire
to Prosody to fix outbound S2S and cipher limitations. I still hate manual
editing of config files with a passion, but I think user's security and
proper connectivi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please add my public XMPP service to the list at xmpp.net. The
information is as follows:
- domain: [chat.cpunk.us]
- website: [http://cpunk.us]
- year launched: [2014]
- country: [NK]
- latitude: [52.5]
- longitude: [5.75]
- CA: [Self-Signed
Please add my public XMPP service to the list at xmpp.net. The
information is as follows:
- domain: [cabbar.org]
- website: [http://cabbar.org]
- year launched: [2013]
- country: [NL]
- latitude: [52.5]
- longitude: [5.75]
- CA: [CA Cert Signing Authority]
- server software: [ejabberd]
-
Hello,
no (unexpected) problems on my end (neko.im with somewhere between 300
and 400 concurrent users); there were a couple of servers which didn't
have TLS properly configured or enabled - I don't think this is the
place to name and shame, but at least two of them had 'secure' in the
name. Some f
Il 06/01/2014 04:32, Peter Saint-Andre ha scritto:
- All servers which run Openfire even if they support TLS, they
seem to trample on authentication steps when they open a stream to
a server which presents both SASL and DB
It would be good to know more about what's happening here so that we
can
Hello,
on our server (linuxlovers.at & 0nl1ne.at with about 10k users) we had
mostly problems with some standalone Jabber servers with no SSL
certificate or bad SSL configuration options - more than 20 servers on
my list, tried to check them with xmpp.net (thanks for this great
tool), let
I as the operator of a small (<15 users) have had not much problems.
Most of the connections, with the only exceptions gmail.com and ddg.gg,
were encrypted already, so no issues on my side.
No complaints either, but I suspect that is more because of people
cannot know why a contact appears offline
On Mon, Jan 6, 2014 at 3:32 AM, Peter Saint-Andre wrote:
> - - Office365 deployments
>
Meaning the (irritatingly named) Lync? I believe that went through quite
extensive S2S/TLS/Auth interop work. Certainly it's now been put on the
DISA APL (as of September), and that mandates that kind of securi
12 matches
Mail list logo
