Charging and Control Applications (MOSC)

MOSC Banner

Disabling SSLv3 Support to Avoid SSL Poodle Attacks on WebRTC Session Controller 7.0

edited Feb 5, 2015 4:14AM in Charging and Control Applications (MOSC) 2 comments

KM Doc ID 1950427.1 is published to explain how to avoid SSL poodle attacks on WebRTC Session Controller 7.0.


It was recently discovered that SSLv3 has security limitations in it, therefore it makes sense that servers should not allow SSL/TLS handshake to agree on using SSLv3 as the underlying protocol. This can be done by applying a system property in the start scripts for the WebRTC Session Controller.


Adding the system property into the start script of your WebRTC Session Controller will reduce the handshake compatibility with client that require SSLv3 or older protocols.


Edit the setDomainEnv.sh under <domain_home>/bin

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center