I’m going to attempt to build a functional version of the WOPR supercomputer from the movie Wargames. Well, mine won’t have supercomputer power, but it’ll be really rad.
Here’s my project page I will be keeping updates on: http://www.riscit.info/wopr/
I found this really really simple jquery plugin for registration forms and what not.
It does:
- password metrics (tells you if its a strong password or not)
- submit lockout (user won’t be able to submit form until everything is good)
- minimum strength requirements (user needs to have a password of X strength)
Here is a demo of the script: http://www.thecreativeoutfit.com/freebies/passroids
You can view the options and download it here: http://www.thecreativeoutfit.com/index.php?view=jQuery-Password-Plugin
I recently had someone ask me if they could set the priority of some pages. In this specific case they wanted index.php to take precedence over index.html. Well, on shared hosting you can’t change the server config to do this (which by the way is in the httpd.conf for Apache). So the next best thing to do is .htaccess redirects.
htaccess will only work on Apache webservers, if in doubt consult your webhost. To use these, you will need to create a text file and call it htaccess. Input code from below into it to suit your needs, and upload to your site via ftp. You will then need to rename the file to .htaccess
There are a couple different codes that are returned to the browser on redirects.
301 – Permanent Redirect. Good for moving files forever. This tells the search engine and clients that it has moved permanently and should use the new URI.
302 – Temporary Redirect. It tells the search engine and client that it’s redirecting and should continue to use the requested URI.
Here are some sample redirect usages:
301 Moving a single page
Redirect 301 /oldpage.html http://www.example.com/newpage.html
301 Move entire site
Redirect 301 / http://www.example.com/
To do 302 redirects, just replace 301 with 302.
Edit: This is an old article (circa 2006)
My main linux distribution of choice is Slackware Linux. I recently installed it on my Thinpad 600X. I have a classic Orinoco wireless card that is pretty cool, of course, it doesn’t compare to the Senao cards. Anywho, I wanted to run kismet on this laptop, but Slack uses the orinoco 0.13d drivers. These drivers do not support monitor mode (also called promiscuous mode) which allows for scanning passively. Thus, I had to update the drivers. I have yet to find a site that has complete directions on how to do this, though the shmoo group developed the driver, their directions are not simple for *nix n00bs.
Below you will find how to easily install the patches to enable monitor mode for Orinoco cards so that you can use kismet, tcpdump, etc
Step 1. What we’re going to do is patch the original driver. To do this we need the original driver. You can obtain it from orinoco driver homepage. You will want to get version 13e. Alternatively, you can grab it from my site here
Step 2. Now that we’ve got the driver, we need the monitor mode patch. This is just a *.diff file from the shmoo group. The patch (orinoco-0.13e-patch.diff) can be obtained from their site here http://airsnort.shmoo.com/orinocoinfo.html or alternatively, from my site here.
Step 3. Now you can go ahead and grab the patch to improve channel changing. This patch is from the kismet wireless homepage. This is the orinoco-0.13e-dragorn3.diff patch. I’ve got a local copy of it as well located here.
Step 4. We can now begin the installation of the driver and patches. First you will untar the orinoco driver using
$ tar zxpvf orinoco-0.13e.tar.gz
Step 5. You can begin patching the code now. Change into the directory just created
$ cd orinoco-0.13e
Step 6. And now apply the patch
$ patch -p1 < ../orinoco-0.13e-patch.diff
Step 7. Now apply the performance patch
$ patch -p1 < ../orinoco-0.13e-dragorn3.diff
Step 8. After everything is patched, you need to compiled the driver using
$ make
Step 9. When it is done compiling, you will need to be root to install it
$ su
Step 10. You can now install the driver
$ make install
Step 11. If you haven’t received any errors (which you shouldn’t have), everything has worked fine. You can now plug in your wireless card to see if it worked with the iwpriv command.
