WebRTC what does the future of Real-Time browser communications mean?

WebRTC is the latest in peer to peer communications via the browser. We are talking about Chat, Video and Audio completed transmitted via the browser, signaled and connected using servers still on the back-end.

Even though a great new piece of ingenuity it still requires a server or a service paid to commercial servers in order to run effectively. This exchange is called Signaling.

Which is basically is a series of processes allowing each peer browser to Call and Respond to each others, even though passing very little data between in order to work.

In just a few lines of JavaScript code you can have yourself what in essence if the Skype or Today on your application or website. But better and more robust. You can read more about WebRTC on webrtc.org which coincidentally just turned 5 years old. How time flies!

Switching Web Hosts? Do it yourself!

Tired of your current host? Switching to a new host account for your website? Here are the steps:

DISCLAIMER:
You should have already backed-up all your email addresses, and backed up all your files and databases before you make this change, because once done, and depending on your host and how fast they propagate through the internet you might have services interrupted when that switch happens and points to the new host!

There are 2 ways to host your domain with a host provider.
Option 1: Using the Web Host’s nameservers. In this case the Web Host has control over your other DNS services like MX records for email, SPF/Text records for Connection and Spam controls, A records, CNAME records for alias records e.t.c.

Option 2: Using the Web Host’s IP address, while still managing the other DNS records on your Domain side as opposed to the Web Host’s side. So you can enter in an IP in the A Record section of your domain, with an IP and using the * or @ symbols to define a wildcard or all notation. This method allows you to add other records like MX, CNAME, SPF/TEXT and other records without giving all control to the Web Host by using their nameservers. This step is pretty straight-forward if you do not plan to host emails and other records with that Web Host.

Now in the case of using your Web Host’s nameservers as a way to connect to your host account, below are the steps to do that on most user friendly domain registrar platforms.

Step 1:
Log into your Domain Registrar’s account and locate the domain you want to switch hosting services.

Step 2:
Locate your DNS Management page or may be labeled as NameServers as well. And get to the Default or Custom NameServer section.

Step 3:
Note the current values somewhere, and then replace with your new Web Hosts’s nameservers. You will be presented with 4 slots usually, but all you need is the Primary and Secondary nameservers. In the case of NamelyWeb your name serves will be ns1.namelyweb.com as the primary and ns2.namelyweb.com as the secondary or however explained in your welcome host packet or documentation.

Step 4:
Save and confirm changes. You should also make sure that in the DNS Management section you have all other settings documented as a good habit in case you need to revert any change in case you break anything 🙂

Easy right? No go out and do it yourself!

DROWN SSL Vulnerability

Continue reading if you are a Dedicated Server client without managed hosting from us. If you do not have a dedicated server with us and just hosted solutions, no need to read on we have already patched your network and server space.

What is DROWN SSL vulnerability

The DROWN vulnerability is an exploit that allows for remote decryption of SSL communications even if they’re protected by more advanced cipher suites.

What systems are affected?

Anyone who uses SSL for any services including, but not limited to, HTTPS or IMAPS should err on the side of caution and assume they’re vulnerable to this exploit.

What should you do?

  • Any web server software, such as Apache or Nginx, should have SSLv2 disabled completely in favor of more modern cipher suites.
  • If OpenSSL is used, users should make sure it’s been patched to the latest version that fixes this vulnerability.
  • OpenSSL 1.0.1 should be upgraded to 1.0.1s. Those using OpenSSL 1.0.2 should make sure they’re running 1.0.2g.
  • As a generic countermeasure to exploits, efforts should be made to make sure all software and operating systems are regularly patched.
  • Keeping your server updated is always the best way to stay up to date with anti-measures in places to protect you.