Some tools for air-sniffing + wepcrack. Check http://www.wardrive.net/wardriving/tools for a more complete list:
1. airodump + wepcrack
http://www.tomsnetworking.com/Sections-article120-page3.php
2. airsnort
3. Also, a nice article on WEP attacks is http://www.securityfocus.com/infocus/1814
4. A Knoppix CD with everything you need in: http://remote-exploit.org/index.php/Auditor_main
TimeOutSavingTWikiPreferences < Support < TWiki
Linux (server) - (Sub)Folder size
Try something like this:
du -sk /backup/
It seems that a solution to the problem with Apache and .pdf files viewed by the plugin of IE has emerged. It is a MIME solution, replacing application/pdf with application/x-pdf in /etc/mime.types. I haven't checked it yet because softlab is down...
A. Excerpt from http://lists.suse.com/archive/suse-linux-e/2004-Mar/3193.html:
On Mon, 29 Mar 2004 10:45:00 -0500, Doug Currey wrote
> I am having a problem with pdf files on suse 9 with apache 2
> running.
>
> The files just never loads correctly. Sometimes I get blank pages
> others I get partial loads then an error message from acrobat saying
> it was unable to read the document (109) This is on an internal
> network so I have a fast connection.
>
> I have tested this with a 231k file. Works on RH 7.3 with apache 1.3
>
> Some strange config option I need or what.
>
> Doug
>
> --
Ok after I figured out the mozilla handles this correctly I updated my
Acrobat reader on my windows machine to 6 was ruuning 4. This gave me the
error File does not begin with %PDF-
After looking around I found that for some reason you need to
edit /etc/mime.types
Change the line
application/pdf pdf
to
application/x-pdf pdf
This allowed acrobat 4,5,6 to load the pdf files correctly.
No reason was given as to why x-pdf works it just does.
Doug
---------------------------------------------
B. Excerpt from http://www.keithrowland.com/archives/2003_12.html
To PDF or NOT to PDF
When is a PDF file NOT a PDF file?
When the Adobe Acrobat Reader Plug-in for Microsoft Internet Explorer says it isn't.
What??!!??
So here's the deal. You post a PDF file on your website. You place a link to it on your web page, and you assume the site visitor has downloaded and installed the Adobe Acrobat Reader. We've all been there, it's pretty simple.
But recently, some folks have been having problems with displaying a PDF file within the IE browser window. IE pops up an error, "File does not begin with %PDF-" and gives you a blank page, when in fact, the file DOES contain the required %PDF- and if you Richt-Click the link, and save it, and open the file with the seperate Acrobat Reader program, it opens and displays fine. But the IE browser PLUG-IN complains.
It is unsure whether this is a Microsoft or Adobe issue, since neither one is speaking on the subject. Neither of the company websites have any direct fix for this, while several independent websites and technical discussion groups do acknowledge the problem and only offer up "work-arounds."
The work-arounds are 1) right click and save, then open with reader, 2) disable the Adobe Plug-In, so it forces use of the Adobe reader as a helper app, or 3) use a different browser. Needless to say, all of these require the website visitor to spend some effort to make changes to their system to accomodate a MS/Adobe compatability issue.
This Internet Engineer, not to be defeated by this, browsed through all the posted questions and all the failed attempts to fix it. I searched the Adobe and MS sites to find some clue as to any sort of fix for this. Neither site seemed to indicate a problem, let alone an upcoming fix.
I then noticed a similar problem with PDFs being e-mailed and the corruption of the MIME TYPE. If the correct MIME type is not asserted with an e-mail attachment, the Acrobat Reader will complain. However, with web sites the MIME type is set by the server and the Acrobat reader will open the file, but the Plug-In version will not read it.
After seaching the Adobe website and making sure our Apache server configuration files DID set the MIME type correctly, I decided to venture outside the box. The official setting of the MIME-TYPE for PDF files is "application/pdf". This is posted on the Adobe website. I decided to set the MIME type in our web server mime.type config file to "application/x-pdf" and viola!! The Plug-In worked! And the reader still worked if you downloaded it with a right-click. Nothing was ever said on any of the discussion forums about this and I don't know what prompted me to try this, but I did.
Now the really stupid part. When we had called back Adobe technical support, (after they failed to help us on our previous call), they did NOT want to hear how we fixed it. On our first call, they charged us $35 to listen to our problem and offer no solutions. They forwarded us to another number that led to a dead end. When we offered up the solution, it feel on deaf ears. They figure if it was a change to OUR web server and not anything to do with THEIR program, they didn't want to hear it.
Now this fix may indeed be another work-around, but it only required a change on the server, not a change to how every visitor to a site configures their web browser. And not every web site has this problem, so let me say, our server was a stock installation of SuSE Linux and Apache2 web server. It used the default settings in most cases and certainly the MIME types were set to their defaults and were set according to Adobe's suggestions.
So there is it, another adventure of the Internet Engineer.
I am very happy to announce you that our weblog is up. I hope that this will be useful in our research efforts.