ferm 0.1.0a1__tar.gz

ferm-0.1.0a1/.gitignore

@@ -0,0 +1,47 @@
+# editor backups and VCS-tool droppings
+*~
+\#*#
+.#*
+.stgit*
+
+# build artifacts of the Perl reference (cd reference && make all/check)
+build
+reference/doc/ferm.1
+reference/doc/ferm.html
+reference/doc/ferm.txt
+reference/doc/import-ferm.1
+reference/ferm.service
+*.tmp
+
+# Python port (uv-managed environment, tool caches, build artifacts)
+.venv/
+# per-interpreter environments of the `matrix` nox session
+.venv-*/
+__pycache__/
+*.py[cod]
+.nox/
+.ruff_cache/
+.mypy_cache/
+.pytest_cache/
+.hypothesis/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+*.egg-info/
+dist/
+mutants/
+# atheris crash-fuzzing (nox -s crashfuzz): the working corpus accumulates
+# coverage across runs and the crash artifacts are raw reproducers; the
+# committed seeds live in fuzz/seeds/.  Promote a minimized reproducer into
+# a unit/golden test by hand rather than committing the artifact.
+fuzz/corpus/
+fuzz/crashes/
+
+# local agent/tooling directories (not part of ferm)
+.omc/
+.codegraph/
+.claude/
+CLAUDE.md
+docs/superpowers/
+.mcp.json

ferm-0.1.0a1/CHANGELOG.md

@@ -0,0 +1,223 @@
+# Changelog
+
+All notable changes to the **Python port** of ferm are documented in this
+file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/),
+and this project adheres to [Semantic Versioning](https://semver.org/).
+
+For the history of the original Perl implementation (versions up to and
+including `v2.8`), see [`reference/NEWS`](reference/NEWS).
+
+## [Unreleased]
+
+No changes yet since 0.1.0a1.
+
+## [0.1.0a1] - 2026-06-16
+
+The Python port (`src/pyferm/`). Phase 1 reproduces the Perl
+implementation's behaviour and emits `iptables` rulesets; its output is
+validated byte-for-byte against the Perl oracle kept in `reference/`.
+
+Phase 2 adds an **opt-in native `nftables` backend** behind `--nft`. The
+default backend stays `iptables`, so existing configurations and output
+are unchanged unless `--nft` is passed.
+
+### Added — packaging
+
+- **PyPI wheel and sdist** (`pip install ferm`). Built with `uv build` and
+  published via Trusted Publishing — no token secrets stored in CI. The
+  package name on PyPI is `ferm`; the `dns` extra (`pip install ferm[dns]`)
+  pulls in `dnspython` for full record-type support in `@resolve()`. Version
+  is derived from the `py-v<PEP440>` git tag through `hatch-vcs`, so the
+  wheel version and the tag are always the same source.
+- **Native `.deb` package** (`pyferm`). Installs `/usr/bin/ferm` and
+  `/usr/bin/import-ferm` and declares `Provides: ferm`, `Conflicts: ferm`,
+  `Replaces: ferm` so it is a drop-in replacement for the Perl `ferm` Debian
+  package — installing `pyferm` removes the Perl package and satisfies any
+  dependency that requires `ferm`. The `.deb` ships a starter
+  `/etc/ferm/ferm.conf` (DROP policy on `INPUT`; only SSH on port 22 by the
+  `ssh` service name and the RFC 4890 ICMPv6 essentials subset are accepted)
+  and a `ferm.service` unit that is **not** enabled or started on install
+  (anti-lockout). Drop-in fragments under `/etc/ferm/ferm.d/*.conf` are
+  merged at runtime. See the installation section of the
+  [README](README.md) for safety notes before enabling the service.
+- **Standalone binary distribution** for **Linux x86_64** (glibc **2.28**
+  or newer), published as `ferm-<version>-linux-x86_64.tar.gz`. It bundles
+  its own Python runtime and `dnspython`, so the target host needs no
+  Python install; it does not bundle `iptables` / `nft`, which must be
+  present at runtime. Unpacking yields a `ferm.dist/` directory with the
+  `ferm` binary and an `import-ferm` symlink. **Install invariant:** the
+  binary loads bundled shared objects from its own directory, so keep it
+  inside `ferm.dist/` and link to it (don't copy the bare binary out);
+  unpack into a root-owned, non-world-writable directory. See the
+  installation section of the [README](README.md) for the full provenance
+  and threat-model notes.
+- **Dynamic release version from git tag (`hatch-vcs`).** The distribution
+  version is derived from the `py-v<PEP440>` git tag via `hatch-vcs`, so
+  the wheel, sdist, binary, and `.deb` all carry the same version as the tag
+  with no manual edit required. The build verifies the tag and the derived
+  version agree before publishing.
+- **Bundled third-party license texts.** The tarball ships a `LICENSES/`
+  directory with the verbatim license text of every native library frozen
+  into the binary (CPython, dnspython, OpenSSL, libffi, bzip2, xz, mpdecimal)
+  plus a manifest. The build fails closed if any bundled library has no
+  license text, so the artifact is never published without its notices.
+- **glibc-floor release gate.** Releases now load the packaged binary on a
+  pinned glibc 2.28 image (not the build image), so a symbol above the
+  advertised floor fails the release rather than a user's old distro.
+
+### Added — Phase 2 (native nft backend)
+
+- **Opt-in `--nft` native nftables backend.** Translates the structured
+  rule into a native nft ruleset and applies it atomically via
+  `nft -f -`. It uses the nft *text* wire only and has no dependency on
+  nft's JSON / `libjansson` build. `--nft` is strictly opt-in; the
+  default remains the `iptables` backend.
+- **`--nft` validates the ruleset with `nft -c -f -` before applying.**
+  The applier runs nft's text `--check` (a netlink validation that
+  installs nothing) first and only pipes the real `nft -f -` once it
+  passes, surfacing nft's own diagnostic *before* any kernel change
+  instead of a generic apply failure.
+- **`--nft --interactive --shell` emits a working anti-lockout net.** The
+  generated shell script snapshots ferm's table (`nft list table`) before
+  applying, and after the confirmation timeout deletes the freshly-applied
+  table and reloads the snapshot (`nft -f`) — mirroring the live rollback,
+  so an admin who never confirms is restored. The script also echoes the
+  rollback to stderr, so the otherwise-silenced restores (`2>/dev/null`)
+  no longer revert a timed-out admin without a word.
+
+### Changed — Phase 2 (native nft backend)
+
+- **`policy DROP` semantics differ under `--nft`.** The nft backend owns
+  a single `table <family> ferm` and does not take over the monolithic
+  kernel `INPUT` / `FORWARD` / `OUTPUT` chains the way the flat iptables
+  ruleset effectively does. ferm's base chains therefore coexist with
+  other tables' base chains on the same hook (ordered by priority), so a
+  packet may be accepted by a higher-priority foreign chain before
+  reaching ferm's chain. A `policy DROP` in `table ip ferm` consequently
+  behaves differently from iptables' monolithic `INPUT DROP`. This is the
+  documented, expected behaviour of the own-table model, not a bug;
+  admins who need the exact monolithic-DROP semantics should stay on the
+  default `iptables` backend.
+
+### Removed / not supported — Phase 2 (native nft backend)
+
+- **`@preserve` is not supported by the `--nft` backend.** Using
+  `@preserve` together with `--nft` is a clean, explicit error rather
+  than a silent no-op. This is a deliberate, opt-in-backend regression;
+  the default `iptables` backend supports `@preserve` exactly as before.
+
+- **Port-bearing NAT requires a transport match under `--nft`.** A NAT
+  verdict that maps a port (`DNAT to ...:port`, `SNAT to ...:port`,
+  `REDIRECT`/`MASQUERADE to-ports`) with no preceding `proto tcp`/`udp`
+  match is now a clean ferm error at translate time, because nft rejects
+  such a mapping at apply (`transport protocol mapping is only valid after
+  transport protocol match`) and would otherwise force a rollback. Add a
+  protocol match to the rule.
+
+### Security — Phase 2 (native nft backend)
+
+- **`--nft` operands are escaped or validated before they reach the save
+  script.** A config value carrying whitespace, `;`, `#`, or a double
+  quote could previously break out of its nft token — for example
+  `saddr "1.2.3.4 accept;#" DROP` rendered as
+  `ip saddr 1.2.3.4 accept;# drop`, silently turning a `DROP` rule into
+  `accept` (a form `nft -c` validates without complaint). Interface names
+  are now emitted as escaped nft quoted strings (the `*` wildcard is
+  preserved); addresses, ports, **protocols**, rate limits, and chain
+  identifiers are grammar-validated, raising a plain ferm error rather
+  than a ruleset nft would mis-apply. The protocol operand specifically
+  (`proto "tcp accept;#" DROP` → `meta l4proto tcp accept;# drop`) was the
+  last unguarded sink and is now validated like the others. The default
+  `iptables` backend already escaped these operands and was never affected.
+- **A failed rollback snapshot no longer degrades into a destructive
+  delete.** The `--nft` rollback deletes ferm's own table when there is no
+  previous snapshot (a genuine first run); a transient `nft list table`
+  failure on an *existing* table is now distinguished from a real first run
+  (by its non-`ENOENT` error) and aborts before any kernel change, instead
+  of being mistaken for "no previous table" and deleting it on rollback.
+
+### Fixed
+
+- nft backend: render `reject-with tcp-reset` in the `ip6` family (it was
+  only mapped for `ip`), matching the default backend and nftables' own
+  family-agnostic `reject with tcp reset`.
+
+### Changed
+
+- `dnspython` is now an optional dependency (`pip install pyferm[dns]`).
+  Without it, `@resolve` uses the system stub resolver (`getaddrinfo`) and
+  supports only `A`/`AAAA` records; `NS`/`MX` and other types raise a clear
+  error. **Migration:** installs that relied on the previously-transitive
+  `dnspython` get the stub backend after upgrading; reinstall with
+  `pyferm[dns]` to restore `NS`/`MX` support.
+
+### Added — Phase 1 (faithful port)
+
+- **Configuration language front end** ported from Perl: tokenizer and
+  lazy token stream, the recursive-descent `enter()` parser over blocks,
+  scopes and keywords, copy-on-write variable/function/array scoping, and
+  deferred value realization (`@resolve()`, `@ipfilter()` and friends
+  expand late).
+- **Module-definition registry** and the compact option-encoding DSL
+  (`add_proto_def` / `add_match_def` / `add_target_def` equivalents), so
+  supported netfilter modules carry over from the Perl tables.
+- **Rule assembly** — rule structure, unfolding into the cartesian product
+  of option lists, `format_option` and byte-faithful `shell_escape`.
+- **Per-family domains and the frozen `Options` model**, with the
+  domains → backend injection seam.
+- **iptables backend** with both execution paths: `--fast` (build a save
+  file and pipe it to `iptables-restore`, atomic) and `--slow` (one
+  `iptables` call per rule), plus `--shell` script emission.
+- **CLI and top-level flow**, including `--noexec`, `--lines`,
+  `--interactive` rollback with confirmation timeout, and the
+  `ip` / `ip6` / `arp` / `eb` families.
+- **`import-ferm`** — converts an `iptables-save` dump into a ferm
+  configuration (save → ferm → save round-trip).
+- **`@resolve` name resolver** backed by `dnspython`.
+
+### Testing & tooling
+
+- **Golden-file test harness** validated against the Perl oracle, with
+  canonicalisation of the non-deterministic table/chain output order.
+- **Differential fuzzing against the Perl oracle** (Hypothesis):
+  tokenizer, `shell_escape`, import lexing, backtick splitting, `@substr`,
+  option tokens, previous-state reader, and whole grammar-generated
+  configs — driving fixes for `\s` Unicode handling (`re.ASCII`), Perl
+  numification, the `substr`/undef model and byte-faithful save-dump
+  regexes.
+- **Real-world config corpus** compiled against the oracle (fast + slow).
+- **`atheris` crash fuzzing** of both parsers and a **containerised
+  anti-lockout e2e** for `--interactive` (both opt-in), plus a periodic
+  **`mutmut` mutation** session.
+- **Containerised data-plane e2e** (`nox -s datapath_e2e`, opt-in): drives
+  real traffic with `nmap --reason` / `ncat` through ferm-installed rules
+  across a three-netns topology, asserting ACCEPT / DROP / REJECT / state /
+  NAT behaviour and parity between the `--nft` and default backends. An
+  extensible distro matrix (`nox -s datapath_e2e_matrix`) reruns the same
+  suite on Debian (bookworm + trixie), Ubuntu, Fedora, Arch, Rocky and
+  openSUSE Leap, detecting the package manager (apt / dnf / apk / pacman /
+  zypper) so adding a distro is a one-line entry.
+- **Diagnostics parity** goldens pinning stderr for negative / params /
+  warning cases.
+- **Byte-faithful I/O**: config, backtick, zonefile and `--def` (`argv`)
+  input read as latin-1 bytes and carried across the CLI, restore and
+  `import-ferm` boundaries.
+- **`MAX_BLOCK_DEPTH`** bound on parser block nesting and **`MAX_VALUE_DEPTH`**
+  bound on value-reader nesting, both failing with a located diagnostic
+  instead of a stack overflow.
+
+### Project infrastructure
+
+- Python project scaffolded at the repo root (`uv` + `src-layout`,
+  `hatchling`), declaring support for Python **3.11–3.14**.
+- The original Perl implementation relocated to `reference/` as the
+  semantic oracle.
+- `nox`-orchestrated gates (lint, tests, typecheck, coverage floor,
+  matrix, fuzz, build, deps-lowest, workflow lint) wired into a binding
+  `preflight` and into GitHub Actions CI (static checks split out, patch
+  gate on PRs, weekly audit + Dependabot).
+
+[Unreleased]: https://github.com/6RUN0/ferm/compare/py-v0.1.0a1...develop
+[0.1.0a1]: https://github.com/6RUN0/ferm/releases/tag/py-v0.1.0a1

ferm-0.1.0a1/COPYING

@@ -0,0 +1,339 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 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 Lesser 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
+
+            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) <year>  <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.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 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) year 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 Lesser General
+Public License instead of this License.