Floke Integrity documentation

Version 0.0.1. 2000-09-07
for
Version 0.01 of the executables
Jon Wickmann

Copyright (c)  2000 Jon Wickmann.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1
or any later version published by the Free Software Foundation;
with no Invariant Sections , with no Front-Cover Texts and with no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
Free Documentation License".

Dublin Core data in publishing:
Dublin Core attributeScheme (if any)Value
DC.TitleFloke Integrity documentation
DC.Title.AlternativeVersion 0.0.1. 2000-09-14 for Version 0.01 of the executables
DC.Creator.PersonalNameWickmann, Jon
DC.Creator.PersonalName.Addressjon.wickmann@excite.com
DC.Subjectintegrity
DC.Subjectcomputer security
DC.Subjectfile
DC.Subjectdocumentation
DC.DescriptionThis is the documentation for Floke Integrity version 0.01.
DC.PublisherJon Wickmann
DC.Publisher.Addressjon.wickmann@excite.com
DC.DateISO86012000-09-14
DC.TypeText
DC.FormatIMTtext/html
DC.Identifierhttp://www.angelfire.com/wi/wickmann/flokedoc001.html
DC.IdentifierURNNBN:no-a352
DC.SourceURNNBN:no-a352
DC.LanguageISO639-1en
DC.CoverageVersion 0.01
DC.RightsURLhttp://www.gnu.org/copyleft/fdl.html
DC.Date.X-MetadataLastModifiedISO86012000-09-14

Thanks goes to the Nordic Metadata Project (http://linnea.helsinki.fi/meta/).


Table of contents

1.0. General
1.1. Contact information
1.2. Download information
1.3. Copyright
1.4. Source code reference
1.4.1. Works by others
1.4.1.1. GNU Privacy guard
1.4.1.2. AIDE - Advanced Intrusion Detection Environment
1.5. Integrity of the archives

2.0. Goals
2.1. Features
2.1.1. Description of hash functions
2.2. Requirements and limitations

3.0. The program
3.1. The user interface
3.2. The menu
3.3. The task options dialog

4.0. Practical issues
4.1. Making and running a task
4.2. The all important report
4.3. Maintaining a bullet-proof integrity

5.0. The Future
5.1. Further development
5.2. A wish list
5.3. Know bugs
5.4. Found a bug?
5.5. Development efforts by you
5.5.1. Maintaining source
5.5.2. Maintaining distribution

Appendixes

A1. The GNU Free Documentation License
A2. The GNU General Public License
A3. Export restrictions


1.0. General

Floke Integrity has been lurking around in my head since late 1998. Due to many other time consuming projects, development couldn't start before autumn 2000. This is bad timing since I'll be far away in the period 2000.09.19. - 2001.09.21. Nevertheless I decided to release Floke now, and let it mature in the hands of its users.  This means that I can't assist in any way. However I'll try to find a web board to place on the Floke home site at http://www.angelfire.com/wi/wickmann/floke.html.
Be sure to read this documentation and understand the license, and I hope you'll be fine. Sorry, my english isn't like it used to be.

1.1. Contact information

I'll be out of reach  until 2001.09.21. so don't flood my mailbox. E-mail in the preferred priority wickmann@sensewave.com, wickmann@hotmail.com, jon.wickmann@excite.com. Privacy enhanced mail by OpenPGP/GNUPG/PGP preferred.

Make sure to check http://www.angelfire.com/wi/wickmann/contact.html, before you send any mail. Thanks.

1.2. Download information

The main point of distribution is the home page that i will try to maintain at Angelfire/Lycos http://www.angelfire.com/wi/wickmann/floke.html

Links to several FTP and HTTP sites will be available.
Else try the search engines.

1.3. Copyright

Both the program and the documentation is copyrighted by Jon Wickmann (2000).

Please refer to
A1. GNU Free Documentation License
A2. The GNU General Public License
for their respective licenses. Some of the code are copyrighted by others and licensed under the same GNU General Public License. Please see section "1.4.1. Works by others" below for further references.
 

1.4. Source code reference

The source code are included in the main zip archive as a included zip file. As for now (2000.09.12.) the source code is not well enough commented. See the web site for a more updated source archive. As the development strives forward newer versions of the source code will be published on the web site before any actual binary releases.

If you want to contribute code please see section 5.5.
 

1.4.1. Works by others

The bulk of the source code for Floke Integrity has been developed by others. Se the source archive for more details.
1.4.1.1. GNU Privacy guard
All the message digest/hash functions comes from GNU Privacy guard. The code is covered by the GNU General Public License. For credits the source mentions Ulrich Drepper (in md5.c) and Werner Koch.

GnuPG
Copyright (C) 2000 Free Software Foundation, Inc.
http://www.gnupg.org/

1.4.1.2. AIDE - Advanced Intrusion Detection Environment
AIDE is a similar programme to Floke, but for Linux (and other Unix like OS). It also uses messages digest/hash functions from GNU Privacy guard. When I couldn't figure out how to use certain functions I turned for aide to AIDE. Thus some header files and slight modifications to the GNU Privacy guard source came from AIDE. The code is covered by the GNU General Public License.

AIDE - Advanced Intrusion Detection Environment
Copyright (C) 1999,2000 Rami Lehti, Pablo Virolainen
http://www.cs.tut.fi/~rammer/aide.html

1.5. Integrity of the archives

To ensure the integrity of the archives Open PGP signatures of the archives are available at my web site.

2.0. Goals

The goal of Floke is to ensure that when a file on your system has been altered due to authorized editing, tampering or software/hardware- malfunction, you know it.

2.1. Features

Floke Integrity has a intuitive user interface, but doesn't stop there. Under the hood you can find:

2.1.1. Description of hash functions

2.1.1.1. SHA-1 (Secure Hash Algorithm)
This hash algorithm was designed by the U.S. National Security Agency. The definition is at (http://www.itl.nist.gov/div897/pubs/fip180-1.htm). For some reason the original Secure Hash Algorithm (SHA) was replaced by this version. A suggestion might be found  at (ftp://ftp.ens.fr/pub/dmi/users/chabaud/sha.ps).
2.1.1.2. RIPEMD-160
This hash algorithm was designed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel. The algorithm is assumed to be as secure as SHA-1, but lacking in its mysterious replacement. A home page is maintained at (http://www.esat.kuleuven.ac.be/~bosselae/ripemd160.html).
2.1.1.3. MD5
This hash algorithm was designed by Ron Rivest. The algorithm is no longer assumed to be a 100% secure, since a collision was found in its compression part (ftp://ftp.rsa.com/pub/pdfs/bulletn4.pdf ). I interpret this to mean that two blocks of data could yield the same hash, thus not confirming uniqueness of data.

2.2. Requirements and limitations

I've confirmed that Floke runs well on my machine, specs: Know limitations:

3.0. The program

3.1. The user interface

The user interface consists of a menu bar (See section 3.2 below). Three buttons and an area for summary reports.

The buttons:

Start:
By pressing the start button the current active task will be processed. If no tasks are active, you'll be prompted to open one.

Display report:
By pressing this button, a text reader will be invoked and the report will be displayed. If the text reader fail, you will be prompted to select an other.

Emergency stop:
The emergency stop button is only available when a task is running. By pressing it, the current running task will be terminated. Some system resources might be tied up afterwards, but a closure of Floke, will re-enable them.
 

3.2. The menu

There are five menus on the menu bar.

File menu:
The file menu has three sub menus that mainly deals with file operation. No "Save" or "Save As" capability is available, since Floke automatically saves its database when it processes the associated task.

New
The new sub menu displays the task options dialog (see section 3.3.). Where you can specify the task you want to make.

Open
The open sub menu presents an open dialog where you can chose witch Floke task/database to load.

Exit
Guess. :-)

3.3. The task options dialog

The task options dialog has four groups, and one sub-group of options.

Files
Here you can enter both the database and report file to use. The small buttons at the end of each line will display a dialog where you can select the path and file names to use.

Hash
Here you can select which message digest/hash function to use. The greyed hash functions are currently not working on you machine. (Tiger is not yet correctly implemented, anyway).

Search
In the first box you're asked for a search pattern. Enter a wild character search pattern, where asterisk (*) means several none specified characters, and question mark (?) means one none specified character. You can have several search patterns, just remember to end them with a pipe (|). You may not use more than 40 characters for your complete search pattern.

e.g. "*.exe|*.com|"   Finds every file ending on either exe or com.

In the path box, you have to select which drive to perform the search on.

Report
Here you might cross the things you want in your report. In the files sub-group you can also specify if you want to have the hashes displayed.


4.0. Practical issues

4.1. Making and running a task

The first step you have to undertake is to decide what you want to protect.
  1. Then assuming that you already have started Floke, hit the "File" menu, then hit "New".
  2. The "Task Options" dialog will now be displayed.
  3. See section 3.3, on how to fill out the task options.
  4. Press Okay to leave the "Task Options" dialog.
  5. Back in the main dialog, press "Start".
  6. The task will now be processed and saved to disk. You might interrupt this by pressing "Emergency Stop".
  7. This will take some time, so do something else. You could minimize Floke and do something else on your computer. Or if you don't like multitasking, just loaf around.
  8. When Floke has finished the Start button will be enabled again.
To check the integrity of your files again:
  1. Start Floke.
  2. Hit the Start button, you will now be prompted for the task/database to use.
  3. The task is running.
  4. When finished: inspect the report.
New files matching the old search pattern has also been added.

4.2. The all important report

You can't really stress this to much: Inspect and keep your report file. By doing this you can monitor the behaviour of your files. Some files might automatically change as a result of a process in the OS. Learn to know which files are affected by such harmless changes, so that you can tell real none authorized changes from those that are "natural" for your system.

4.3. Maintaining a bullet proof integrity

This is the hard topic. By just running Floke you want maintain any integrity at all. It is necessary that you understand how your system works. By this I mean you have to understand how your system is vulnerable to unauthorized tampering. Discover those tiny bits thoughtlessness that can corrupt your data.

Some scenarios:

Scared ? Assume that knowledge is power and educate yourself. Understand how things work, keep the edge in security, but verify new things before you deploy them. Be safe not sorry.

5.0. The Future

I will not be able to do any development one Floke until 2001.09.21. I'm sorry but this is the situation. I will not even be able to answer any mail until then either. Please see http://www.angelfire.com/wi/wickmann/contact.html for more details. However others might help and might also have released new versions. To simplify communications and to have a central meeting point, I plan to add a web board on http://www.angelfire.com/wi/wickmann/floke.html, where one might discuss Floke and announce new versions.
 

5.1. Further development

For a plan of things that I want to see in Floke, see section 5.2.
 

5.2. A wish list

I want these new features:

5.3. Know bugs

Floke can't tell you if it didn't gain access to a file. In the report file 0 is reported in that category.
See the web board on http://www.angelfire.com/wi/wickmann/floke.html for more recent bugs.

5.4. Found a bug?

Announce it on the web board on http://www.angelfire.com/wi/wickmann/floke.html.
If the bug is not resolved before 2001.09.21. mail me.
 

5.5. Development efforts by you

It would be very nice if others helped me in this development effort. Please observe the following two sub-sections.
 

5.5.1. Maintaining source

In order to maintain good source:

5.5.2. Maintaining distribution

If you changed/added source code, you probably want to distribute source and binaries before I'm back. Right?

Appendixes


A1. The GNU Free Documentation License

Version 1.1, March 2000
Copyright (C) 2000  Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you".

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage subsequent modification by readers is not Transparent. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modification. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

3. COPYING IN QUANTITY

If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections entitled "History" in the various original documents, forming one section entitled "History"; likewise combine any sections entitled "Acknowledgements", and any sections entitled "Dedications". You must delete all sections entitled "Endorsements."

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the compilation. Such a compilation is called an "aggregate", and this License does not apply to the other self-contained works thus compiled with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate.

8. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License provided that you also include the original English version of this License. In case of a disagreement between the translation and the original English version of this License, the original English version will prevail.

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

      Copyright (c)  YEAR  YOUR NAME.
      Permission is granted to copy, distribute and/or modify this document
      under the terms of the GNU Free Documentation License, Version 1.1
      or any later version published by the Free Software Foundation;
      with the Invariant Sections being LIST THEIR TITLES, with the
      Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
      A copy of the license is included in the section entitled "GNU
      Free Documentation License".
If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant. If you have no Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being LIST"; likewise for Back-Cover Texts.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.


A2. The GNU General Public License

                    GNU GENERAL PUBLIC LICENSE
                       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
                          675 Mass Ave, Cambridge, MA 02139, USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

                            Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it.  (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.)  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their
rights.

  We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

  Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software.  If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

  Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary.  To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

  The precise terms and conditions for copying, distribution and
modification follow.

                    GNU GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License.  The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language.  (Hereinafter, translation is included without limitation in
the term "modification".)  Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

  2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices
    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

    c) If the modified program normally reads commands interactively
    when run, you must cause it, when started running for such
    interactive use in the most ordinary way, to print or display an
    announcement including an appropriate copyright notice and a
    notice that there is no warranty (or else, saying that you provide
    a warranty) and that users may redistribute the program under
    these conditions, and telling the user how to view a copy of this
    License.  (Exception: if the Program itself is interactive but
    does not normally print such an announcement, your work based on
    the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code.  (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it.  For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.  However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License.  Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

  5. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Program or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

  7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all.  For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

  10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission.  For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this.  Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

                            NO WARRANTY

  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

                     END OF TERMS AND CONDITIONS

        Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) 19yy  <name of author>

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program; if not, write to the Free Software
    Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

    Gnomovision version 69, Copyright (C) 19yy name of author
    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
  `Gnomovision' (which makes passes at compilers) written by James Hacker.

  <signature of Ty Coon>, 1 April 1989
  Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs.  If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library.  If this is what you want to do, use the GNU Library General
Public License instead of this License.


A3. Export restictions

Floke Integrity makes use of message digest/hash functions which in its bare nature resembles features of stream chipers. In its present state in the source code, the functions can't be used for encryption. However, discussions on the USENET news group sci.crypt has shown that hash functions easily can be modified to stream chipers.

Wassennar export restrictions which cover my region, grants export to any software that is "In the public domain". And by the Wassennar definitions Floke Integrity is both "software" and "in the public domain". Thus any export from any Wassennar country should be okay. If other export/import restrictions apply to your region please consider them.