Language Selection

English French German Italian Portuguese Spanish


How much legal trouble is Cisco in against the FSF?

Filed under
Legal A new Law.Com analysis indicates Cisco may be in big legal trouble over the FSF lawsuit alleging it misused open source code in its hardware. Until you learn the rest of the story.

some more tomtom stuffstuff

Filed under
  • "They Started It!" -- TomTom Countersues Microsoft
  • TomTom sues Microsoft on patent infringement
  • TomTom chooses a moderate limited hang out route
  • Strike/Counterstrike: TomTom Sues Microsoft
  • TomTom fights back, but not over Linux

TomTom Countersues: Linux And Microsoft Going To War

Filed under
Legal This is exactly what we were afraid of. Last month, when Microsoft sued Dutch GPS-maker TomTom on the principle that parts of Linux -- which form the guts of TomTom's device -- violate Microsoft's patents, we hoped for a quick settlement.

TomTom Linux impact light hit so far

Filed under

blogs.the451group: I’ve been talking to device manufacturers and the Linux-centered software providers and I can definitively report that I am not hearing or sensing any fear, uncertainty or doubt (FUD) as a result of Microsoft’s TomTom patent suit.

Why Microsoft has chosen to go after Linux now

Filed under
Legal A couple of months back, at Australia's national Linux conference, a young Microsoft employee sat down with me and discussed ways in which Microsoft has contributed to open source.

Who should Software Freedom sue on FAT32?

Filed under
Legal Microsoft owns FAT32, but it didn’t appear to pursue its rights. Until the TomTom case. At which point Jeremy Allison of Samba says Microsoft had secret cross-licensing deals with all those other guys which violate the GPL. So who should Software Freedom sue?

Syndicate content

More in Tux Machines

Security Leftovers

  • Friday's security updates
  • Researchers poke hole in custom crypto built for Amazon Web Services
    Underscoring just how hard it is to design secure cryptographic software, academic researchers recently uncovered a potentially serious weakness in an early version of the code library protecting Amazon Web Services. Ironically, s2n, as Amazon's transport layer security implementation is called, was intended to be a simpler, more secure way to encrypt and authenticate Web sessions. Where the OpenSSL library requires more than 70,000 lines of code to execute the highly complex TLS standard, s2n—short for signal to noise—has just 6,000 lines. Amazon hailed the brevity as a key security feature when unveiling s2n in June. What's more, Amazon said the new code had already passed three external security evaluations and penetration tests.
  • Social engineering: hacker tricks that make recipients click
    Social engineering is one of the most powerful tools in the hacker's arsenal and it generally plays a part in most of the major security breaches we hear about today. However, there is a common misconception around the role social engineering plays in attacks.
  • Judge Gives Preliminary Approval to $8 Million Settlement Over Sony Hack
    Sony agreed to reimburse employees up to $10,000 apiece for identity-theft losses
  • Cyber Monday: it's the most wonderful time of year for cyber-attackers
    Malicious attacks on shoppers increased 40% on Cyber Monday in 2013 and 2014, according to, an anti-malware and spyware company, compared to the average number of attacks on days during the month prior. Other cybersecurity software providers have identified the December holiday shopping season as the most dangerous time of year to make online purchases. “The attackers know that there are more people online, so there will be more attacks,” said Christopher Budd, Trend Micro’s global threat communications manager. “Cyber Monday is not a one-day thing, it’s the beginning of a sustained focus on attacks that go after people in the holiday shopping season.”

Openwashing (Fake FOSS)

Android Leftovers

Slackware Live Edition – Beta 2

  • Slackware Live Edition – Beta 2
    Thanks for all the valuable feedback on the first public beta of my Slackware Live Edition. It allowed me to fix quite a few bugs in the Live scripts (thanks again!), add new functionality (requested by you or from my own TODO) and I took the opportunity to fix the packages in my Plasma 5 repository so that its Live Edition should actually work now.
  • Updated multilib packages for -current
  • (Hopefully) final recompilations for KDE 5_15.11
    There was still some work to do about my Plasma 5 package repository. The recent updates in slackware-current broke several packages that were still linking to older (and no longer present) libraries which were part of the icu4c and udev packages.