Skip to Content

2014 October

October 31, 2014

FCC considering hybrid approach to ISP reclassification

FCC logo

Ars Technica is reporting that the head of the Federal Communications Commission is close to proposing a “hybrid approach” to net neutrality in which Internet service providers (ISPs) would be partially reclassified as common carriers. Under this proposal, broadband service that ISPs offer to consumers would be maintained as a lightly regulated information service. ISPs would serve as the conduit for websites to distribute content while also classifying them as a common carrier to police deals between ISPs and content providers. This proposal–that would still allow ISPs to charge premium rates on bandwidth speeds–has received mixed support from advocacy groups and providers alike.

For more information, check out this article on Ars Technica.

To learn more about net neutrailty, check out this article from the New York Times.

October 23, 2014

Inbox by Google…maybe the future of e-mail?

Inbox by Google

Gmail’s new user interface

Google announced a new interface and mobile app today called Inbox. For Gmail users, the interface takes some cues from the Google Apps for Education recent updates but incorporates the Tasks feature in Gmail while also incorporating some new features. The mobile app is available on iOS, Android, and Windows Phone stores but using the Inbox interface requires an invitation from Google or from an existing Inbox user. Invite requests can be sent to inbox@google.com.

For more information on the new features and functionality, check out this article from The Verge and this video from Google.

October 15, 2014

Google identifies SSL 3.0 security flaw

Security locks (ZDNet)

Google’s Security Team revealed on Tuesday that the long obsolete, but still all too used, Secure Sockets Layer (SSL) 3.0 cryptographic protocol has a major security flaw.

According to the team’s Bodo Möller: “This vulnerability allows the plaintext of secure connections to be calculated by a network attacker.”

While SSL 3.0 has been succeeded by Transport Layer Security (TLS) 1.0, TLS 1.1, and TLS 1.2, many TLS implementations have continued to be backwards compatible with SSL 3.0 to work with legacy systems for a smoother user experience.

For more information, check out this article posted on ZDNet.com

For information on how to fix the issue, check out this information from ZMAP.io