We are still in the early whistleblowing stages and that gives a huge disguist in any security minded professionals's gut. I mean why would i bother implementing a security mechanism or protocol that might be disclosed or compromised a few weeks now. Just building against the latest openssl is one thing, but reviewing the actual ciphers is another. Right now just about everyone is waiting for more light on the subject. Opensource projects aren't really moving onto tls 1.2 afraid not to look stupid some time ahead.
Voting isn't going to do much here… the question is, is someone motivated to do the work and create a patch. I see no reason we would reject a good working tested patch for this.
Mike
On Sep 13, 2013, at 2:18 PM, EL <fs.user@fordior.net> wrote:
> I'm voting (if I may) for a newer TLS version (1.2) and I share your
> concerns regarding security/privacy. I respect a 'secure by default'
> approach like for example the OpenBSD project. If you ask me, the whole
> security topic is today still nothing compared to what it will become in
> a few years... (It's annoying that so many devices still only support
> unencrypted sip/rtp these days.)
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org