With the continuous stream of reports about hacked websites it never fails to baffle me, that these sites still fail to take even the simplest steps to protect their user’s passwords. Storing them in plain-text in your database isn’t secure, you could as well just post them on your main page. But still the published database dumps don’t stop to contain these. Are these developers just ignorant or incompetent? Are these old legacy apps once developed by overpaid consultants and not updated ever after? Maybe it’s like Marcus Carey (security researcher & community manager at Rapid7) said: “Many businesses outsource web application development and once the application is deployed, service contracts may lapse or IT staff may not be paying much attention to them.” I don’t know and most likely I never will.
It’s stated in the docs but it seems like everyone has to run into this at least once….
HashMapclass is roughly equivalent to
Hashtable, except that it is unsynchronized and permits nulls.
… or why hashCode() and equals() should be calculated on immutable parts of your keys only and what happens if you don’t.
Vendor: The Apache Software Foundation
Versions Affected: Apache Wicket 1.4.x
Please note: This article applies to wicket versions prior to 1.5 only. Wicket 1.5 introduces an event bus to handle these types of requirements. The solution described here works but it has some issues that weren’t completely resolved when I switched to Wicket 1.5. Most annoying among these is the rather tight coupling from the components to their page, which could be removed by extracting the IReflector-related code from the page and creating an own class for it.
Wicket makes it easy to manipulate CSS attributes on the fly. The most obvious solution would be to overwrite the onComponentTag method and add the logic there. It’s a very powerful solution as you can virtually do anything to the tag. But writing html fragments directly from my Java code is something that smells like JSPs and I don’t like that smell.
Considering myself a Linux-user rather than a power-user or even a Linux-Geek, I thought, I could pick up some tricks from this book. But to make it short: I was disappointed. At first I thought that maybe I just wasn’t part of the target audience and that the book was a little bit mislabelled with “Ubuntu for the computer illiterate” being a more appropriate title. The authors describe at length all the useless stuff on how to make your system as unusable as possible with changed colors, fonts, wallpapers, custom icons for each and every folder or application. While being boring or at it’s best repetitive. “Open the Ubuntu Software Center, Search for this, provide your password when asked, you find your new application here.” - “Open the Ubuntu Software Center, Search for that, provide your password when asked, you find your new application here.” - “Open the Ubuntu Software Center, Search for something else, provide your password when asked, you find your new application here.”