--- /dev/null
-@setfilename mit-scheme-blowfish.info
+ \input texinfo @c -*-texinfo-*-
+ @comment %**start of header
-@set SCMVERS 9.2.1
-@settitle MIT/GNU Scheme Blowfish Plugin Manual
++@setfilename blowfish.info
+ @include version.texi
-This manual documents MIT/GNU Scheme Blowfish @value{VERSION}.
++@set SCMVERS 9.2.7
++@settitle Blowfish Plugin Manual
+ @comment %**end of header
+
++@ifhtml
++@macro bref {name}
++@ref{\name\,,@code{\name\}}
++@end macro
++@end ifhtml
++@ifinfo
++@macro bref {name}
++\name\
++@end macro
++@end ifinfo
++@ifnothtml
++@ifnotinfo
++@macro bref {name}
++@code{\name\}
++@end macro
++@end ifnotinfo
++@end ifnothtml
++
+ @copying
-* Blowfish: (mit-scheme-blowfish).
++This manual documents MIT/GNU Scheme Pucked Blowfish @value{VERSION}.
+
+ Copyright @copyright{} 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014,
+ 2015, 2016, 2017 Matthew Birkholz
+
+ @quotation
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.2 or
+ any later version published by the Free Software Foundation; with no
+ Invariant Sections, with no Front-Cover Texts and no Back-Cover Texts.
+ A copy of the license is included in the section entitled ``GNU Free
+ Documentation License.''
+ @end quotation
+ @end copying
+
+ @dircategory Programming Languages
+ @direntry
-@title MIT/GNU Scheme Blowfish Plugin Manual
++* Blowfish: (mit-scheme-pucked/blowfish).
+ Blowfish plugin.
+ @end direntry
+
+ @titlepage
-@subtitle for MIT/GNU Scheme version @value{SCMVERS}
++@title Blowfish Plugin Manual
+ @subtitle a Blowfish block cipher plugin (version @value{VERSION})
-less in length. For text keys (strings), apply @code{md5} to the
++@subtitle for MIT/GNU Scheme Pucked version @value{SCMVERS}
+ @subtitle @value{UPDATED}
+ @author by Matt Birkholz
+ @page
+ @vskip 0pt plus 1filll
+ @insertcopying
+ @end titlepage
+
+ @ifnottex
+ @node Top
+ @top Blowfish Plugin Manual
+
+ @insertcopying
+ @end ifnottex
+
+ @menu
+ * Introduction::
+ * Procedures::
+ * DES Modes::
+ * GNU Free Documentation License::
+ @end menu
+
+ @node Introduction
+ @chapter Introduction
+
+ This plugin is a dynamically loadable wrapper of the Blowfish block
+ cipher C API as implemented by libssl (OpenSSL).
+
+ The cipher operates on 64 bit (8 byte) blocks of data and uses a
+ variable size key. Keys with 128 bits (16 bytes) are considered good
+ for strong encryption. Blowfish can be used in the same modes as DES
+ and is currently one of the faster block ciphers. It is quite a bit
+ faster than DES, and much faster than IDEA or RC2.
+
+ The plugin includes a Scheme procedure to feed bytes from a binary
+ input port to the library, and write the encrypted bytes to a binary
+ output port.
+
+ @node Procedures
+ @chapter Procedures
+
+ Blowfish consists of a key setup phase and the actual encryption or
+ decryption phase.
+
+ @deffn Procedure blowfish-set-key bytes
+ Generate a Blowfish key from @var{bytes}, which must be 72 bytes or
-simply initialized to zero. @code{Blowfish-cbc} operates on data that
-is a multiple of 8 bytes long, while @code{blowfish-cfb64} and
-@code{blowfish-ofb64} are used to encrypt any number of bytes. The
++less in length. For text keys (strings), apply @bref{md5} to the
+ string, and use the digest for @var{bytes}.
+ @end deffn
+
+ @deffn Procedure blowfish-ecb input output key encyrpt?
+ Apply Blowfish in Electronic Code Book mode.
+ @var{Input} is an 8-byte byte vector.
+ @var{Output} is an 8-byte byte vector.
+ @var{Key} is a Blowfish key.
+ @var{Encrypt?} specifies whether to encrypt (when @code{#t}) or decrypt
+ (when @code{#f}).
+ @end deffn
+
+ The mode functions below all operate on variable length data. They
+ all take an initialization vector which needs to be passed along into
+ the next call of the same function for the same message. The vector
+ may be initialized with anything, but the recipient needs to know what
+ it was initialized with, or it won't be able to decrypt. Some
+ programs and protocols simplify this, like SSH, where the vector is
-the end. Feeds the bytes to @code{blowfish-cfb64} and writes the
++simply initialized to zero. @bref{Blowfish-cbc} operates on data that
++is a multiple of 8 bytes long, while @bref{blowfish-cfb64} and
++@bref{blowfish-ofb64} are used to encrypt any number of bytes. The
+ purpose of the latter two is to simulate stream ciphers, and
+ therefore, they have a parameter @code{num}, the current offset in the
+ initialization vector, which should start at zero and be stored
+ between calls.
+
+ @deffn Procedure blowfish-cbc input output key init encrypt?
+ Apply Blowfish in Cipher Block Chaining mode.
+ @var{Input} is a multiple of 8 bytes.
+ @var{Output} is the same number of bytes as in Input.
+ @var{Key} is a Blowfish key.
+ @var{Init} is an 8 byte initialization vector;
+ it is modified after each call.
+ The value from any call may be passed in to a later call.
+ @var{Encrypt?} specifies whether to encrypt (when @code{#t}) or decrypt
+ (when @code{#f}).
+ @end deffn
+
+ @deffn Procedure blowfish-cfb64 input istart iend output ostart key init num encrypt?
+ Apply Blowfish in Cipher Feed-Back mode.
+ @var{Istart} and @var{Iend} specify a range of bytes in @var{Input}.
+ @var{Ostart} specifies the first byte to write in @var{Output}.
+ @var{Key} is a Blowfish key.
+ @var{Init} is an 8 byte initialization vector;
+ it is modified after each call.
+ The value from any call may be passed in to a later call.
+ The initial value must be unique for each message/key pair.
+ @var{Num} is an integer from 0 to 7 inclusive, the low 3 bits of the
+ number of bytes that have previously been processed in this stream.
+ @var{Encrypt?} specifies whether to encrypt (when @code{#t}) or decrypt
+ (when @code{#f}).
+ The returned value is the new value of Num.
+ @end deffn
+
+ @deffn Procedure blowfish-ofb64 input istart iend output ostart key init num
+ Apply Blowfish in Output Feed-Back mode.
+ @var{Istart} and @var{Iend} specify a range of bytes in @var{Input}.
+ @var{Ostart} specifies the first byte to write in @var{Output}.
+ @var{Key} is a Blowfish key.
+ @var{Init} is an 8 byte initialization vector;
+ it is modified after each call.
+ The value from any call may be passed in to a later call.
+ The initial value must be unique for each message/key pair.
+ @var{Num} is an integer from 0 to 7 inclusive, the low 3 bits of the
+ number of bytes that have previously been processed in this stream.
+ The returned value is the new value of Num.
+ @end deffn
+
+ Two convenience procedures are also provided.
+
+ @deffn Procedure blowfish-encrypt-port input output key init encrypt?
+ Reads bytes from @var{input}, which should be in blocking mode, until
-@var{init} are passed to @code{blowfish-cfb64} (which modifies
++the end. Feeds the bytes to @bref{blowfish-cfb64} and writes the
+ resulting, encrypted bytes to @var{output}. @var{Key} and
++@var{init} are passed to @bref{blowfish-cfb64} (which modifies
+ the latter).
+ @var{Encrypt?} specifies whether to encrypt (when @code{#t}) or decrypt
+ (when @code{#f}).
+ @end deffn
+
+ @deffn Procedure compute-blowfish-init-vector
+ Returns a new initialization vector that includes a timestamp with a
+ resolution of milliseconds, plus 20 random bits. This should make it
+ very likely unique.
+ @end deffn
+
+ The Blowfish cipher was invented and described by Counterpane (see
+ @url{http://www.counterpane.com/blowfish.html}). Most of this manual
+ was adapted from the OpenSSL manual pages.
+
+ @node DES Modes
+ @chapter DES Modes
+
+ This chapter was written in large parts by Eric Young in his original
+ documentation for SSLeay, the predecessor of OpenSSL. In turn, he
+ attributed it to:
+
+ @smallexample
+ AS 2805.5.2
+ Australian Standard
+ Electronic funds transfer - Requirements for interfaces,
+ Part 5.2: Modes of operation for an n-bit block cipher algorithm
+ Appendix A
+ @end smallexample
+
+ @section Electronic Codebook Mode (ECB)
+
+ 64 bits are enciphered at a time.
+
+ The order of the blocks can be rearranged without detection.
+
+ The same plain text block always produces the same cipher text block
+ (for the same key) making it vulnerable to a dictionary attack.
+
+ An error will only affect one cipher text block.
+
+ @section Cipher Block Chaining Mode (CBC)
+
+ A multiple of 64 bits are enciphered at a time.
+
+ The CBC mode produces the same cipher text whenever the same plain text
+ is encrypted using the same key and starting variable.
+
+ The chaining operation makes the cipher text blocks dependent on the
+ current and all preceding plain text blocks and therefore blocks can
+ not be rearranged.
+
+ The use of different starting variables prevents the same plain text
+ enciphering to the same cipher text.
+
+ An error will affect the current and the following cipher text blocks.
+
+ @section Cipher Feedback Mode (CFB)
+
+ Any number of bits, j, up to 64, are enciphered at a time.
+
+ The CFB mode produces the same cipher text whenever the same plain text
+ is encrypted using the same key and starting variable.
+
+ The chaining operation makes the cipher text variables dependent on
+ the current and all preceding variables and therefore j-bit variables
+ are chained together and can not be rearranged.
+
+ The use of different starting variables prevents the same plain text
+ enciphering to the same cipher text.
+
+ The strength of the CFB mode depends on the size of k (maximal if j
+ = k). In my implementation this is always the case.
+
+ Selection of a small value for j will require more cycles through the
+ encipherment algorithm per unit of plain text and thus cause greater
+ processing overheads.
+
+ Only multiples of j bits can be enciphered.
+
+ An error will affect the current and the following cipher text
+ variables.
+
+ @section Output Feedback Mode (OFB)
+
+ Any number of bits, j, up to 64, are enciphered at a time.
+
+ The OFB mode produces the same cipher text whenever the same plain text
+ enciphered using the same key and starting variable. More over, in
+ the OFB mode the same key stream is produced when the same key and
+ start variable are used. Consequently, for security reasons a
+ specific start variable should be used only once for a given key.
+
+ The absence of chaining makes the OFB more vulnerable to specific
+ attacks.
+
+ The use of different start variables values prevents the same
+ plain text enciphering to the same cipher text, by producing different
+ key streams.
+
+ Selection of a small value for j will require more cycles through the
+ encipherment algorithm per unit of plain text and thus cause greater
+ processing overheads.
+
+ Only multiples of j bits can be enciphered.
+
+ OFB mode of operation does not extend cipher text errors in the
+ resultant plain text output. Every bit error in the cipher text causes
+ only one bit to be in error in the deciphered plain text.
+
+ OFB mode is not self-synchronizing. If the two operations of
+ encipherment and decipherment get out of synchronism, the system
+ needs to be re-initialized.
+
+ Each re-initialization should use a value of the start variable
+ different from the start variable values used before with the same
+ key. The reason for this is that an identical bit stream would be
+ produced each time from the same parameters. This would be
+ susceptible to a 'known plain text' attack.
+
+ @node GNU Free Documentation License
+ @appendix GNU Free Documentation License
+
+ @cindex FDL, GNU Free Documentation License
+ @center Version 1.2, November 2002
+
+ @display
+ Copyright @copyright{} 2000,2001,2002 Free Software Foundation, Inc.
+ 51 Franklin St, 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.
+ @end display
+
+ @enumerate 0
+ @item
+ PREAMBLE
+
+ The purpose of this License is to make a manual, textbook, or other
+ functional and useful document @dfn{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.
+
+ @item
+ APPLICABILITY AND DEFINITIONS
+
+ This License applies to any manual or other work, in any medium, that
+ contains a notice placed by the copyright holder saying it can be
+ distributed under the terms of this License. Such a notice grants a
+ world-wide, royalty-free license, unlimited in duration, to use that
+ work under the conditions stated herein. The ``Document'', below,
+ refers to any such manual or work. Any member of the public is a
+ licensee, and is addressed as ``you''. You accept the license if you
+ copy, modify or distribute the work in a way requiring permission
+ under copyright law.
+
+ 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. (Thus, 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. If a
+ section does not fit the above definition of Secondary then it is not
+ allowed to be designated as Invariant. The Document may contain zero
+ Invariant Sections. If the Document does not identify any Invariant
+ Sections then there are none.
+
+ 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 Front-Cover Text may
+ be at most 5 words, and a Back-Cover Text may be at most 25 words.
+
+ A ``Transparent'' copy of the Document means a machine-readable copy,
+ represented in a format whose specification is available to the
+ general public, that is suitable for revising the document
+ 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, or absence of markup, has been arranged to thwart
+ or discourage subsequent modification by readers is not Transparent.
+ An image format is not Transparent if used for any substantial amount
+ of text. A copy that is not ``Transparent'' is called ``Opaque''.
+
+ Examples of suitable formats for Transparent copies include plain
+ @sc{ascii} without markup, Texinfo input format, La@TeX{} input
+ format, @acronym{SGML} or @acronym{XML} using a publicly available
+ @acronym{DTD}, and standard-conforming simple @acronym{HTML},
+ PostScript or @acronym{PDF} designed for human modification. Examples
+ of transparent image formats include @acronym{PNG}, @acronym{XCF} and
+ @acronym{JPG}. Opaque formats include proprietary formats that can be
+ read and edited only by proprietary word processors, @acronym{SGML} or
+ @acronym{XML} for which the @acronym{DTD} and/or processing tools are
+ not generally available, and the machine-generated @acronym{HTML},
+ PostScript or @acronym{PDF} 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.
+
+ A section ``Entitled XYZ'' means a named subunit of the Document whose
+ title either is precisely XYZ or contains XYZ in parentheses following
+ text that translates XYZ in another language. (Here XYZ stands for a
+ specific section name mentioned below, such as ``Acknowledgements'',
+ ``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the Title''
+ of such a section when you modify the Document means that it remains a
+ section ``Entitled XYZ'' according to this definition.
+
+ The Document may include Warranty Disclaimers next to the notice which
+ states that this License applies to the Document. These Warranty
+ Disclaimers are considered to be included by reference in this
+ License, but only as regards disclaiming warranties: any other
+ implication that these Warranty Disclaimers may have is void and has
+ no effect on the meaning of this License.
+
+ @item
+ 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.
+
+ @item
+ COPYING IN QUANTITY
+
+ If you publish printed copies (or copies in media that commonly have
+ printed covers) 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 computer-network location from which the general network-using
+ public has access to download using public-standard network protocols
+ a complete Transparent copy of the Document, free of added material.
+ 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.
+
+ @item
+ 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:
+
+ @enumerate A
+ @item
+ Use in the Title Page (and on the covers, if any) a title distinct
+ from that of the Document, and from those of previous versions
+ (which should, if there were any, be listed in the History section
+ of the Document). You may use the same title as a previous version
+ if the original publisher of that version gives permission.
+
+ @item
+ List on the Title Page, as authors, one or more persons or entities
+ responsible for authorship of the modifications in the Modified
+ Version, together with at least five of the principal authors of the
+ Document (all of its principal authors, if it has fewer than five),
+ unless they release you from this requirement.
+
+ @item
+ State on the Title page the name of the publisher of the
+ Modified Version, as the publisher.
+
+ @item
+ Preserve all the copyright notices of the Document.
+
+ @item
+ Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+
+ @item
+ Include, immediately after the copyright notices, a license notice
+ giving the public permission to use the Modified Version under the
+ terms of this License, in the form shown in the Addendum below.
+
+ @item
+ Preserve in that license notice the full lists of Invariant Sections
+ and required Cover Texts given in the Document's license notice.
+
+ @item
+ Include an unaltered copy of this License.
+
+ @item
+ Preserve the section Entitled ``History'', Preserve its Title, and add
+ to it an item stating at least the title, year, new authors, and
+ publisher of the Modified Version as given on the Title Page. If
+ there is no section Entitled ``History'' in the Document, create one
+ stating the title, year, authors, and publisher of the Document as
+ given on its Title Page, then add an item describing the Modified
+ Version as stated in the previous sentence.
+
+ @item
+ Preserve the network location, if any, given in the Document for
+ public access to a Transparent copy of the Document, and likewise
+ the network locations given in the Document for previous versions
+ it was based on. These may be placed in the ``History'' section.
+ You may omit a network location for a work that was published at
+ least four years before the Document itself, or if the original
+ publisher of the version it refers to gives permission.
+
+ @item
+ For any section Entitled ``Acknowledgements'' or ``Dedications'', Preserve
+ the Title of the section, and preserve in the section all the
+ substance and tone of each of the contributor acknowledgements and/or
+ dedications given therein.
+
+ @item
+ Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section titles.
+
+ @item
+ Delete any section Entitled ``Endorsements''. Such a section
+ may not be included in the Modified Version.
+
+ @item
+ Do not retitle any existing section to be Entitled ``Endorsements'' or
+ to conflict in title with any Invariant Section.
+
+ @item
+ Preserve any Warranty Disclaimers.
+ @end enumerate
+
+ 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.
+
+ @item
+ 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, and that you preserve all their Warranty Disclaimers.
+
+ 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.''
+
+ @item
+ 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.
+
+ @item
+ 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, is called an ``aggregate'' if the copyright
+ resulting from the compilation is not used to limit the legal rights
+ of the compilation's users beyond what the individual works permit.
+ When the Document is included an aggregate, this License does not
+ apply to the other works in the aggregate which 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 half of
+ the entire aggregate, the Document's Cover Texts may be placed on
+ covers that bracket the Document within the aggregate, or the
+ electronic equivalent of covers if the Document is in electronic form.
+ Otherwise they must appear on printed covers that bracket the whole
+ aggregate.
+
+ @item
+ 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, and all the license notices in the
+ Document, and any Warrany Disclaimers, provided that you also include
+ the original English version of this License and the original versions
+ of those notices and disclaimers. In case of a disagreement between
+ the translation and the original version of this License or a notice
+ or disclaimer, the original version will prevail.
+
+ If a section in the Document is Entitled ``Acknowledgements'',
+ ``Dedications'', or ``History'', the requirement (section 4) to Preserve
+ its Title (section 1) will typically require changing the actual
+ title.
+
+ @item
+ 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.
+
+ @item
+ 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
+ @uref{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.
+ @end enumerate
+
+ @page
+ @appendixsec ADDENDUM: 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:
+
+ @smallexample
+ @group
+ Copyright (C) @var{year} @var{your name}.
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.2
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+ A copy of the license is included in the section entitled ``GNU
+ Free Documentation License''.
+ @end group
+ @end smallexample
+
+ If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+ replace the ``with...Texts.'' line with this:
+
+ @smallexample
+ @group
+ with the Invariant Sections being @var{list their titles}, with
+ the Front-Cover Texts being @var{list}, and with the Back-Cover Texts
+ being @var{list}.
+ @end group
+ @end smallexample
+
+ If you have Invariant Sections without Cover Texts, or some other
+ combination of the three, merge those two alternatives to suit the
+ situation.
+
+ 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.
+
+ @bye
projects / mit-scheme.git / commitdiff