Good morning. Here's the dissecation of the problem...
like............This sample allows users to use the network transport protocol independence of JMF in RTP. Users can run RTP over any underlying transport protocol. By default, JMF uses RTP over UDP. Users running RTP over a non UDP transport, can use the RTPSocket object defined in javax.media.rtp.RTPSocket and its accompanying interfaces.
The RTPSocketPlayer.java sampleapp explains the use of the RTPSocket using UDP as its underlying protocol. To use the sample, users need to change the address and port to that of their RTP session. The variables "address" and "port" (line 50) need to match those your RTP server is streaming data to. Recompile the file and run RTPSocketPlayer as
java RTPSocketPlayer
The RTPSocket will stream data over from UDP to the RTPSessionManager
Only the first stream received on the session is played back in this case.
HACKING
Hacking !!!!!! 1) Install and ensure Fail2Ban is working. Fail2Ban locks unauthorised users out of SSH, GUI and Webmin after 3 unsuccessful attempts by placing them in a jail. The only way to regain access is to remove them from a jail. FreePBX systems (other than PIAF) DO NOT include this by default. This is your first line of defence. http://www.fail2ban.org/wiki/index.php/MANUAL_0_8
2) Do not use common or easy to guess passwords for ANYTHING. Use a mixture of upper and lower case and symbols e.g. Wh0@r3you?_6581 . Every extra digit increases the complexity exponentially. Use a password generator like LastPass if you are not creative
3) Only open ports that you must have open. Close any unused ports e.g POP3, IAX2 etc if you are not using them. It is pointless to change your SSH port because an NMAP scan will pick it up anyway.You can try and change SIP port to something other than 5060 though as this is a commonly targeted port.
4) Disable root login on SSH. Let users authenticate with their normal user login and pass and the SU that will require a root level password. This doubles the security on SSH.
5) Use a separate outbound route for all international calls that has a dial plan that matches 00. then pin protect it. Give the client CEO the pin and let him decide who has access to it.
like............This sample allows users to use the network transport protocol independence of JMF in RTP. Users can run RTP over any underlying transport protocol. By default, JMF uses RTP over UDP. Users running RTP over a non UDP transport, can use the RTPSocket object defined in javax.media.rtp.RTPSocket and its accompanying interfaces.
The RTPSocketPlayer.java sampleapp explains the use of the RTPSocket using UDP as its underlying protocol. To use the sample, users need to change the address and port to that of their RTP session. The variables "address" and "port" (line 50) need to match those your RTP server is streaming data to. Recompile the file and run RTPSocketPlayer as
java RTPSocketPlayer
The RTPSocket will stream data over from UDP to the RTPSessionManager
Only the first stream received on the session is played back in this case.
HACKING
Hacking !!!!!! 1) Install and ensure Fail2Ban is working. Fail2Ban locks unauthorised users out of SSH, GUI and Webmin after 3 unsuccessful attempts by placing them in a jail. The only way to regain access is to remove them from a jail. FreePBX systems (other than PIAF) DO NOT include this by default. This is your first line of defence. http://www.fail2ban.org/wiki/index.php/MANUAL_0_8
2) Do not use common or easy to guess passwords for ANYTHING. Use a mixture of upper and lower case and symbols e.g. Wh0@r3you?_6581 . Every extra digit increases the complexity exponentially. Use a password generator like LastPass if you are not creative
3) Only open ports that you must have open. Close any unused ports e.g POP3, IAX2 etc if you are not using them. It is pointless to change your SSH port because an NMAP scan will pick it up anyway.You can try and change SIP port to something other than 5060 though as this is a commonly targeted port.
4) Disable root login on SSH. Let users authenticate with their normal user login and pass and the SU that will require a root level password. This doubles the security on SSH.
5) Use a separate outbound route for all international calls that has a dial plan that matches 00. then pin protect it. Give the client CEO the pin and let him decide who has access to it.
No comments:
Post a Comment