Skip to main content

FSF sues Cisco

Today, the FSF let Cisco Systems know in no uncertain terms that line had been crossed. The complaint centers on the Linksys brand routers, and the firmware used on those products.

Brett Smith, the licensing compliance engineer at the FSF said that in 2003, the FSF was notified that the Linksys WRT54G used GPL/LGPL licensed code in its firmware, but customers weren't getting the source code that these licenses required Cisco supply. He said that initially, Cisco seemed willing to work with the FSF to put procedures in place so that its products -- at the time, and in the future -- would comply with the license terms the firmware used.

Over the course of five years, a compliance plan never materialized. As the FSF investigated the Linksys WRT54G complaint, it was receiving license violation reports regarding other Cisco products. Smith says that new issues were being brought up before the older ones could be addressed, resulting in "...a five-years-running game of Whack-A-Mole."



Ostatic

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op