Free pain olympics software for linux

The programming of measurement instruments can be real pain. There are many different protocols, sent over many different interface and bus systems. For every programming language you want to use, you have to find libraries that support both your device and its bus system.
In order to ease this unfortunate situation, the VISA [1] specification was defined in the middle of the 90ies. Today VISA is implemented on all significant operating systems. A couple of vendors offer VISA libraries, albeit mostly in binary form.
These libraries work together with arbitrary peripherical devices, although they may be limited to certain interface devices, such as the vendors GPIB card. Virtual Instrument Software Architecture
The VISA specification has explicit bindings to Visual Basic, C, and G (LabVIEWs graphical language). However, you can use VISA with any language capable of calling functions in a DLL. Python is such a language.
PyVISA project is a VISA binding for Python. In relies on an external library file that you can download from your interface vendors web pages (National Instruments, Agilent, etc). PyVISA implements a convenient and Pythonic access to this library in two layers:
1. First, there is the lower level vpp43, which directly calls the VISA functions from Python. See the PyVISA low-level implementation for more information.
2. On top of it, an object-oriented Python module has been created called visa simply. In case of doubt, use visa because it is easier and more convenient. vpp43 is only for people who need full control or the official VISA functions for some reason. See the PyVISA manual for more information.
Enhancements:
- PyVISA can now cope with older VISA implementations, too.

GIMP circle brushes provides circle brushes for use as "rubber stamps" in the GIMP.

GIMP circle brushes can be used with one click instead of creating outline circles by making a circle, filling with black, shrinking, and filling with white.

The following pixel sizes are provided: 6, 12, 15, 20, 24, 30, 40, 50, 60, 80, 100, 140, 200, 300, 400, 500, and 600.

Circle brushes are my third brush collection for use in the GIMP.

It was brush week for me.

Making circles is a bit of a pain with the GIMP. I know the Make a circular selection,
fill it black, shrink it, fill it white thingy -- but come on already... if I can rubber stamp a
premade circle brush where I need it instead, wouldnt that be kinda nice?

These were fairly easy, in theory. I had to add a bit of extra feathering to the above technique to get nice circles in all the sizes. Also several 45-degree rotations which smoothed out a lot of upper-end noise.

I also tried exporing from Inkscape, but the paths I converted to bitmaps did not work out as well as I had hoped and wound up sticking with the GIMP to create all
of them.

Sizes I made are:

6,12,15,20,24,30,40,50,60,80,100,140,200,300,400,500 and 600.

Use them for anything youd like. If you redistribute them, please include this file.

I post these, and perhaps make updates, at gimphelp.org. All the items will also be included (in png format) at wpclipart.com, the Public Domain clipart site.

Installation:

Stick them in the GIMP brushes folder and either "refresh brushes" or restart the GIMP. I put them in the system-wide folder, on my Slackware machine this folder is located at: /usr/share/gimp/2.0/brushes

You should also have a local brushes folder at: ~/.gimp-2.x/brushes

log_analysis is a log file analysis engine that extracts relevant data for any of the recognised log messages and produces a summary that is much easier to read.
Main features:
- Logs contain lots of extraneous stuff that I want to be logged, but that I dont want to sift through when I review logs (ie. routine, error-free daemon operation.)
- Logs contain a lot of repetition, which drowns out the interesting entries.
- Noting repetition can be tricky because each entry usually has extra features to make it unique, such as a date, maybe a PID (ie. for syslog), and maybe application-specific information (ie. sendmail queue IDs.)
- One needs to remember to review them. :)
- One needs to be root to looks at logs for some OSs.
- On most systems, looking at the logs for just one day can be a pain.
- If I attack each box I deal with and write a separate script to do all this, Ill waste a lot of time duplicating effort.
- Writing patterns is a pain even if you know regular expressions.
log_analysis is my solution to these problems. It goes through several different kinds of logs (currently syslog, wtmp, and sulog), over some period (defaults to yesterday). It strips out the date and PID, and throws away certain entries. Then it tries each entry against a list of perl regular expressions. Each perl regular expression is associated with a category name and a rule for extracting data. When theres a match, the data-extracting rule is applied, and filed under the category.
If a log entry is unknown, its filed under a special category for unknowns. Identical entries for a given category are sorted and counted. Theres an option to mail the output, so you can just run it out of cron. You can also save a local copy of the output. If you prefer to PGP-mail yourself the output, you can do this, too. The whole thing is designed to be easily extended, complete with an easy plug-in interface. The default mode is for reporting, but it also "real" and "gui" modes for continuous monitoring, complete with action support. Oh, and you can edit patterns in a GUI that helps write regular expressions quickly and easily.
Security
The program needs to run with permissions to read your log files in order to be useful, which usually means root. It does not default to SUID root, and I recommend not making it SUID, so just run it as root (ie. manually or out of cron). Ive tried to avoid temp files everywhere that I can, and in the one case where I do use a temp file, I make sure to use the POSIX tmpnam function instead of trying to make up my own temp file algorithm. The default umask is 077. If you use action commands, there is nothing to stop you from using parts of the log message in insecure ways, so for goodness sake, be careful.
Local extensions
log_analysis already has lots of rules, but chances are that you have log entries that arent already covered. So, log_analysis can easily be extended via a local config file, as documented in the log_analysis manpage. Theres even an easy way to do modular plug-ins.
Enhancements:
- This release includes a "find" feature in the GUI, various bugfixes, and assorted minor features.

THC-Dialup Login Hacker is a tool for penetrating dialup modems.

All you need is UNIX and minicom. Have fun with this little release!

The internet is not the only door into a network. In this new days, wavelans are becoming popular, in old days, there were dial-in modems. But today, dial-in modems are still present in any company.

While tools for wardialing (scanning phone numbers for modems by dialing every number and checking if theres a carrier) are available for all operating systems for years, there were only a very few tools for trying to guess login/passwords against modem carriers, and they were all for MS-DOS only. Years ago, I wrote such a tool called LOGIN-HACKER, which is still in use by many people, just because theres no real choice.

About 5 years ago I completely moved from MS-DOS to UNIX (Linux and OpenBSD) so executing penetration tests became a pain in the ass for modem login hacking. Finally I wrote some scripts to hack into modem carriers for Unix as well.

To make it flexible and portable, I chose not to write my own terminal program and scripting language, like I did with LOGIN-HACKER. I just use simple Minicom scripts. And they are very effective! Also they could include more commands to interact with the operating system while the script is running, I made it possible, to autodetect almost any prompt, and detect if a login/password, or password only prompt was successfully passed or not.

DGNLib is a small C/C++ library for reading and writing DGN files.
Building:
This is a preliminary source distribution, and I have not gone to any pains to make it easy to configure and build. To build please do the following:
1. Update cpl_config.h to represent your platform accurately. Generally all that matters is to #define WORDS_BIGENDIAN on big endian platforms. The rest can likely be ignored.

2. Compile the sample program. On unix this can be accomplished something like:
% gcc dgndump.c *.cpp -lm -o dgndump
Enhancements:
- This release adds support for Bsplines, shared cell definitions, and text nodes.
- 3d solids and surfaces have been fixed.

Dataxi project is a collection of tools for developing form-based information systems. Dataxi enables one to quickly build an application based on forms with which the user can access the underlying database in order to query, read, edit and write. Dataxi is the link between the user interface and the database.
Dataxi is an OS and enviroment independent product. It follows HTML and SQL standards to such extend that interoperability with all browsers and database backends should be supported.
Dataxi runs on all major operating systems as is or only with minor changes in ini -files.
The purpose of Dataxi is to take the pain away from the most boring phase in the data access application development: user interface designing and programming. Ones you have defined the layout of the form and location for columns, you are done, unless you prefer setting data validation and output format features and other niceties.
A database is a structured collection of data. It may be anything from a simple shopping list to a picture gallery or the vast amounts of information in a corporate network. To add, access, and process data stored in a computer database, you need a database management system such as MySQL. Since computers are very good at handling large amounts of data, database management plays a central role in computing, as stand-alone utilities, or as parts of other applications.
Enhancements:
- This version works with both PHP 4 and 5.