Free nu wa hitchhiker trailor software for linux

NS WebMail project is a simple set of PERL scripts, it works using module Mail::POP3Client, and allows to send and receive MIME compliant mails.
The whole thing is "secured" using POP3 authentication, ie mail cant be send or retrieved without initial correct authentication.APOP and standard PASS authentication work.
No need of any SQL base and so on. However, better know how PERL and CGIs work ! This allows NSWM to remain simple and light, and not to require an important set of PERL modules.
NSWM now support two kinda security improvments:
- HTTP Auth: just configure your Apache to authenticate user with normal HTTP Auth. Then you
need to use indexauth.pl instead of index.html as a start page, and run NSWM in mod_perl.
It works automatically.
- Cookie stored key: the key used to encrypt the password may be stocked partially in a cookie.
This prevents bad guys from accessing other users inboxes when they used shared computers.
You have to enable this feature in the configwm.pm file, at "cookiedomain": enter your
domain to enable the feature, comment the line out to disable.
Both security features will work over HTTPS.
Supported languages
Modules exists and languages have been tested for:
- English (lang-en.pl module, core module)
- Francais (lang-fr.pl module, dev module)
- Russian (lang-ru.pl module, dev module)
- Hrvatski (lang-hr.pl module, trn module from dpavlin at rot13.org)
- Deutsch (lang-de.pl module, trn module from Tobias.Mueller at stud.uni-hannover.de)
- Norwegian (lang-no.pl module, trn module from erlingp at f00bar.fagmed.uit.no)
- Hungarian (lang-hu* modules, trn module from keve_g at mail.takarek.net)
- Swedish (lang-se.pl, trn module from hm at nool.nu)
- Czech (lang-cz.pl, trn module from svasek at nextra.cz)
- Italian (lang-it.pl, trn module from theos at bp.lnf.it)
- Spanish (lang-spl.pl, trn module from scristi at startlight.com)
- Portuguese (lang-pt.pl, trn module from luiz at pucrs.br)
- Romanian (lang-ro.pl, trn module from chally_ro at yahoo.com)
Anyone translating the langpack in another language is asked to send it us, please !
This way we can improve NSWM.
installation
1- Unzip it:
On performant UNIX (with recent gnu tar), do a tar xvzf nswm-XXXXXX.tar.gz
On Windows, use Winzip or PowerArchiver (http://www.powerarchiver.com)
2- Set up your favorite HTTP server to handle the application.
For Apache:
=> put an Alias section as /nswm for the nswm/html directory
=> put a ScriptAlias section as /nswm/cgi-bin for the nswm/cgi-bin directory
For IIS,NES:
Use the graphic interface to set it up properly. Refer to server documentation.
3- Then you have to edit configwm.pm file and specify your SMTP server ($SMTPserver variable).
Words and paths can be set up in config.pl file.
You can also choose the language.
Nota: configwm.pm template is configwm.pm.dist.
4- PERL Modules to install if not installed:
Dont forget to install them (example with Mail::POP3Client):
=> perl -MCPAN -e install Mail::POP3Client on UNIX (or see at http://www.cpan.org)
or ppm Mail-POP3Client on WNTs ActivePerl (but better see at http://www.activetsate.com)
The following modules/packages are needed:
IO-stringy,MIME-Base64,MIME-Lite,MIME-tools,MailTools,Mail::POP3Client,TimeDate,URI,CGI
(yeah, thats a lot, i know. MIME encoding/decoding isnt a simple thing...)
5- Misc install things:
Dont forget to chmod 777 (or, better, chown apache or nobody or www-data) the /var/opt/nswm/log and
/var/opt/nswm/tmp directories if you dont change those locations in the configwm.pm file.
You can do a small cron script to launch bin/nswmcron to enable the automatic cleanup of temp files (This is automatically done by the RPM). Dont forget to change the html/title.htm file....
Enhancements:
- Several improvements in mail header decoding in the inbox.
- Optional ability to report spam to spam software (tested and documented with SpamAssassin).
- Full management of the "Urgent header".

Six Sigma project is a formalized methodology which some companies use to measure and delivery quality to their customers.
Companies who participate in Six Sigma programs strive for a statistical goal of six standard deviations between the mean and the closest specification limit for whatever process is being measured.
This translates to a permissible defect or error rate of just 3.4 errors or defects of out of every 1 million "opportunities" to create that error or defect, or a success rate of 99.9997%.
How did Six Sigma originate?
A Motorola Corporation Quality and Reliability engineer by the name of Bill Smith is widely credited with devising the Six Sigma process. He had concluded a study which determined that actual Motorola product failure rates were much higher than had been predicted when the products were designed. The high failure rates translated into additional warranty repair costs for Motorola and decreased customer satisfaction.
Mr. Smith went to Motorolas CEO and convinced him that the company would benefit financially from a formalized methodology which analyzed and controlled quality and reliability processes. This process became what is known as Six Sigma.
Does Six Sigma work?
There are many large and small businesses who have implemented Six Sigma programs successfully. It is reported that the General Electric Corporation saved over $10 billion dollars in the first five years after implementing their Six Sigma program.
Enhancements:
- The CSS had a few bugs in the syntax that caused some minor display problems.

SuperBunguru is a 2d platform/arcade game.

SuperBunguru is a arcade game where your objective is jump from block to block to reach a goal at the top of a level.

To make this hard you cant return to a previous lower position. And to turn up the pace of the game blocks collapps when you stand on them too long.

SuperBunguru is inspired by Bunguru-Wa.

Image::MetaData::JPEG::MakerNotes contains random information and details on MakerNotes.

Pieces of information available after parsing the MakerNote

The result of the process of parsing the maker note is stored in a directory in the internal data structure for the APP1 Segment, whose path is "IFD@SubIFD@MakerNoteData_$format", where $format is the specific note format; the MakerNote entry in IFD0@SubIFD is then removed. This translation happens always, because there is a catch-all unknown rule for a binary makernote with very broad acceptance rules. The maker note directory contains, in addition, a special subdir with some fields reporting about the parsing process.

key content
-------- -------
ORIGINAL the raw content of the maker note (unparsed)
SIGNATURE the first few bytes which allowed the format to be chosen
ENDIANNESS the byte order chosen during parsing
FORMAT the maker note format chosen during parsing
ERROR [optional] error details, in case of failure while parsing

Supported MakerNote formats

Maker note formats are specified in a special internal hash, with a key for each format (including the unknown format). Each format entry corresponds to an anonymous hash containing information for parsing the MakerNote; the "normal" format is considered to be an IFD-like MakerNote with a next_link pointer, offsets counted from the global TIFF header and no MakerNote internal TIFF header.

key meaning or effect
--------- -----------------
signature the MakerNote signature (a regular expression)
maker the Maker signature (i.e., its name, no regex)
tags a reference to a hash for tag translations
(A) mkntstart if set, offsets are counted from the maker note start
(B) mkntTIFF if set, offsets are counted from the internal TIFF header
(C) ignore if set, the format is to be ignored
(D) nonext if set, the maker note IFD does not have a next_link
(E) endianness if set, the byte order is fixed to this value
(F) nonIFD if set, the maker note is not IFD-like

Currently, "supported" formats are described in the following table; authoritative data is indeed kept in Tables_makernotes.pl, to which the reader should refer for tag definitions and translations. Remember that both the signature and the maker fields are regular expressions matching at the beginning (the real signature corresponds to $1).

A B C D E F Maker Signature
----------- --------- -----------------
Agfa AGFA (AGFA 00 01)
Canon Canon ()
Casio_1 CASIO ()[^Q]
Casio_2 CASIO (QVC 00{3})
Epson EPSON (EPSON 00 01 00)
Foveon FOVEON (FOVEON 00{2} 01 00)
Fujifilm x FUJIFILM (FUJIFILM 14 00{3})
HPackard x Hewlett-Packard (HP)
Kyocera x x KYOCERA (KYOCERA {12} 00{3})
Kodak B x KODAK (KDK INFO[a-zA-Z0-9]* )
Minolta_1 MINOLTA ().{10}MLT0
Minolta_2 Minolta ().{10}MLT0
Konica x Minolta|KONICA ((MLY|KC|(+M){4})| 01 00{5} 04)
Nikon_1 NIKON (Nikon 00 01 00)
Nikon_2 NIKON ()[^N]
Nikon_3 x NIKON (Nikon 00 02[ 20 00] 00{2})
Olympus OLYMPUS (OLYMP 00[ 01 02] 00)
Panasonic_1 x Panasonic (Panasonic 00{3})
Panasonic_2 x x Panasonic (MKED)
Pentax_1 x Asahi ()[^A]
Pentax_2 x x Asahi (AOC 00..)
Ricoh_1 x RICOH (Rv|Rev)
Ricoh_2 x RICOH ( 00)
Ricoh_3 RICOH ((Ricoh|RICOH) 00{3})
Sanyo SANYO (SANYO 00 01 00)
Sigma SIGMA (SIGMA 00{3} 01 00)
Sony x SONY (SONY (CAM|DSC) 00{3})
Toshiba x TOSHIBA ()
unknown x . ()

References

MakerNote format details are not usually released by vendors (well, this is an euphemism: no vendor ever, to my knowledge, released any detail on its format, exception made for Sigma/Foveon). All information used for this package was collected on the Internet (and its reliability is therefore limited) or through personal tests. Some interesting sites are (not an exhaustive list at all):

General: home.arcor.de/ahuggel/exiv2/makernote.html
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/makernotes.html

Agfa: www.ozhiker.com/electronics/pjmt/jpeg_info/agfa_mn.html
Canon: www.burren.cx/david/canon.html
Casio: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
...: www.dicasoft.de/casiomn.htm
Epson: www.ozhiker.com/electronics/pjmt/jpeg_info/epson_mn.html
Foveon: Foveon is the same as Sigma, see Sigma
Fujifilm: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
......: www.ozhiker.com/electronics/pjmt/jpeg_info/fujifilm_mn.html
Kyocera: www.ozhiker.com/electronics/pjmt/jpeg_info/kyocera_mn.html
Kodak: my personal tests with my Kodak DX3900 (not IFD-like)
Minolta: www.dalibor.cz/minolta/makernote.htm
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/minolta_mn.html
Nikon: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
...: www.tawbaware.com/990exif.htm
...: www.ozhiker.com/electronics/pjmt/jpeg_info/nikon_mn.html
Olympus: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/olympus_mn.html
Panasonic: www.compton.nu/panasonic.html
Pentax: www.ozhiker.com/electronics/pjmt/jpeg_info/pentax_mn.html
Ricoh: www.ozhiker.com/electronics/pjmt/jpeg_info/ricoh_mn.html
Sanyo: www.exif.org/makernotes/SanyoMakerNote.html
Sigma: www.x3f.info/technotes/FileDocs/MakerNoteDoc.html
Sony: www.ozhiker.com/electronics/pjmt/jpeg_info/sony_mn.html

DX3900 MakerNote format

Kodak MakerNotes are written in a proprietary binary format, which is not IFD-like. So, there is no way to detect the beginning, end and type of a field; everything here was inferred through a careful comparison of the content of a set of Kodak JPEG files and their shot parameters. Fields seems to be aligned on four bytes boundaries. For the DX3900 model the endianness is always fixed to big endian. The signature regular expression is "^(KDK INFO[a-zA-Z0-9]* )", the maker is KODAK. The meaning of the tags is as follows:

BYTE ??? firmware version? This is always 3
BYTE Compression 1 = normal, 2 = 2160x1440 high compression
BYTE BurstMode 0 = off, 1 = on
BYTE MacroMode 0 = normal, 1 = close-up
SHORT PixelXDimension allowed 2160x1440, 1800x1200,
SHORT PixelYDimension / values: 1536x1024, 1080x720
SHORT Year the year value, with four digits
BYTE Month the month value (in [1,12])
BYTE Day the day value (in [1,31])
BYTE Hour the hour value (in [0,23])
BYTE Minute the minute value (in [0,59])
BYTE Second the second value (in [0,59])
BYTE SubSecond (in 130th of seconds?)
SHORT ??? ???
BYTE ??? ???
BYTE ShutterMode 0 = auto, 32 = manual
BYTE MeteringMode 0 = multi-pattern, 1=centre weight., 2=centre spot
BYTE BurstSequenceIndex index in [1,8], 0 if burst mode off
SHORT FNumber 100 times the Exif F-number
LONG ExposureTime in 10^-5 seconds
SSHORT ExposureBiasValue 1000 times the exposure bias in [-2,+2 step .5]
SHORT ??? ???
LONG ???
LONG ??? is this an estimate of the subject
LONG ??? / distance? If so, it is very rough.
LONG ??? /
BYTE FocusMode 0 = auto, 2 = close, 3 = infinity
BYTE ??? always 2
SHORT ??? ???
SSHORT PanoramaMode 0 = normal, -1 = focus at infinity
SHORT SubjectDistance (x-28)*2.54+7 looks like the distance in cm
BYTE WhiteBalance 0 = normal, 1 = fluor., 2 = tungsten, 3 = daylight
(27 bytes with unknown meaning here)
BYTE FlashMode 0 = auto, 1 = on, 2 = off, 3 = red-eyes
BYTE FlashFired 0 = yes, 1 = no
SHORT ISOSpeedMode the requested speed in {100,200,400} or zero
SHORT ??? ???
SHORT TotalZoomFactor 100 times the zoom factor in [+1,+6 step 0.1]
SHORT DateTimeStampMode 0 = none, [1,6] = the six modes
SHORT ColourMode 1 = black & white, 2 = sepia, 32 = colour
SHORT DigitalZoomFactor 100 times the zoom factor in [+1,+3 step 0.1]
BYTE ??? always zero
SBYTE Sharpness 0 = standard, 1 = sharp, -1 = soft
(808 bytes with unknown meaning here, maybe a thumbnail?)

Nemesis Utilities System or NUS for short, is a cross-platform C++ application development framework that focuses on the development of network applications, non-GUI applications, CGI scripts, database applications, and any kind of application that needs interoperability.
NUS is very modular, making it easy to maintain, debug, and deploy. The project was greatly inspired by other libraries such as Trolltechs Qt.
Enhancements:
- A security module with hash manipulation classes was added.
- A class to manipulate command-line options was added.
- The output handling classes were improved.
- Exception handling was improved.
- The XML module was documented.
- The examples were improved.

CruxPorts4Slack adapts the "ports" and "pkgmk" commands to allow the use of ports repositories for Crux with Slackware.
In the BSD Unix World a ports system means a directory hierarchy (ususally under /usr/ports)
where you can automatically build your own binary packages from source.
The advantage of a ports system is, that the built packages are optimized for your computer. Second advantage is: ports are faster available then binary packages.
In the last years ports systems became popular on Linux, too. A well-known Linux distro with a ports system is Gentoo, another one is Crux (www.crux.nu).
Being a Slackware fan, I decided to switch to Crux, because Slackware hadnt alls the packages I wanted and using ./configure && make && make install (or even checkinstall) wasnt the optimum for me.
At first I was impressed with the ports system of Crux. But building every single package, even the most basic software (e.g. util-linux), was getting on my nerves. And I didnt like the system layout of Crux (they are using devfs) as much as I liked Slackwares.
I thought "Why dont use a mix of the two". Slackware with the Crux ports system - that would be it. Crux binary packages are based on tar.gz, so are Slackware packages. So I switched back to Slack and ported the Crux port system to Slackware. Another reason for making this is, that I will use this system in the next version of DeLi Linux (www.delilinux.de).
Here is the result: With cruxports4slack you can use the crux ports system with Slackware.
Running:
pkginfo
-------
usage: pkginfo [-i|-i package]
options:
-i, --installed list installed packages and their version.
-l, --list package list files owned by the specified package
-h print help and exit
Enhancements:
- The ability to use alternative Pkgfiles was added.
- The httpup files for the contrib and opt repositories were updated.

SYNOPSIS

# To send a user to login:
use Hey::heyPass;
$heyPass = Hey::heyPass->new($yourSiteId, $yourSiteKey);
$login = $heyPass->beginSession({
successUrl => "http://$ENV{HTTP_HOST}/loginSuccess.cgi?sessionId=%s",
failureUrl => "http://$ENV{HTTP_HOST}/loginFailure.cgi?sessionId=%s",
cancelUrl => "http://$ENV{HTTP_HOST}/loginCancel.cgi?sessionId=%s"
});
print "Location: $login->{loginUrl}nn";

# To logout the user:
use Hey::heyPass;
$heyPass = Hey::heyPass->new($yourSiteId, $yourSiteKey);
$heyPass->endSession($sessionId);

# To retrieve the session data of the user:
use Hey::heyPass;
$heyPass = Hey::heyPass->new($yourSiteId, $yourSiteKey);
$session = $heyPass->getSession($sessionId);
use Data::Dumper;
print Dumper($session);

Documentation: https://heypass.hey.nu/interface/guestdocs/
If you want to have a heyPass siteId/siteKey for your application, please check to see if there is an automated way to do this (not yet at time of writing). If there still isnt, contact me (Dusty Wilson ) and I will get you started.