brontes3d-rubycas-server 0.8.0.20090812

data/CHANGELOG.txt

@@ -0,0 +1 @@
+See History.txt

data/History.txt

@@ -0,0 +1,271 @@
+=== 0.8.0 :: In Progress...
+
+* NEW:
+  * Support for localization via Ruby-GetText. 
+    See http://code.google.com/p/rubycas-server/wiki/Localization 
+    for details. [antono]
+  * Switched to Picnic 0.8.x, so RubyCAS-Server is now based on Rack
+    and Camping 2.0 and is now compatible with Passenger Phusion
+  * Added new SQL authenticator (sql_rest_auth) compatible with the
+    restful_authentication Rails plugin. [antono]
+
+* FIXED:
+  * Fixed weird problems with loading controllers when using older versions of 
+    activesupport and/or rubygems.
+  * Failure to connect to a service during a single sign out request is now
+    handled gracefully.
+  * Required gem dependencies have been re-enabled in the gemspec.
+  * Authlogic authenticator files added to gemspec. [rajiv]
+
+=== 0.7.1 :: 2008-11-10
+
+* Fixed dependency loading problems introduced by upstream changes in RubyGems 
+  1.3.1.
+
+=== 0.7.0 :: 2008-11-04
+
+* NEW:
+  * Implemented single-sign-out functionality as specified in CAS 3.3.  See
+    http://www.ja-sig.org/wiki/display/CASUM/Single+Sign+Out.
+  * It is now possible to configure Authenticators to return extra attributes
+    to CAS clients alongside the username. For an example of how to do this see
+    the included SQL authenticator. Also have a look at:
+    http://groups.google.com/group/rubycas-server/browse_thread/thread/5eade3793cb590e9
+    Note that extra attributes of type other than String or Numeric are serialized 
+    into YAML format before being sent along to the client.
+  * Added an MD5-password version of the SQL authenticator for Drupal and any other
+    database that stores its passwords in hashed form (thanks malcolmm).
+  * Added new Google authenticator for authenticating against Google/GMail
+    accounts.
+       
+* CHANGED:
+  * Service URIs are now automatically normalized. For example, if the service 
+    URI given to the server has a 'ticket' parameter, the ticket will now be 
+    automatically stripped. This is to avert any possible issues raised by 
+    misbehaving CAS clients (the CAS ticket should never be part of the service 
+    URI). Same goes for other CAS-related parameters like 'service', 'renew',
+    and 'gateway'. Additionally, the trailing '/' and '?' characters are
+    automatically stripped from URLs, since, for example, "http://google.com/"
+    is almost certainly equivalent to "http://google.com".
+  * The expire_sessions config variable is now respected -- ticket granting
+    ticket cookies are set with an expiry datetime, so that the SSO session
+    is effectively terminated once the ticket_granting_ticket_expiry period
+    is reached.
+  * If present, the HTTP_X_FORWARDED_FOR header is used for recording the
+    client's address. This is useful when the server is running behind a reverse
+    proxy, but it should not be considered authoritative since it can be
+    easily spoofed.
+  * The 'service' field in the 'casserver_st' table has been changed from
+    VARCHAR(255) to TEXT in order to accomodate service URIs longer than 255
+    characters (fixes issue #46).
+  * The CAS XML responses are no longer whitespace-formatted (i.e. Markaby's
+    auto-indentation has been turned off). Apparently the whitespace was
+    causing problems with mod_auth_cas. See:
+    http://groups.google.com/group/rubycas-server/browse_thread/thread/e482fe09999b73d3
+  * When used without pre-authentication, the LDAP authenticator now tries to 
+    bind by searching for the given username in the LDAP directory based on the 
+    configured username_attribute. Prior to this change the authenticator
+    attempted to bind with the LDAP server by assuming that the username credential
+    matches the user's CN. This is no longer the case.
+  * CAS responses to invalid requests (for example where required parameters
+    are missing or incorrect) will now have HTTP status code 422. Internal server
+    errors (where the server rather than the client is at fault) have error 500.
+    Previously most responses had error code 200, regardless of their contents.
+    
+* FIXED:
+  * Fixed logout action to work properly with ActiveRecord 2.1 (eager loading behaviour
+    was changed upstream forcing a change to the way we look for ProxyGrantingTickets
+    to delete on logout).
+  * When running under Mongrel, the USR2 signal should now restart the server as 
+    expected -- however currently this only works when the server is running
+    in the foregaround. When daemonized, USR2 will shut down the server without
+    restarting (see issue #58).
+  * Fixed activerecord/activesupport gem load problems, hopefully once and for all
+    (however picnic-0.7.0 is now required).
+
+=== 0.6.0 :: 2008-03-28
+
+* Much of the supporting functionality that makes RubyCAS-Server
+  act as a well-behaved Linux service has been abstracted out
+  into its own library. This new library is called Picnic and is
+  now a gem dependency for RubyCAS-Server. You can find out more about
+  it at http://code.google.com/p/camping-picnic/.
+* The logout action will now accept a 'destination' parameter in lieu of
+  'service'. This means that if a 'destination' parameter is given with
+  some URL, the logout action will show the login form, allowing the user
+  to immedietly log back in to the service specified by 'destination'.
+* The logout action will now accept a 'url' parameter. If given, the logout
+  page will show a message indicating that the CAS session has been terminated
+  and instructing the user to click on a link to follow the given URL. If the
+  'url' parameter is given, the login form will NOT be shown on the logout
+  page (see above).
+* When an authentication failure occurs (because the user submitted
+  invalid credentials or the login ticket is missing), the server
+  now returns a 401 (Unauthorized) response instead of 200.
+* An encryption-enabled version of the SQL authenticator is now
+  available. For more info have a look at:
+  http://code.google.com/p/rubycas-server/wiki/UsingTheSQLEncryptedAuthenticator
+* Better compatibility with Oracle databases. The database migration 
+  no longer tries to create tables with long names when long
+  table names are not supported by the underlying database connector
+  (issue #15).
+* The server now automatically removes leading and trailing whitespace from
+  the username entered by users. Passwords however are left intact, with no
+  whitespace removed.
+* The server can now be configured to automatically downcase the
+  username entered by users (dowcase_username option). So if a user
+  enters "JSmith", the system will convert it to "jsmith" if the
+  downcase_username option is set to true.
+* The server can now be made to bind to a specific address. See the
+  :bind_address option in the config.example.yml file.
+* Fixed bug with ActiveRecord 2.0.2 where service tickets were not
+  being given a type (issue #37).
+
+=== 0.5.1 :: 2007-12-20
+
+* Tickets generated by the server should now be a lot more secure.
+  The random string generator used for generating tickets now uses
+  Crypt::ISAAC. Tickets have also been extended in length; STs, PTs
+  and LTs can now extend up to 32 characters, and PGTs and PGT-IOUs 
+  up to 64.
+
+=== 0.5.0 :: 2007-09-20
+
+* Gateway requests should now be handled correctly. When the request to the
+  login page is made with gateway=true as one of the parameters, the CAS
+  server will immediately redirect back to the target service along with
+  a service ticket if an SSO session exists for the user (or without a
+  service ticket if there is no pre-existing SSO session). 
+  Note that if you are using RubyCAS-Client and want gatewaying, you will 
+  need to upgrade it to 1.1.0 as gatewaying was broken in prior versions.
+* If gateway=true is specified as part of the logout URI, the server will
+  log the user out and immediately redirect them back to the specified
+  service. In other words, you can now do "gatewayed logouts" as well
+  as logins.
+* A login ticket can now be remotely requested from the server by placing
+  a POST request to '/loginTicket'.
+* The login view can now be made to return only the login form. This is
+  done by adding the 'onlyLoginForm' parameter to the '/login' request.
+  Optionally, a 'submitToURI' parameter can be supplied to force the login
+  form to submit to the given URI (otherwise the server will try to figure
+  out the full URI to its own login controller). This functionality may be
+  useful when you want to embed the login form in some external page, as
+  an IFRAME otherwise.
+* Custom views can now be used to override the default Markaby templates
+  by specifying a 'custom_views_file' option in the configuration. See
+  custom_views.example.rb. [jzylks]
+* Table names have been shortened to work with Oracle. A migration has
+  been added that should do the shortening for you the first time you run
+  this new RubyCAS-Server version.
+* Multiple authenticators can now be specified. During authentication,
+  credentials are presented to the first authenticator, then the second,
+  and so on, until the user is validated by any one authenticator or fails 
+  validation for all of them. [jzylks]
+* When using webrick, you can now run with SSL disabled by omitting the 
+  ssl_cert and ssl_key parameters.
+* Changed incorrect MySQL example database configuration -- option should
+  be 'host:' not 'server:' (issue #22).
+
+=== 0.4.2 :: 2007-07-26
+
+* The LDAP/AD authenticator has been largely re-written. The code is a bit
+  cleaner now, and should work better with non-Active Directory LDAP servers
+  (although this has yet to be tested since I don't have access to a non-AD
+  LDAP server).
+* The validate() method in your authenticators now receives a :service element
+  (in addition to :username, and :password). This is simply the service
+  url (if any) specified in the user's CAS request. If you call 
+  read_standard_credentials(credentials) at the top of your validator, the value
+  will also be available as @service along with @username and @password.
+* By request, a :username_prefix option has been added to the ldap 
+  configuration. If entered, this string will be automatically prefixed to 
+  the username entered by the user.
+* A bug having to do with handling authenticator errors has been fixed.
+  Any authenticator error messages should now be correctly shown on the
+  login page.
+* Minor improvements to error messages having to do with login tickets.
+  They're a bit more prescriptive now, explaining to the user what steps
+  they should take to correct the error.
+
+=== 0.4.1 :: 2007-06-07
+
+* This release restores compatiblity with older versions of rubygems
+  (pre-0.9.0). To achieve this, we alias the 'gem' method to the old 
+  'require_gem' if 'gem' is not already defined.
+* rubycas-server-ctl will now quiety delete an orphaned .pid file 
+  instead complaining loudly and refusing to start up.
+* Fixed minor bug in rubycas-server-ctl that sometimes incorrectly reported
+  startup problems when in fact the server had started just fine.
+
+
+=== 0.4.0 :: 2007-06-05
+
+* Added rubycas-server-ctl script for controlling daemonized server.
+* rubygems-0.9.0 or later is now required.
+* Added system startup script to be used in /etc/init.d on Linux systems.
+* Authenticator can now be loaded from an external file using the 'source'
+  configuration option.
+* Better preemptive detection of startup problems with mongrel.
+* User now sees an error message if the service URI is not a valid URI (i.e.
+  if it's not URI-encoded or otherwise malformed).
+
+
+=== 0.3.0 :: 2007-03-29
+
+* Fixed glaring security problem with LDAP/AD Authenticator where under some
+  circumstances blank passwords were accepted as valid.
+* Autocomplete has been turned off on the password field for better security.
+  In the future we may allow autocomplete to be re-enabled using a
+  configuration setting.
+* When the user visits the login page and is already authenticated (i.e. they
+  have a valid ticket granting cookie), a message is shown at the top 
+  indicating that they are already logged in.
+* sqlite3-ruby is no longer required by the gem as a dependency.  The user 
+  must now install it manually prior to installing rubycas-server. The
+  building of sqlite3 native extensions appears to be somewhat flakey
+  and probably defeats the original purpose of using it (which was
+  to have a CAS server up and running with no additional DB configuration).
+  We will use MySQL as the default database adapter instead, since it does
+  not require additional libraries and many users will have a MySQL server
+  already available.
+* Fixed bug that was causing all proxy-granting tickets to be deleted whenever
+  any user logged out. Only the PGTs for the user that is logging out are now
+  being deleted.
+* Trailing slashes in service URLs are now ignored when validating service
+  and proxy tickets (e.g. "http://www.google.com" and "http://www.google.com/"
+  are now considered to be the same service URL).
+* Authenticators now raise AuthenticatorError exceptions when encountering
+  a problem/error. This makes it easier to send feedback to the user.
+  However, other exceptions should still be raised when errors ought
+  not be recoverable (i.e. programming errors).
+* Fixed serious vulnerability in LDAP authenticator where under some
+  cirumstances the user could just enter '*' as their username to match 
+  any username. The LDAP authenticator will now refuse to process logins 
+  with usernames that contain the characters * ( ) \ / and the NULL 
+  character \0.
+* Views are no longer xhtml-validated. Markaby's auto-validation was turned
+  off to allow for use of the autocomplete property on inputs, since this is
+  the only viable way of turning off password storage in IE and Firefox at
+  the page level.
+* You can now limit the maximum length of a login session by setting the
+  expire_sessions config setting to true.
+* Fixed some minor bugs in the login view.
+
+
+=== 0.2.0 :: 2007-03-20
+
+* ruby-casserver now behaves more like a real command-line app, accepting
+  various command line arguments including -h (help), -v (version), -c (use
+  an alternate config.yml), and -d (daemonize, when using webrick or mongrel 
+  mode).
+* Special characters in CAS XML responses are now properly encoded into XML
+  entities
+* CAS XML responses are no longer auto-indented... Markaby's indentation
+  seemed to be causing problems with the PHP CAS client.
+* Misc minor bug fixes/cleanup.
+
+
+=== 0.1.0 :: 2007-03-01
+
+* First public release.
+

data/LICENSE.txt

@@ -0,0 +1,504 @@
+		  GNU LESSER GENERAL PUBLIC LICENSE
+		       Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 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.
+
+[This is the first released version of the Lesser GPL.  It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+  This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it.  You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+  When we speak of free software, we are referring to freedom of use,
+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 and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+  To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights.  These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+  For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you.  You must make sure that they, too, receive or can get the source
+code.  If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it.  And you must show them these terms so they know their rights.
+
+  We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+  To protect each distributor, we want to make it very clear that
+there is no warranty for the free library.  Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+  Finally, software patents pose a constant threat to the existence of
+any free program.  We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder.  Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+  Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License.  This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License.  We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+  When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library.  The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom.  The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+  We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License.  It also provides other free software developers Less
+of an advantage over competing non-free programs.  These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries.  However, the Lesser license provides advantages in certain
+special circumstances.
+
+  For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard.  To achieve this, non-free programs must be
+allowed to use the library.  A more frequent case is that a free
+library does the same job as widely used non-free libraries.  In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+  In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software.  For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+  Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.  Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library".  The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+		  GNU LESSER GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+  A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+  The "Library", below, refers to any such software library or work
+which has been distributed under these terms.  A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language.  (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+  "Source code" for a work means the preferred form of the work for
+making modifications to it.  For a library, 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 library.
+
+  Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it).  Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+  
+  1. You may copy and distribute verbatim copies of the Library's
+complete 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 distribute a copy of this License along with the
+Library.
+
+  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 Library or any portion
+of it, thus forming a work based on the Library, 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) The modified work must itself be a software library.
+
+    b) You must cause the files modified to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    c) You must cause the whole of the work to be licensed at no
+    charge to all third parties under the terms of this License.
+
+    d) If a facility in the modified Library refers to a function or a
+    table of data to be supplied by an application program that uses
+    the facility, other than as an argument passed when the facility
+    is invoked, then you must make a good faith effort to ensure that,
+    in the event an application does not supply such function or
+    table, the facility still operates, and performs whatever part of
+    its purpose remains meaningful.
+
+    (For example, a function in a library to compute square roots has
+    a purpose that is entirely well-defined independent of the
+    application.  Therefore, Subsection 2d requires that any
+    application-supplied function or table used by this function must
+    be optional: if the application does not supply it, the square
+    root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Library,
+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 Library, 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 Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library.  To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License.  (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.)  Do not make any other change in
+these notices.
+
+  Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+  This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+  4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you 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.
+
+  If distribution of 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 satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library".  Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+  However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library".  The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+  When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library.  The
+threshold for this to be true is not precisely defined by law.
+
+  If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work.  (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+  Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+  6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+  You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License.  You must supply a copy of this License.  If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License.  Also, you must do one
+of these things:
+
+    a) Accompany the work with the complete corresponding
+    machine-readable source code for the Library including whatever
+    changes were used in the work (which must be distributed under
+    Sections 1 and 2 above); and, if the work is an executable linked
+    with the Library, with the complete machine-readable "work that
+    uses the Library", as object code and/or source code, so that the
+    user can modify the Library and then relink to produce a modified
+    executable containing the modified Library.  (It is understood
+    that the user who changes the contents of definitions files in the
+    Library will not necessarily be able to recompile the application
+    to use the modified definitions.)
+
+    b) Use a suitable shared library mechanism for linking with the
+    Library.  A suitable mechanism is one that (1) uses at run time a
+    copy of the library already present on the user's computer system,
+    rather than copying library functions into the executable, and (2)
+    will operate properly with a modified version of the library, if
+    the user installs one, as long as the modified version is
+    interface-compatible with the version that the work was made with.
+
+    c) Accompany the work with a written offer, valid for at
+    least three years, to give the same user the materials
+    specified in Subsection 6a, above, for a charge no more
+    than the cost of performing this distribution.
+
+    d) If distribution of the work is made by offering access to copy
+    from a designated place, offer equivalent access to copy the above
+    specified materials from the same place.
+
+    e) Verify that the user has already received a copy of these
+    materials or that you have already sent this user a copy.
+
+  For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it.  However, as a special exception,
+the materials to be 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.
+
+  It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system.  Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+  7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+    a) Accompany the combined library with a copy of the same work
+    based on the Library, uncombined with any other library
+    facilities.  This must be distributed under the terms of the
+    Sections above.
+
+    b) Give prominent notice with the combined library of the fact
+    that part of it is a work based on the Library, and explaining
+    where to find the accompanying uncombined form of the same work.
+
+  8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License.  Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library 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.
+
+  9. 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 Library or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+  10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+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 with
+this License.
+
+  11. 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 Library at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Library 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 Library.
+
+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.
+
+  12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library 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.
+
+  13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser 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 Library
+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 Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+  14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+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
+
+  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "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
+LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. 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 LIBRARY 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
+LIBRARY (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 LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), 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 Libraries
+
+  If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change.  You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+  To apply these terms, attach the following notices to the library.  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 library's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This library is free software; you can redistribute it and/or
+    modify it under the terms of the GNU Lesser General Public
+    License as published by the Free Software Foundation; either
+    version 2.1 of the License, or (at your option) any later version.
+
+    This library 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
+    Lesser General Public License for more details.
+
+    You should have received a copy of the GNU Lesser General Public
+    License along with this library; 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.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the
+  library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+  <signature of Ty Coon>, 1 April 1990
+  Ty Coon, President of Vice
+
+That's all there is to it!
+
+