Fact is, we don’t yet know enough details about all possible attack surfaces against SSH available to the agencies and we badly need more information to know what infrastructure components remain save and reliable for our day to day work. However we do have an idea about the weak spots that should be avoided.
The online community tore the project apart and discovered that the makers of Anonabox were disingenuous when they were saying that it was something original, custom built. As it turned out, it was actually a repurposed Chinese device with a slightly better memory. Also, the operating system used was OpenWRT, which is basically Linux distro for routers and other such devices. Most, if not all of the information provided on Kickstarter was a lie. Eventually, the Kickstarter project was suspended and no one got hurt, financially.
In 2014, open source technology came under a heavy barrage of criticism as a result of high-profile security vulnerabilities. Mark Shuttleworth, the founder of Ubuntu Linux and its lead commercial sponsor Ubuntu, has a very different view and remains a stalwart defender of the open source model for software development and security.
In a video interview with Datamation, Shuttleworth details his view on open-source security as Ubuntu Linux celebrates its 10th anniversary.
In 2014, the Heartbleed vulnerability in the open source OpenSSL cryptographic library had wide ranging impact. OpenSSL is widely deployed on servers, VPNs and even mobile devices and it took some time for vendors and users to get systems and devices patched.
"We have a big responsibility to proactively make sure that the system is as robust in the face of inevitable flaws as it can be," Shuttleworth said.
As it turns out, Boeing might actually be BlackBerry's best friend right now. You see, the ultra-secure Boeing Black handset will come with support for BlackBerry's BES 12 device management service. It's not much of a stretch to assume the Boeing Black might also feature BlackBerry's hallmark secure messaging system.
Boies, along with three attorneys representing the States, brought Microsoft to it’s knees — or so it seemed at the time.
On November 5, 1999, Judge Thomas Penfield Jackson found that Windows dominance on the PC made the company a monopoly and that the company had taken illegal actions against Apple, Java, Netscape, Lotus Notes, RealNetworks, Linux, and others in order to maintain that monopoly. He ordered Microsoft broken in two, with one company producing Windows and another handling all other Microsoft software.
As we all know, Judge Jackson’s solution was never implemented.
Although an appeals court upheld the verdict against Redmond, the breakup of the company was overturned and sent back to the lower court for a review by a new judge. Two years later, in September, 2001, under the Bush Administration, the DOJ announced that it was no longer seeking the breakup of Microsoft, and in November reached a settlement which California, Connecticut, Iowa, Florida, Kansas, Minnesota, Utah, Virginia and Massachusetts opposed.
The settlement basically required Microsoft to share its APIs and appoint a three person panel that would have complete access to Microsoft’s systems, records, and source code for five years. The settlement didn’t require Microsoft to change any code or stop the company from tying additional software with Windows. Additionally, the DOJ did not require Microsoft to change any of its code.
Those of us who work in the depths of high technology are not immune to the age-old adage of the shoemaker’s children having no shoes. We probably have the most technologically advanced homes of anyone we know, but we also tend to leave various items alone if they’re not causing problems. After all, that’s what we deal with at work. Who needs to saddle themselves with network upgrade projects at home when nothing’s broken?
The Grinch flaw was reported by Stephen Cody, chief security evangelist at Alert Logic. Cody alleges that the Grinch flaw enables users on a local machine to escalate privileges. Leading Linux vendor Red Hat, however, disagrees that the Grinch issue is even a bug and instead notes in a Red Hat knowledge base article that the Grinch report "incorrectly classifies expected behavior as a security issue."
Today's Git vulnerability affects those using the Git client on case-insensitive file-systems. On case-insensitive platforms like Windows and OS X, committing to .Git/config could overwrite the user's .git/config and could lead to arbitrary code execution. Fortunately with most Phoronix readers out there running Linux, this isn't an issue thanks to case-sensitive file-systems.