Nothing too exciting, just two regressions fixed: “pasv_address” should work again, and SSL data connections should no longer fail after a long previous transfer or an extended idle period.
Google has rolled out a feature that provides webmasters of compromised sites with samples of malicious code and other detailed information to help them clean up.
The search giant has long scanned websites for malware while indexing the world wide web. When it detects outbreaks, it includes language in search results that warns the site may be harmful and passes that information along so the Google Chrome, Mozilla Firefox, and Apple Safari browsers can more prominently warn users. Google also provides administrators a private list of infected pages so they can be cleaned up.
Now, Google will give additional detail by offering samples of malicious code that criminal hackers may have injected into a website. In some cases, the service will also identify the underlying cause of the malicious code. Admins of compromised websites will get the information automatically when logging in to Google’s Webmaster Tools.
“While it is important to protect users, we also know that most of these sites are not intentionally distributing malware,” Google’s Lucas Ballard wrote here in announcing the new feature. “We understand the frustration of webmasters whose sites have been compromised without their knowledge and who discover that their site has been flagged.”
Over the past few years, a variety of studies have concluded that the majority of malware being foisted on web surfers comes from legitimate sites that have been compromised. Web applications that don’t properly vet text entered into search boxes and other website fields is one of the chief causes. Sloppy password hygiene by webmasters and compromises of website administration tools are two others.
“If the underlying vulnerability is not identified and patched, it is likely that the site will be compromised again,” he said.
This little, but very usefull program, try to sends ICMP packet out the LAN, and detect all the host that allow it. Whit this you can find bugs in your (“company’s”) network ( or others), for example hosts that allow p2p connections.
When we use a Gateway, we send the packets with IP dest of the target, but the dest mac on the Ethernet is the mac at the Gateway. If we send a packet to the different macs in the LAN, we can know who is the gateway when we receive an response from this mac.
Some times we can discover more than one box configured to be an gateway, generally, this is an wrong configuration, and the box will response with an ICMP-Redirect. This is the same, because the script only verify if the mac response.
No time for details at the moment, but I’m just back from HITB Malaysia and a great time was had by all! The hospitality and warmth of the organizing crew surpassed anything I’ve ever encountered before.I presented with my colleague Julien Tinnes. See …
I presented with my colleague Julien Tinnes. See awesome blog:
We presented on various intriguing aspects of sandboxing on Linux, covering vsftpd and Chromium as test cases. Our slides are located here:
Security in Depth for Linux Software
As per other presentations, I'll leave it at that for now and follow up with a mini series of posts for the more interesting points. I think vsftpd is well covered by previous posts, but Chromium on Linux is awesome and its built-in sandboxing deserves a few notes.