Free fakes software for linux

Raw Fake AP is a program that emulates valid IEEE 802.11 access points using wireless raw injection.
Raw Fake AP application aims to create both beacon and probe response frames and could be used to "hide" real networks from novice wardrivers or for testing wireless intrusion detection systems.
Main features:
Overall features:
- Raw injection of beacon and probe response frames in monitor mode
- Try to forge coherent sequence numbers and BSS timestamps (depending on driver injection capabilities)
- Try to have a coherent time interval between beacons (which is hard to achieve without a real time kernel)
Command line interface will help you to choose between:
- Randomize Open/WEP/WPA/RSN crypto
- Randomize b/g cards
- Channel hopping
- TXpower hopping
- Randomize ESSIDs (alnum or not)
- Randomize BSSIDs
- Choose beacon interval
- Choose number of fake access points
- Choose a file with valid OUIs
- Choose a file with ESSIDs
- Choose between beacon or probe response frames
- Select a destination MAC address

NRPG Ratiomaster is a small standalone application which fakes upload and download stats of a torrent to almost all bittorrent trackers.

This means that it does NOT rely on your bittorrent client (uTorrent, Azureus, etc.) and it will NOT download/upload the files on a torrent - it only can fake download/upload.

The application has hardcoded emulations for the most commonly used BitTorrent clients: uTorrent, BitComet, Azureus, ABC, BitLord, BTuga, BitTornado, Burst, BitTyrant, BitSpirit.

o2-sms.pl is intended for customers of O2 Germany that have an account at www.o2online.de. o2-sms.pl can send SMS messages via the WWW gateway.
Use the -f option to send a flash SMS (it will pop up on the recipients display immediately).
The message text can have up to 780 characters. SMS to wired recipients are limited to 160 chars, as they are being sent as "text-to-speech".
Main features:
- sends SMS to ALL german cellphone networks and text-to-speech messages to wired recipients - now you can reach nearly everyone
- supports Flash SMS
- fakes user-agent by selecting one out of currently 10 "real" agents (IE, Mozilla, Opera et al.)
- very fast and reliable message delivery
- can be modified to use with other networks
- fully emulates a web user filling in the HTML form

spamdyke is a drop-in filter for qmail to provide connection-time blacklisting, graylisting, DNS RBL checking, improved logging, and more spamdyke project is a standalone program that does not use qmail source code or require patching/recompiling qmail.
For anyone who runs a mail server, spam is a problem. Its a huge problem and its only getting bigger. Unfortunately, qmail doesnt have many facilities for dealing with spam. qmail also doesnt do good logging. The qmail logs are probably useful to qmail developers but not to system administrators. Consider:
- Qmail doesnt log with a human-readable time format.
- Qmail logs dont track usable information (like senders and recipients).
- Qmail doesnt log to a single log file, making it very difficult to track an email from connection to delivery.
- Qmail logs roll over after a set size is reached (could be a few hours, could be a few minutes).
All of these things makes qmail very difficult to troubleshoot or monitor. spamdyke solves this. It monitors incoming traffic, acting as a middleman between qmail and the remote server. It catches the sender and recipient addresses as they go by and logs them to syslog. If it sees something it doesnt like (e.g. a blacklisted sender), it cuts the connection, closes qmail and fakes the rest of the SMTP transaction with the remote server. qmail thinks the remote server disconnected normally. The remote server thinks qmail is rejecting the message. Its the best of both worlds.
Some history: DJBs ucspi-tools package includes a handy little program called rblsmtpd for checking incoming SMTP connections against a DNSRBL. Initially, this seemed like a great thing (and it was) but it didnt go far enough. Lots of spam still came through. So after extending rblsmtpd to do more and more and more things, a limit was finally reached where it wouldnt go any further. Thus, spamdyke was born.
Main features:
- Reject the connection if the remote server has no reverse DNS entry.
- Reject the connection if the remote servers reverse DNS entry does not resolve.
- Reject the connection if the remote servers reverse DNS entry contains its IP address and a prohibited keyword (like "dynamic").
- Reject the connection if the remote servers reverse DNS entry contains its IP address and ends in a country code (whats the japanese word for "dynamic"?).
- Reject the connection if the remote servers IP address is listed in an IP blacklist.
- Reject the connection if the remote servers reverse DNS entry is listed in a domain name blacklist.
- Reject the connection if the remote servers IP address is listed in a given DNS realtime blacklist.
- Reject the connection if the remote server sends data before the SMTP greeting banner is displayed (earlytalkers).
- Reject the connection if the senders address is listed in a sender blacklist file.
- Limit recipients to a maximum number per connection. (Yes, this goes against RFC 821 but legitimate mail servers retry the rejected recipients, spammers dont.)
- Graylist incoming mail to specific domains (some domains can enjoy graylisting while others do not).
- Close the connection after a set idle time.
- Close the connection after a set maximum time.
Those filters end up rejecting more than 99.9% of the incoming connections to my mail server. As a result, I receive (on average) less than one spam message PER WEEK! (Down from a high of 70+ per day.) Regular correspondance with real people has not suffered.
Graylisting deserves special mention. As of 2007, its not widely used (and therefore still effective against spammers). Heres how it works:
An incoming connection is received and the sender and recipient are identified.
A log is consulted to see if the sender has sent email to the recipient before. If so, the message is accepted. If not, the message is rejected with a temporary rejection code and a log entry is made.
When the remote mail server retries the message (usually only a few minutes later), the previously-logged connection is noted and the message is accepted.
Simple, right? After the system is activated, regular correspondents first email is delayed a few minutes. After that, there are no delays. But the spam stops because most spammers dont retry their deliveries! Even when they do, they usually change their sender address to a new (fake) one, which gets graylisted.
Graylisting is amazing and makes a tremendous difference (for now). spamdyke will also:
- Bypass all filters if the remote servers IP address is listed in an IP whitelist file.
- Bypass all filters if the remote servers reverse DNS entry is listed in a domain name whitelist file.
- Log meaningful messages to the syslog (very unlike qmails logs).
- Log all SMTP traffic to aid diagnosing problems.
Enhancements:
- This release fixes a serious bug that was causing lost mail when the remote server sent the message and disconnected in a burst without waiting for a response.
- Code has been added to translate bare line feeds into carriage return+line feeds.
- Support has been added for MUAs that send their username with their AUTH LOGIN command.

w3bfukk0r is a forced browsing tool which scans Web servers for a directory by using the HTTP HEAD command and a brute force mechanism based on a word list.

w3bfukk0r supports HTTP and HTTPS, does banner grabbing, and allows User-Agent faking.

chaostables is a package with iptables/netfilter targets that will foil network scanners. Documentation on how it works and how to reimplement it in userspace are also provided.

Special features include recognition of all nmap scan types including -sS SYN Scan, proactive slowdown of TCP FNX and UDP (50000+%), and providing back fake nondeterministic information.

tagji implements a "fake but working" tagging file system. Users can organize and retrieve documents based on the tags attached to them.
No changes to the operating system or applications are necessary.
Main features:
- automatically prompts you to tag any document you create (but only if that doc is being created in one of the dirs you specified)
- lets you store directory trees as single documents (think of, e.g., a source code tree, or a set of pictures taken at the same occasion: you just tag the directory itself, not all the files it contains)
- tag information is stored in the filename, which ensures portability (as long as you dont move your files to filesystems which only support very short filenames) and low risk of losing your documents metadata (since filesystems dont corrupt/accidentally delete the name of a file that often)

Blogbench is a portable filesystem benchmark that tries to reproduce the load of a real-world busy file server.

It stresses the filesystem with multiple threads performing random reads, writes and rewrites in order to get a realistic idea of the scalability and the concurrency a system can handle.

Blogbench was initially designed to mimic the behavior of the Skyblog.com
blog service.

4 different types of threads are started:

- The writers. They create new blogs (directories) with a random amount of
fake articles and fake pictures.

- The rewriters. They add or they modify articles and pictures of existing
blogs.

- The "commenters". They add fake comments to existing blogs in random order.

- The readers. They read articles, pictures and comments of random blogs. They
sometimes even try to access non-existent files.

New files are written atomically. The content is pushed with 8 Kb chunks in a
temporary file that gets renamed if everything completes. 8 Kb is the default
PHP buffer size for writes.

Reads are performed with a 64 Kb buffer.

Concurrent writers and rewriters can quickly create fragmentation if the
preallocation is not optimal. But it is very interesting to check how
different filesystems reacts to fragmentation.

Every blog is a new directory withing the same parent directory. Since some
filesystems are unable to manage more than 32k or 64k links to the same
directory (an example is UFS), you should not force the test to run a silly
amount of time on these filesystems.