Hi Ingo, thx for the info. See my other e-mail. We'll have to check how someone was able to manipulate index.php but I'll wait for Oystein to contact me. He's the Drupal expert, and there might be a vulnerability in the CMS. Afterwards we need to contact Google again.
It also might be that someone with access as local, non-priveliged user did exploit the recent linux kernel bug (though I doubt it). I checked http://lwn.net/Articles/347006/ for my company yesterday and figured out that I would be able to get root access on all Redhat and SuSE servers without a problem ... not that bad if you know that I'm working for the biggest German telecommunication company at the moment ;-). Anyhow, this is something the provider of gnubg.org (Bytecamp) has to take care of. Ciao Achim On Sat, Aug 15, 2009 at 1:02 AM, Ingo Macherius <[email protected]> wrote: > For whatever reason, the block must have been activated within a few hours > before this mail as it worked fine a few hours earlier. Tested on Windows XP > and Vista with FF 3.5.2 german version. > > See: > http://safebrowsing.clients.google.com/safebrowsing/diagnostic?client=Firefox&hl=de&site=http://gnubg.org/ > > Confused, > Ingo > > > > _______________________________________________ > Bug-gnubg mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/bug-gnubg >
_______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
