CVE-2010-4329

Cross site scripting was possible in search, that allowed
a remote attacker to inject arbitrary web script or HTML.

CVE-2010-4480

Cross site scripting was possible in errors, that allowed
a remote attacker to inject arbitrary web script or HTML.

CVE-2010-4481

Display of PHP’s phpinfo() function was available to world, but only
if this functionality had been enabled (defaults to off). This may
leak some information about the host system.

For the stable distribution (lenny), these problems have been fixed in
version 2.11.8.1-5+lenny7.

For the testing (squeeze) and unstable distribution (sid), these problems
have been fixed in version 3.3.7-3.

We recommend that you upgrade your phpmyadmin package.

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: http://www.debian.org/security/

As a first, we need to ensure the content inside the div is fully loaded (e. g. images), or else we won’t determine the exact width and height of it. Unless the div is not getting changed after the page was loaded, it is enough to use the $(document).ready() function:

$(document).ready(function() {
// here is our code
});

Detecting the screen size

Here is where you can do the first mistake. Using $(window).height() may not be enough. For some browsers (such as Opera), you will not get the correct size and we need to use window.innerHeight instead. In this case, our code looks like this:

var winHeight = window.innerHeight ? window.innerHeight : $(window).height();
var winWidth = window.innerWidth ? window.innerWidth : $(window).width();

Getting the div size

This is easy, we simply use the height() and width() functions.

Centering the div

Will do it by simple math. Here you can do the 2nd mistake: do not allow negative values as result; part of the window will then get hidden and that content will not be visible and you won’t be even able to scroll to it!

var myTop=parseInt((winHeight-$('#myDiv').height())/2);
var myLeft=parseInt((winWidth-$('#myDiv').width())/2);
if(myTop < 0) myTop=0; if(myLeft < 0) myLeft = 0;
$('#myDiv').css({ "left" : myLeft + "px", "top" : myTop + "px"});

Now, our div is centered on the screen. Do not forget to style the div with a fixed position (position: fixed; on CSS part of your page/site). In many of the examples you will find, it is not fixed and this is the reason why the div will scroll once with the window. If you want it to remain centered, this is the way. Also, put a background color, maybe some borders. Without a background color, you will see both texts, the one form the newly centered div and the one the page already has. Also, the z-index property is important, you need the div to be over everything else on page. A style example follows:

#myDiv {
background-color: #FFFFFF;
border: 1px solid #AAAAAA;
display: none;
position: fixed;
top: 10px;
z-index: 100;
}

Of course, if you are using this to have kind of popup windows, you will need to have show/hide functions and maybe even an overlay layer or functions to detect the complete load of the div due to user interaction, but I’ll cover this topic on another tutorial.

I consider myself B as being deprecated. There are a lot of years behind since B should have been removed. My guess is all the engines which will consider as being important for ranking the bold text, will be using STRONG instead of B.

As of what the search engines are considering now, it looks like Yahoo gives higher ranking for B than STRONG and could not see any difference on Google. I like considering Yahoo is still using old algorithms and B will soon get changed to STRONG. Even so, I would still recommend using STRONG. If the SEO part is properly made (I am not talking here only about the local file optimization), the content will be indexed by a lot of 3rd party websites (which will probably consider STRONG rather than B) and this will improve the ranking results more to balance to standards, which defines STRONG as a replacement of B.

The same group attacked some other websites as well, such as:

• Senator Joe Lieberman;
• PostFinance;
• Assange’s Swedish prosecutor’s website;
• the website of the lawyer representing the two women who were allegedly assaulted by Julian Assange.