background preloader

ExtremeDRM.com - Digital Rights Management (DRM) News

Password generator I hate passwords. I mean, I don't mind having really important ones be made-up and memorized but what about all those e-commerce and community sites that want me to create accounts? I end up using the same password at all of them and then I feel stupid knowing that one SQL Server exploit or disgruntled admin could cost me my whole identity. So, this is a little Javascript program that will concatenate two fields and MD5 them. Then just hit return and copy your new password so you can paste it into whatever site you're registering at. (Note that all this is done by your browser running the program that's in the source of this page; nothing is passed back to my server. You should be using this more recent version which uses SHA-1 instead of MD5 and base64 instead of hex. Here's a bookmarklet version, which is pretty neat and works now on both http and https sites. Zsolt Molnár has made a Google Gadget version.

Texas German Texas German (German: Texasdeutsch) is a German language dialect spoken by descendants of German immigrants who settled in Texas the in the mid-19th century. These "German Texans" founded the towns of New Braunfels, Fredericksburg, Boerne, Walburg, and Comfort in Texas Hill Country, and Schulenburg and Weimar to its east. History and documentation[edit] Most German Texans continued to speak German in their homes and communities for several generations after settling in the state. During World War I Texas education rules were established mandating English-only instruction, requiring children to learn English in school regardless of what was spoken outside it. Due to the growth of these communities and cultural bias during both World War I and World War II, Texas German speakers drifted towards English and few passed the language to their descendants.[1] The dialect is near extinction, as it is now spoken almost exclusively by a few elderly German Texans. Gillespie County See also[edit]

Part2 - browsersec - Browser Security Handbook, part 2 - Google Code Written and maintained by Michal Zalewski <lcamtuf@google.com>. Copyright 2008, 2009 Google Inc, rights reserved. Released under terms and conditions of the CC-3.0-BY license. ← Back to basic concepts behind web browsers → Forward to experimental and legacy mechanisms This section provides a detailed discussion of explicit security mechanisms and restrictions implemented within browser. Long-standing design deficiencies are discussed, but no specific consideration is given to short-lived vulnerabilities. Same-origin policy Perhaps the most important security concept within modern browsers is the idea of the same-origin policy. In practice, there is no single same-origin policy, but rather, a set of mechanisms with some superficial resemblance, but quite a few important differences. Same-origin policy for DOM access If protocol, host name, and - for browsers other than Microsoft Internet Explorer - port number for two interacting pages match, access is granted with no further checks.

Perfect Prime Rib Article iptables tutorial How to shoot a handgun accurately by Massad Ayoob Issue #85 "I want you to do an article on how to shoot a handgun accurately," Dave Duffy told me. "Make it 2,500 or 3,000 words." Long ago, I would have answered, "Sure, and while I'm at it, how about a history of the world in, oh, 10,000 words or so?" Today, with more than 45 years of handgunning behind me (yeah, I'm old, but I started early, too) I realize that you actually can cover this topic in a fairly short article. The reason is found in the classic statement of Ray Chapman, the first world champion of the combat pistol. I'll buy that. And few handguns have the inherent mechanical accuracy of a good rifle. That said, though, you can get the most of your handgun's intrinsic accuracy by simply performing marksmanship basics correctly. I teach my students a five-point "pre-flight check list" to go through before they fire the shot. The "power stance" I've found that stance is the one thing I'm likely to have to correct first, even when teaching the experienced shooter. High hand grasp Hard grip

javascript Rhino security. I recently had the opportunity to embed Rhino into a third-party web application. The purpose was to permit users to upload (untrusted) scripts. Those scripts could then run with the privilege of the user in question, enforced by the security model inherent in the webapp's API. It all seemed too easy to be true, until I uploaded a script that began with: var CLASS = embeddedObject.getClass().getClass(); var FILE = CLASS.forName("java.io.File"); ...and it went downhill from there rapidly. The problem The problem is/was that I'm trying to use javascript as a "little language" to permit relatively untrusted third parties to upload and execute javascripts within a web application: their entire purpose is to coordinate a few calls on the objects exposed by the web app. I want to expose some of the web application's operations to the javascript by embedding objects into the Javascript context. Rhino is quite clever. The workaround if ("getClass".equals(name)) continue;

My Wallpapaers Security and the Java Platform Oracle Technology Network > Java Software Downloads View All Downloads Top Downloads New Downloads What's New Java in the Cloud: Rapidly develop and deploy Java business applications in the cloud. Essential Links Developer Spotlight Java EE—the Most Lightweight Enterprise Framework? Blogs Technologies Contact Us About Oracle Cloud Events Top Actions News Key Topics Oracle Integrated Cloud Applications & Platform Services

Related: