Free reporting credit card fraud software for linux

Kexi Report Part is a reporting component for Kexi 1.6 based on OpenRPT 1.2.
Main features:
- A report viewer for Kexi
- An external report designer (KexiReportWriter) based on the OpenRPT writer program
Known Working Features
- Page Header
- Page Footer
- Report Header
- Report Footer
- Detail section
- Labels
- Lines
- Fields
- Page Browser
How To Create Report
1. Install the component following the instructions in INSTALL
2. Run KexiReportWriter to start designing a report
3. Select Database->Connect to DB
4. Browse to an existing Kexi Database and open it
5. Create a new report (File->New)
6. Assign a data source to the report (Document->Properties)
7. Create the report using labels/fields/lines
8. Assign columns to the field objects (Double click for properties)
9. Save the report. (Database->Save to DB)
10. Load the database in Kexi and double click the report to view it
Enhancements:
- Removed requirement to have kexi source available to install the plugin.Done this by including the needed kexi headers in the package. Only downside is that kexi 1.1.3 (from koffice 1.6.3) is required.

Plone Error Reporting is a project which facilitates the submission of useful bug reports to Plone.
PloneErrorReporting replaces default_error_message and prefs_error_log_showEntry with pages that facilitate the submission of useful bug reports to Plone.
It is designed with the goal of improving the information provided by bug reporters.
To see PloneErrorReporting in action, first install the product, then create a python script called imabug in the ZMI that contains the single line
raise AttributeError, bad attribute
Now, while still authenticated, load the page http://mysite/imabug. You should see a step-by-step procedure for reporting bugs at the bottom of the error page as long as you are logged in as a Manager. Similarly, when you view bugs in the Plone error log, you will see the bug submitting procedure.
Enhancements:
- Moved the product to use its own translation domain. This fixes an issue were half-translated sentences showed up in the templates.

Asterisk Live CF card is, clearly, a compact flash install of asterisk that will give you a complete, running system similar to that of the asterisk live CD.

Indeed most things are the same although there have been some additions and changes.

To install the CF you will need some way of getting the image onto the card. Generally this can be done with a USB CF card reader using

dd if=asterisk-cf-b01 of=/dev/sda bs=1k count=64000

Useful things to know

1. The cf install currently assumes its hda (1 2 and 3) so youll need to put it in as your primary master using your CF->IDE adaptor, this will be more automagical in the future

2. example configs are stored on hda3 along with a new feature script called remoteconfig. This will allow you to update the configuration/OS automatically on boot from a remote webserver. More detail on how to use this feature will appear at http://www.automated.it/asterisk be sure to read any notes there first.

3. At the minimum youll need a 64mb CF card but you can use a larger one if you wish and create futher partitions. Currenly when you create the CF from the image the following partitions exist

Disk /dev/hda: 8 heads, 32 sectors, 490 cylinders
Units = cylinders of 256 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 33 4208 83 Linux
/dev/hda2 34 354 41088 83 Linux
/dev/hda3 355 490 17408 83 Linux

4. Once booted you will need to make changes to the files in /dev/hda3/astlive-example, particularly networking and the zapata/zaptel configs. Note, if you rename the astlive-example directory to astlive then on the next boot the files will be copied and activated on the running system automatically. Using the example astlive directory includes a PASSWORD CHANGE for root from EPPING to epping (without quotes) as a demonstration. At the minimum you MUST change the networking to suit your environment, since they will change to what is in this directory too.

5. All partitions on the CF are unmounted after boot so if you need to work on them, you will need to specifically mount them.

6. Ive tested E100P, X100P and TDM40B cards using this install, and would be interested to hear of other cards proven to be working.