From 16e6dc64c6f133d6d2032a77b2c80ea8dee0f874 Mon Sep 17 00:00:00 2001 From: ubbo Date: Sun, 10 Aug 2008 13:40:36 +0000 Subject: moved gpg.exe to bin, added copyright and readme for binaries git-svn-id: http://cpunk.de/svn/src/gpg4usb@123 34ebc366-c3a9-4b3c-9f84-69acf7962910 --- README | 2 +- bin/COPYING.txt | 676 ++++++++++++++++++++++++++++++++++++++++++ bin/README.txt | 822 ++++++++++++++++++++++++++++++++++++++++++++++++++++ bin/gpg.exe | Bin 0 -> 870400 bytes release/bin/gpg.exe | Bin 870400 -> 0 bytes 5 files changed, 1499 insertions(+), 1 deletion(-) create mode 100644 bin/COPYING.txt create mode 100644 bin/README.txt create mode 100644 bin/gpg.exe delete mode 100644 release/bin/gpg.exe diff --git a/README b/README index 6fa9e4b..f315325 100644 --- a/README +++ b/README @@ -2,7 +2,7 @@ ABOUT ----- gpg4usb is an easy to use, small portable editor with the possibility to encrypt and decrypt any text-message or -file you want. For encryption it acts as -a gpg-frontend (http://gnupg.org/) Its intend is to be used from an usb-stick, +a gpg-frontend (http://gnupg.org/). Its intend is to be used from an usb-stick, running on Windows(TM) and Linux. Providing a mac-binary is on our TODO-list. Our aim is, to give anyone the possibility to send and receive secure encrypted diff --git a/bin/COPYING.txt b/bin/COPYING.txt new file mode 100644 index 0000000..5b244d5 --- /dev/null +++ b/bin/COPYING.txt @@ -0,0 +1,676 @@ + + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU General Public License is a free, copyleft license for +software and other kinds of works. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +the GNU General Public License is intended to guarantee your freedom to +share and change all versions of a program--to make sure it remains free +software for all its users. We, the Free Software Foundation, use the +GNU General Public License for most of our software; it applies also to +any other work released this way by its authors. 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 +them 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 prevent others from denying you +these rights or asking you to surrender the rights. Therefore, you have +certain responsibilities if you distribute copies of the software, or if +you modify it: responsibilities to respect the freedom of others. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must pass on to the recipients the same +freedoms that you received. 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. + + Developers that use the GNU GPL protect your rights with two steps: +(1) assert copyright on the software, and (2) offer you this License +giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL clearly explains +that there is no warranty for this free software. For both users' and +authors' sake, the GPL requires that modified versions be marked as +changed, so that their problems will not be attributed erroneously to +authors of previous versions. + + Some devices are designed to deny users access to install or run +modified versions of the software inside them, although the manufacturer +can do so. This is fundamentally incompatible with the aim of +protecting users' freedom to change the software. The systematic +pattern of such abuse occurs in the area of products for individuals to +use, which is precisely where it is most unacceptable. Therefore, we +have designed this version of the GPL to prohibit the practice for those +products. If such problems arise substantially in other domains, we +stand ready to extend this provision to those domains in future versions +of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. +States should not allow patents to restrict development and use of +software on general-purpose computers, but in those that do, we wish to +avoid the special danger that patents applied to a free program could +make it effectively proprietary. To prevent this, the GPL assures that +patents cannot be used to render the program non-free. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for +the work, and the source code for shared libraries and dynamically +linked subprograms that the work is specifically designed to require, +such as by intimate data communication or control flow between those +subprograms and other parts of the work. + + The Corresponding Source need not include anything that users +can regenerate automatically from other parts of the Corresponding +Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not +convey, without conditions so long as your license otherwise remains +in force. You may convey covered works to others for the sole purpose +of having them make modifications exclusively for you, or provide you +with facilities for running those works, provided that you comply with +the terms of this License in conveying all material for which you do +not control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. Sublicensing is not allowed; section 10 +makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological +measure under any applicable law fulfilling obligations under article +11 of the WIPO copyright treaty adopted on 20 December 1996, or +similar laws prohibiting or restricting circumvention of such +measures. + + When you convey a covered work, you waive any legal power to forbid +circumvention of technological measures to the extent such circumvention +is effected by exercising rights under this License with respect to +the covered work, and you disclaim any intention to limit operation or +modification of the work as a means of enforcing, against the work's +users, your or third parties' legal rights to forbid circumvention of +technological measures. + + 4. Conveying Verbatim Copies. + + You may convey 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; +keep intact all notices stating that this License and any +non-permissive terms added in accord with section 7 apply to the code; +keep intact all notices of the absence of any warranty; and give all +recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, +and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to +produce it from the Program, in the form of source code under the +terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent +works, which are not by their nature extensions of the covered work, +and which are not combined with it such as to form a larger program, +in or on a volume of a storage or distribution medium, is called an +"aggregate" if the compilation and its resulting copyright are not +used to limit the access or legal rights of the compilation's users +beyond what the individual works permit. Inclusion of a covered work +in an aggregate does not cause this License to apply to the other +parts of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms +of sections 4 and 5, provided that you also convey the +machine-readable Corresponding Source under the terms of this License, +in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the + Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded +from the Corresponding Source as a System Library, need not be +included in conveying the object code work. + + A "User Product" is either (1) a "consumer product", which means any +tangible personal property which is normally used for personal, family, +or household purposes, or (2) anything designed or sold for incorporation +into a dwelling. In determining whether a product is a consumer product, +doubtful cases shall be resolved in favor of coverage. For a particular +product received by a particular user, "normally used" refers to a +typical or common use of that class of product, regardless of the status +of the particular user or of the way in which the particular user +actually uses, or expects or is expected to use, the product. A product +is a consumer product regardless of whether the product has substantial +commercial, industrial or non-consumer uses, unless such uses represent +the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, +procedures, authorization keys, or other information required to install +and execute modified versions of a covered work in that User Product from +a modified version of its Corresponding Source. The information must +suffice to ensure that the continued functioning of the modified object +code is in no case prevented or interfered with solely because +modification has been made. + + If you convey an object code work under this section in, or with, or +specifically for use in, a User Product, and the conveying occurs as +part of a transaction in which the right of possession and use of the +User Product is transferred to the recipient in perpetuity or for a +fixed term (regardless of how the transaction is characterized), the +Corresponding Source conveyed under this section must be accompanied +by the Installation Information. But this requirement does not apply +if neither you nor any third party retains the ability to install +modified object code on the User Product (for example, the work has +been installed in ROM). + + The requirement to provide Installation Information does not include a +requirement to continue to provide support service, warranty, or updates +for a work that has been modified or installed by the recipient, or for +the User Product in which it has been modified or installed. Access to a +network may be denied when the modification itself materially and +adversely affects the operation of the network or violates the rules and +protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, +in accord with this section must be in a format that is publicly +documented (and with an implementation available to the public in +source code form), and must require no special password or key for +unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this +License by making exceptions from one or more of its conditions. +Additional permissions that are applicable to the entire Program shall +be treated as though they were included in this License, to the extent +that they are valid under applicable law. If additional permissions +apply only to part of the Program, that part may be used separately +under those permissions, but the entire Program remains governed by +this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option +remove any additional permissions from that copy, or from any part of +it. (Additional permissions may be written to require their own +removal in certain cases when you modify the work.) You may place +additional permissions on material, added by you to a covered work, +for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you +add to a covered work, you may (if authorized by the copyright holders of +that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on + those licensors and authors. + + All other non-permissive additional terms are considered "further +restrictions" within the meaning of section 10. If the Program as you +received it, or any part of it, contains a notice stating that it is +governed by this License along with a term that is a further +restriction, you may remove that term. If a license document contains +a further restriction but permits relicensing or conveying under this +License, you may add to a covered work material governed by the terms +of that license document, provided that the further restriction does +not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you +must place, in the relevant source files, a statement of the +additional terms that apply to those files, or a notice indicating +where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the +form of a separately written license, or stated as exceptions; +the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly +provided under this License. Any attempt otherwise to propagate or +modify it is void, and will automatically terminate your rights under +this License (including any patent licenses granted under the third +paragraph of section 11). + + However, if you cease all violation of this License, then your +license from a particular copyright holder is reinstated (a) +provisionally, unless and until the copyright holder explicitly and +finally terminates your license, and (b) permanently, if the copyright +holder fails to notify you of the violation by some reasonable means +prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + + Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, you do not qualify to receive new licenses for the same +material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or +run a copy of the Program. Ancillary propagation of a covered work +occurring solely as a consequence of using peer-to-peer transmission +to receive a copy likewise does not require acceptance. However, +nothing other than this License grants you permission to propagate or +modify any covered work. These actions infringe copyright if you do +not accept this License. Therefore, by modifying or propagating a +covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically +receives a license from the original licensors, to run, modify and +propagate that work, subject to this License. You are not responsible +for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an +organization, or substantially all assets of one, or subdividing an +organization, or merging organizations. If propagation of a covered +work results from an entity transaction, each party to that +transaction who receives a copy of the work also receives whatever +licenses to the work the party's predecessor in interest had or could +give under the previous paragraph, plus a right to possession of the +Corresponding Source of the work from the predecessor in interest, if +the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of the +rights granted or affirmed under this License. For example, you may +not impose a license fee, royalty, or other charge for exercise of +rights granted under this License, and you may not initiate litigation +(including a cross-claim or counterclaim in a lawsuit) alleging that +any patent claim is infringed by making, using, selling, offering for +sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this +License of the Program or a work on which the Program is based. The +work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims +owned or controlled by the contributor, whether already acquired or +hereafter acquired, that would be infringed by some manner, permitted +by this License, of making, using, or selling its contributor version, +but do not include claims that would be infringed only as a +consequence of further modification of the contributor version. For +purposes of this definition, "control" includes the right to grant +patent sublicenses in a manner consistent with the requirements of +this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free +patent license under the contributor's essential patent claims, to +make, use, sell, offer for sale, import and otherwise run, modify and +propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express +agreement or commitment, however denominated, not to enforce a patent +(such as an express permission to practice a patent or covenant not to +sue for patent infringement). To "grant" such a patent license to a +party means to make such an agreement or commitment not to enforce a +patent against the party. + + If you convey a covered work, knowingly relying on a patent license, +and the Corresponding Source of the work is not available for anyone +to copy, free of charge and under the terms of this License, through a +publicly available network server or other readily accessible means, +then you must either (1) cause the Corresponding Source to be so +available, or (2) arrange to deprive yourself of the benefit of the +patent license for this particular work, or (3) arrange, in a manner +consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have +actual knowledge that, but for the patent license, your conveying the +covered work in a country, or your recipient's use of the covered work +in a country, would infringe one or more identifiable patents in that +country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or +arrangement, you convey, or propagate by procuring conveyance of, a +covered work, and grant a patent license to some of the parties +receiving the covered work authorizing them to use, propagate, modify +or convey a specific copy of the covered work, then the patent license +you grant is automatically extended to all recipients of the covered +work and works based on it. + + A patent license is "discriminatory" if it does not include within +the scope of its coverage, prohibits the exercise of, or is +conditioned on the non-exercise of one or more of the rights that are +specifically granted under this License. You may not convey a covered +work if you are a party to an arrangement with a third party that is +in the business of distributing software, under which you make payment +to the third party based on the extent of your activity of conveying +the work, and under which the third party grants, to any of the +parties who would receive the covered work from you, a discriminatory +patent license (a) in connection with copies of the covered work +conveyed by you (or copies made from those copies), or (b) primarily +for and in connection with specific products or compilations that +contain the covered work, unless you entered into that arrangement, +or that patent license was granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting +any implied license or other defenses to infringement that may +otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If 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 convey a +covered work so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you +to collect a royalty for further conveying from those to whom you convey +the Program, the only way you could satisfy both those terms and this +License would be to refrain entirely from conveying the Program. + + 13. Use with the GNU Affero General Public License. + + Notwithstanding any other provision of this License, you have +permission to link or combine any covered work with a work licensed +under version 3 of the GNU Affero General Public License into a single +combined work, and to convey the resulting work. The terms of this +License will continue to apply to the part which is the covered work, +but the special requirements of the GNU Affero General Public License, +section 13, concerning interaction through a network will apply to the +combination as such. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU 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 that a certain numbered version of the GNU General +Public License "or any later version" applies to it, you have the +option of following the terms and conditions either of that numbered +version or of any later version published by the Free Software +Foundation. If the Program does not specify a version number of the +GNU General Public License, you may choose any version ever published +by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future +versions of the GNU General Public License can be used, that proxy's +public statement of acceptance of a version permanently authorizes you +to choose that version for the Program. + + Later license versions may give you additional or different +permissions. However, no additional obligations are imposed on any +author or copyright holder as a result of your choosing to follow a +later version. + + 15. Disclaimer of Warranty. + + 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. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS +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. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. + + 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 +state the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + 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 3 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, see . + +Also add information on how to contact you by electronic and paper mail. + + If the program does terminal interaction, make it output a short +notice like this when it starts in an interactive mode: + + Copyright (C) + This program 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, your program's commands +might be different; for a GUI interface, you would use an "about box". + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU GPL, see +. + + The GNU 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. But first, please read +. + diff --git a/bin/README.txt b/bin/README.txt new file mode 100644 index 0000000..1683a89 --- /dev/null +++ b/bin/README.txt @@ -0,0 +1,822 @@ + + GnuPG - The GNU Privacy Guard + ------------------------------- + Version 1.4.9 + + Copyright 1998, 1999, 2000, 2001, 2002, 2003, 2004, + 2005, 2006, 2007, 2008 Free Software Foundation, Inc. + + This file is free software; as a special exception the author + gives unlimited permission to copy and/or distribute it, with or + without modifications, as long as this notice is preserved. + + This file is distributed in the hope that it will be useful, but + WITHOUT ANY WARRANTY, to the extent permitted by law; without even + the implied warranty of MERCHANTABILITY or FITNESS FOR A + PARTICULAR PURPOSE. + + + Intro + ----- + + GnuPG is GNU's tool for secure communication and data storage. + It can be used to encrypt data and to create digital signatures. + It includes an advanced key management facility and is compliant + with the proposed OpenPGP Internet standard as described in RFC2440. + + GnuPG works best on GNU/Linux or *BSD systems. Most other Unices + are also supported but are not as well tested as the Free Unices. + See http://www.gnupg.org/download/supported_systems.html for a + list of systems which are known to work. + + See the file COPYING for copyright and warranty information. + + Because GnuPG does not use use any patented algorithms it is not + by default fully compatible with PGP 2.x, which uses the patented + IDEA algorithm. See http://www.gnupg.org/why-not-idea.html for + more information on this subject, including what to do if you are + legally entitled to use IDEA. + + The default public key algorithms are DSA and Elgamal, but RSA is + also supported. Symmetric algorithms available are AES (with 128, + 192, and 256 bit keys), 3DES, Blowfish, CAST5 and Twofish. Digest + algorithms available are MD5, RIPEMD/160, SHA-1, SHA-256, SHA-384, + and SHA-512. Compression algorithms available are ZIP, ZLIB, and + BZIP2 (with libbz2 installed). + + + Installation + ------------ + + Please read the file INSTALL and the sections in this file + related to the installation. Here is a quick summary: + + 1) Check that you have unmodified sources. See below on how to do + this. Don't skip it - this is an important step! + + 2) Unpack the tarball. With GNU tar you can do it this way: + "tar xzvf gnupg-x.y.z.tar.gz". If got a bzip2 compressed + tarball you need to use: "tar xjvf gnupg-x.y.z.tar.bz2". + + 3) "cd gnupg-x.y.z" + + 4) "./configure" + + 5) "make" + + 6) "make install" + + 7) You end up with a "gpg" binary in /usr/local/bin. + + 8) To avoid swapping out of sensitive data, you can install "gpg" + setuid root. If you don't do so, you may want to add the + option "no-secmem-warning" to ~/.gnupg/gpg.conf + + + How to Verify the Source + ------------------------ + + In order to check that the version of GnuPG which you are going to + install is an original and unmodified one, you can do it in one of + the following ways: + + a) If you already have a trusted Version of GnuPG installed, you + can simply check the supplied signature: + + $ gpg --verify gnupg-x.y.z.tar.gz.sig + + This checks that the detached signature gnupg-x.y.z.tar.gz.sig + is indeed a signature of gnupg-x.y.z.tar.gz. The key currently + used to create this signature is: + + "pub 1024R/1CE0C630 2006-01-01 Werner Koch (dist sig) " + + If you do not have this key, you can get it from the source in + the file doc/samplekeys.asc (use "gpg --import doc/samplekeys.asc" + to add it to the keyring) or from any keyserver. You have to + make sure that this is really the key and not a faked one. You + can do this by comparing the output of: + + $ gpg --fingerprint 0x1CE0C630 + + with the fingerprint published elsewhere. + + Please note, that you have to use an old version of GnuPG to + do all this stuff. *Never* use the version which you are going + to check! + + + b) If you don't have any of the above programs, you have to verify + the SHA1 checksum: + + $ sha1sum gnupg-x.y.z.tar.gz + + This should yield an output _similar_ to this: + + fd9351b26b3189c1d577f0970f9dcadc1234abcd gnupg-x.y.z.tar.gz + + Now check that this checksum is _exactly_ the same as the one + published via the announcement list and probably via Usenet. + + + Documentation + ------------- + + The manual will be distributed separately under the name "gph". + An online version of the latest manual draft is available at the + GnuPG web pages: + + http://www.gnupg.org/documentation/ + + A list of frequently asked questions is available in the GnuPG + distribution in the file doc/FAQ and online as: + + http://www.gnupg.org/documentation/faqs.html + + A couple of HOWTO documents are available online; for a listing see: + + http://www.gnupg.org/documentation/howtos.html + + A man page with a description of all commands and options gets installed + along with the program. + + + Introduction + ------------ + + Here is a brief overview on how to use GnuPG - it is strongly suggested + that you read the manual and other information about the use of + cryptography. GnuPG is only a tool, secure usage requires that + YOU KNOW WHAT YOU ARE DOING. + + The first time you run gpg, it will create a .gnupg directory in + your home directory and populate it with a default configuration + file. Once this is done, you may create a new key, or if you + already have keyrings from PGP, you can import them into GnuPG + with: + + gpg --import path/to/pgp/keyring/pubring.pkr + and + gpg --import path/to/pgp/keyring/secring.skr + + The normal way to create a key is + + gpg --gen-key + + This asks some questions and then starts key generation. To create + good random numbers for the key parameters, GnuPG needs to gather + enough noise (entropy) from your system. If you see no progress + during key generation you should start some other activities such + as moving the mouse or hitting the CTRL and SHIFT keys. + + Generate a key ONLY on a machine where you have direct physical + access - don't do it over the network or on a machine also used + by others, especially if you have no access to the root account. + + When you are asked for a passphrase use a good one which you can + easily remember. Don't make the passphrase too long because you + have to type it for every decryption or signing; but, - AND THIS + IS VERY IMPORTANT - use a good one that is not easily to guess + because the security of the whole system relies on your secret key + and the passphrase that protects it when someone gains access to + your secret keyring. One good way to select a passphrase is to + figure out a short nonsense sentence which makes some sense for + you and modify it by inserting extra spaces, non-letters and + changing the case of some characters - this is really easy to + remember especially if you associate some pictures with it. + + Next, you should create a revocation certificate in case someone + gets knowledge of your secret key or you forgot your passphrase + + gpg --gen-revoke your_user_id + + Run this command and store the revocation certificate away. The output + is always ASCII armored, so that you can print it and (hopefully + never) re-create it if your electronic media fails. + + Now you can use your key to create digital signatures + + gpg -s file + + This creates a file "file.gpg" which is compressed and has a + signature attached. + + gpg -sa file + + Same as above, but creates a file "file.asc" which is ASCII armored + and and ready for sending by mail. It is better to use your + mailers features to create signatures (The mailer uses GnuPG to do + this) because the mailer has the ability to MIME encode such + signatures - but this is not a security issue. + + gpg -s -o out file + + Creates a signature of "file", but writes the output to the file + "out". + + Everyone who knows your public key (you can and should publish + your key by putting it on a key server, a web page or in your .plan + file) is now able to check whether you really signed this text + + gpg --verify file + + GnuPG now checks whether the signature is valid and prints an + appropriate message. If the signature is good, you know at least + that the person (or machine) has access to the secret key which + corresponds to the published public key. + + If you run gpg without an option it will verify the signature and + create a new file that is identical to the original. gpg can also + run as a filter, so that you can pipe data to verify trough it + + cat signed-file | gpg | wc -l + + which will check the signature of signed-file and then display the + number of lines in the original file. + + To send a message encrypted to someone you can use + + gpg -e -r heine file + + This encrypts "file" with the public key of the user "heine" and + writes it to "file.gpg" + + echo "hello" | gpg -ea -r heine | mail heine + + Ditto, but encrypts "hello\n" and mails it as ASCII armored message + to the user with the mail address heine. + + gpg -se -r heine file + + This encrypts "file" with the public key of "heine" and writes it + to "file.gpg" after signing it with your user id. + + gpg -se -r heine -u Suttner file + + Ditto, but sign the file with your alternative user id "Suttner" + + + GnuPG has some options to help you publish public keys. This is + called "exporting" a key, thus + + gpg --export >all-my-keys + + exports all the keys in the keyring and writes them (in a binary + format) to "all-my-keys". You may then mail "all-my-keys" as an + MIME attachment to someone else or put it on an FTP server. To + export only some user IDs, you give them as arguments on the command + line. + + To mail a public key or put it on a web page you have to create + the key in ASCII armored format + + gpg --export --armor | mail panther@tiger.int + + This will send all your public keys to your friend panther. + + If you have received a key from someone else you can put it + into your public keyring. This is called "importing" + + gpg --import [filenames] + + New keys are appended to your keyring and already existing + keys are updated. Note that GnuPG does not import keys that + are not self-signed. + + Because anyone can claim that a public key belongs to her + we must have some way to check that a public key really belongs + to the owner. This can be achieved by comparing the key during + a phone call. Sure, it is not very easy to compare a binary file + by reading the complete hex dump of the file - GnuPG (and nearly + every other program used for management of cryptographic keys) + provides other solutions. + + gpg --fingerprint + + prints the so called "fingerprint" of the given username which + is a sequence of hex bytes (which you may have noticed in mail + sigs or on business cards) that uniquely identifies the public + key - different keys will always have different fingerprints. + It is easy to compare fingerprints by phone and I suggest + that you print your fingerprint on the back of your business + card. To see the fingerprints of the secondary keys, you can + give the command twice; but this is normally not needed. + + If you don't know the owner of the public key you are in trouble. + Suppose however that friend of yours knows someone who knows someone + who has met the owner of the public key at some computer conference. + Suppose that all the people between you and the public key holder + may now act as introducers to you. Introducers signing keys thereby + certify that they know the owner of the keys they sign. If you then + trust all the introducers to have correctly signed other keys, you + can be be sure that the other key really belongs to the one who + claims to own it. + + There are 2 steps to validate a key: + 1. First check that there is a complete chain + of signed keys from the public key you want to use + and your key and verify each signature. + 2. Make sure that you have full trust in the certificates + of all the introduces between the public key holder and + you. + Step 2 is the more complicated part because there is no easy way + for a computer to decide who is trustworthy and who is not. GnuPG + leaves this decision to you and will ask you for a trust value + (here also referenced as the owner-trust of a key) for every key + needed to check the chain of certificates. You may choose from: + a) "I don't know" - then it is not possible to use any + of the chains of certificates, in which this key is used + as an introducer, to validate the target key. Use this if + you don't know the introducer. + b) "I do not trust" - Use this if you know that the introducer + does not do a good job in certifying other keys. The effect + is the same as with a) but for a) you may later want to + change the value because you got new information about this + introducer. + c) "I trust marginally" - Use this if you assume that the + introducer knows what he is doing. Together with some + other marginally trusted keys, GnuPG validates the target + key then as good. + d) "I fully trust" - Use this if you really know that this + introducer does a good job when certifying other keys. + If all the introducer are of this trust value, GnuPG + normally needs only one chain of signatures to validate + a target key okay. (But this may be adjusted with the help + of some options). + This information is confidential because it gives your personal + opinion on the trustworthiness of someone else. Therefore this data + is not stored in the keyring but in the "trustdb" + (~/.gnupg/trustdb.gpg). Do not assign a high trust value just + because the introducer is a friend of yours - decide how well she + understands the implications of key signatures and you may want to + tell her more about public key cryptography so you can later change + the trust value you assigned. + + Okay, here is how GnuPG helps you with key management. Most stuff + is done with the --edit-key command + + gpg --edit-key + + GnuPG displays some information about the key and then prompts + for a command (enter "help" to see a list of commands and see + the man page for a more detailed explanation). To sign a key + you select the user ID you want to sign by entering the number + that is displayed in the leftmost column (or do nothing if the + key has only one user ID) and then enter the command "sign" and + follow all the prompts. When you are ready, give the command + "save" (or use "quit" to cancel your actions). + + If you want to sign the key with another of your user IDs, you + must give an "-u" option on the command line together with the + "--edit-key". + + Normally you want to sign only one user ID because GnuPG + uses only one and this keeps the public key certificate + small. Because such key signatures are very important you + should make sure that the signatories of your key sign a user ID + which is very likely to stay for a long time - choose one with an + email address you have full control of or do not enter an email + address at all. In future GnuPG will have a way to tell which + user ID is the one with an email address you prefer - because + you have no signatures on this email address it is easy to change + this address. Remember, your signatories sign your public key (the + primary one) together with one of your user IDs - so it is not possible + to change the user ID later without voiding all the signatures. + + Tip: If you hear about a key signing party on a computer conference + join it because this is a very convenient way to get your key + certified (But remember that signatures have nothing to to with the + trust you assign to a key). + + + 8 Ways to Specify a User ID + ---------=----------------- + + There are several ways to specify a user ID, here are some examples. + + * Only by the short keyid (prepend a zero if it begins with A..F): + + "234567C4" + "0F34E556E" + "01347A56A" + "0xAB123456 + + * By a complete keyid: + + "234AABBCC34567C4" + "0F323456784E56EAB" + "01AB3FED1347A5612" + "0x234AABBCC34567C4" + + * By a fingerprint: + + "1234343434343434C434343434343434" + "123434343434343C3434343434343734349A3434" + "0E12343434343434343434EAB3484343434343434" + + The first one is a short fingerprint for PGP 2.x style keys. + The others are long fingerprints for OpenPGP keys. + + * By an exact string: + + "=Heinrich Heine " + + * By an email address: + + "" + + * By word match + + "+Heinrich Heine duesseldorf" + + All words must match exactly (not case sensitive) and appear in + any order in the user ID. Words are any sequences of letters, + digits, the underscore and characters with bit 7 set. + + * Or by the usual substring: + + "Heine" + "*Heine" + + The '*' indicates substring search explicitly. + + + Batch mode + ---------- + + If you use the option "--batch", GnuPG runs in non-interactive mode and + never prompts for input data. This does not even allow entering the + passphrase. Until we have a better solution (something like ssh-agent), + you can use the option "--passphrase-fd n", which works like PGP's + PGPPASSFD. + + Batch mode also causes GnuPG to terminate as soon as a BAD signature is + detected. + + + Exit status + ----------- + + GnuPG returns with an exit status of 1 if in batch mode and a bad signature + has been detected or 2 or higher for all other errors. You should parse + stderr or, better, the output of the fd specified with --status-fd to get + detailed information about the errors. + + + Configure options + ----------------- + + Here is a list of configure options which are sometime useful + for installation. + + --enable-static-rnd= + Force the use of the random byte gathering + module . Default is either to use /dev/random + or the auto mode. Value for name: + egd - Use the module which accesses the + Entropy Gathering Daemon. See the webpages + for more information about it. + unix - Use the standard Unix module which does not + have a very good performance. + linux - Use the module which accesses /dev/random. + This is the first choice and the default one + for GNU/Linux or *BSD. + auto - Compile linux, egd and unix in and + automagically select at runtime. + + --with-egd-socket= + This is only used when EGD is used as random + gatherer. GnuPG uses by default "~/.gnupg/entropy" + as the socket to connect EGD. Using this option the + socket name can be changed. You may use any filename + here with 2 exceptions: a filename starting with + "~/" uses the socket in the home directory of the user + and one starting with a "=" uses a socket in the + GnuPG home directory which is "~/.gnupg" by default. + + --without-readline + Do not include support for the readline library + even if it is available. The default is to check + whether the readline library is a available and + use it to allow fancy command line editing. + + --with-included-zlib + Forces usage of the local zlib sources. Default is + to use the (shared) library of the system. + + --with-zlib= + Look for the system zlib in DIR. + + --with-bzip2= + Look for the system libbz2 in DIR. + + --without-bzip2 + Disable the BZIP2 compression algorithm. + + --with-included-gettext + Forces usage of the local gettext sources instead of + the one provided by your system. + + --disable-nls + Disable NLS support (See the file ABOUT-NLS) + + --enable-m-guard + Enable the integrated malloc checking code. Please + note that this feature does not work on all CPUs + (e.g. SunOS 5.7 on UltraSparc-2) and might give + you a bus error. + + --disable-dynload + If you have problems with dynamic loading, this + option disables all dynamic loading stuff. Note + that the use of dynamic linking is very limited. + + --disable-asm + Do not use assembler modules. It is not possible + to use this on some CPU types. + + --disable-exec + Disable all remote program execution. This + disables photo ID viewing as well as all keyserver + access. + + --disable-photo-viewers + Disable only photo ID viewing. + + --disable-keyserver-helpers + Disable only keyserver helpers. + + --disable-keyserver-path + Disables the user's ability to use the exec-path + feature to add additional search directories when + executing a keyserver helper. + + --with-photo-viewer=FIXED_VIEWER + Force the photo viewer to be FIXED_VIEWER and + disable any ability for the user to change it in + their options file. + + --disable-rsa + Removes support for the RSA public key algorithm. + This can give a smaller gpg binary for places + where space is tight. + + --disable-idea + --disable-cast5 + --disable-blowfish + --disable-aes + --disable-twofish + --disable-sha256 + --disable-sha512 + Removes support for the selected symmetric or hash + algorithm. This can give a smaller gpg binary for + places where space is tight. + + **** Note that if there are existing keys that + have one of these algorithms as a preference, + messages may be received that use one of these + algorithms and you will not be able to decrypt the + message! **** + + The public key preference list can be updated to + match the list of available algorithms by using + "gpg --edit-key (thekey)", and running the + "setpref" command. + + --enable-minimal + Build the smallest gpg binary possible (disables + all optional algorithms, disables keyserver + access, and disables photo IDs). Specifically, + this means --disable-rsa --disable-idea, + --disable-cast5, --disable-blowfish, + --disable-aes, --disable-twofish, + --disable-sha256, --disable-sha512, + --without-bzip2, --disable-exec, + --disable-card-support and + --disable-agent-support. + Configure command lines are read from left to + right, so if you want to have an "almost minimal" + configuration, you can do (for example) + "--enable-minimal --enable-rsa" to have RSA added + to the minimal build. + + --enable-key-cache=SIZE + Set the internal key and UID cache size. This has + a significant impact on performance with large + keyrings. The default is 4096, but for use on + platforms where memory is an issue, it can be set + as low as 5. + + --disable-card-support + Do not include smartcard support. The default is + to include support if all required libraries are + available. + + --disable-agent-support + Do not include support for the gpg-agent. The + default is to include support. + + --enable-selinux-support + This prevents access to certain files and won't + allow import or export of secret keys. + + --enable-noexecstack + Pass option --noexecstack to as. Autdetect wether + the tool chain actually support this. + + --disable-gnupg-iconv + If iconv is available it is used to convert + between utf-8 and the system character set. This + is in general the preferable solution. However + the code is new and under some cirumstances it may + give different output than with the limited old + support. This option allows to explicity disable + the use of iconv. Note, that iconv is also + disabled if gettext has been disabled. + + + Installation Problems + --------------------- + + If you get unresolved externals "gettext" you should run configure + again with the option "--with-included-gettext"; this is version + 0.12.1 which is available at ftp.gnu.org. + + If you have other compile problems, try the configure options + "--with-included-zlib" or "--disable-nls" (See ABOUT-NLS) or + --disable-dynload. + + We can't check all assembler files, so if you have problems + assembling them (or the program crashes) use --disable-asm with + ./configure. If you opt to delete individual replacement files in + hopes of using the remaining ones, be aware that the configure + scripts may consider several subdirectories to get all available + assembler files; be sure to delete the correct ones. The assembler + replacements are in C and in mpi/generic; never delete + udiv-qrnnd.S in any CPU directory, because there may be no C + substitute. Don't forget to delete "config.cache" and run + "./config.status --recheck". We have also heard reports of + problems when using versions of gcc earlier than 2.96 along with a + non-GNU assembler (as). If this applies to your platform, you can + either upgrade gcc to a more recent version, or use the GNU + assembler. + + Some make tools are broken - the best solution is to use GNU's + make. Try gmake or grab the sources from a GNU archive and + install them. + + On some OSF systems you may get unresolved externals. This is a + libtool problem and the workaround is to manually remove all the + "-lc -lz" but the last one from the linker line and execute them + manually. + + On some architectures you see warnings like: + longlong.h:175: warning: function declaration isn't a prototype + or + http.c:647: warning: cast increases required alignment of target type + This doesn't matter and we know about it (actually it is due to + some warning options which we have enabled for gcc) + + If you are cross-compiling and you get an error either building a + tool called "yat2m" or running that tool, the problem is most + likely a bad or missing native compiler. We require a standard + C-89 compiler to produce an executable to be run on the build + platform. You can explicitly set such a compiler with configure + arguments. On HP/UX you might want to try: "CC_FOR_BUILD=c89". + + + + Specific problems on some machines + ---------------------------------- + + * Apple Darwin 6.1: + + ./configure --with-libiconv-prefix=/sw + + * IBM RS/6000 running AIX: + + Due to a change in gcc (since version 2.8) the MPI stuff may + not build. In this case try to run configure using: + CFLAGS="-g -O2 -mcpu=powerpc" ./configure + + * SVR4.2 (ESIX V4.2 cc) + + Due to problems with the ESIX as, you probably want to do + CFLAGS="-O -K pentium" ./configure --disable-asm + + * SunOS 4.1.4 + + ./configure ac_cv_sys_symbol_underscore=yes + + + The Random Device + ----------------- + + Random devices are available in Linux, FreeBSD and OpenBSD. + Operating systems without a random devices must use another + entropy collector. + + This collector works by running a lot of commands that yield more + or less unpredictable output and feds this as entropy into the + random generator - It should work reliably but you should check + whether it produces good output for your version of Unix. There + are some debug options to help you (see cipher/rndunix.c). + + + Creating an RPM package + ----------------------- + + The file scripts/gnupg.spec is used to build a RPM package (both + binary and src): + 1. copy the spec file into /usr/src/redhat/SPECS + 2. copy the tar file into /usr/src/redhat/SOURCES + 3. type: rpm -ba SPECS/gnupg.spec + + Or use the -t (--tarbuild) option of rpm: + 1. rpm -ta gnupg-x.x.x.tar.gz + + The binary rpm file can now be found in /usr/src/redhat/RPMS, source + rpm in /usr/src/redhat/SRPMS + + + Building Universal Binaries on Apple OS X + ----------------------------------------- + + You can build a universal ("fat") binary that will work on both + PPC and Intel Macs with something like: + + ./configure CFLAGS="-arch ppc -arch i386" --disable-endian-check \ + --disable-dependency-tracking --disable-asm + + If you are doing the build on a OS X 10.4 (Tiger) PPC machine you + may need to add "-isysroot /Developer/SDKs/MacOSX10.4u.sdk" to + those CFLAGS. This additional isysroot is not necessary on Intel + Tiger boxes, or any OS X 10.5 (Leopard) or later boxes. + + Note that when building a universal binary, any third-party + libraries you may link with need to be universal as well. All + Apple-supplied libraries (even libraries not originally written by + Apple like curl, zip, and BZ2) are universal. + + + GnuPG 1.4 and GnuPG 2.0 + ----------------------- + + GnuPG 2.0 is a newer version of GnuPG with additional support for + S/MIME. It has a different design philosophy that splits + functionality up into several modules. Both versions may be + installed simultaneously without any conflict (gpg is called gpg2 + in GnuPG 2). In fact, the gpg version from GnuPG 1.4 is able to + make use of the gpg-agent as included in GnuPG 2 and allows for + seamless passphrase caching. The advantage of GnupG 1.4 is its + smaller size and no dependency on other modules at run and build + time. + + + How to Get More Information + --------------------------- + + The primary WWW page is "http://www.gnupg.org" + The primary FTP site is "ftp://ftp.gnupg.org/gcrypt/" + + See http://www.gnupg.org/download/mirrors.html for a list of + mirrors and use them if possible. You may also find GnuPG + mirrored on some of the regular GNU mirrors. + + We have some mailing lists dedicated to GnuPG: + + gnupg-announce@gnupg.org For important announcements like + new versions and such stuff. + This is a moderated list and has + very low traffic. Do not post to + this list. + + gnupg-users@gnupg.org For general user discussion and + help (English). + + gnupg-de@gnupg.org German speaking counterpart of + gnupg-users. + + gnupg-ru@gnupg.org Russian speaking counterpart of + gnupg-users. + + gnupg-devel@gnupg.org GnuPG developers main forum. + + You subscribe to one of the list by sending mail with a subject + of "subscribe" to x-request@gnupg.org, where x is the name of the + mailing list (gnupg-announce, gnupg-users, etc.). An archive of + the mailing lists are available at + http://www.gnupg.org/documentation/mailing-lists.html + + Please direct bug reports to http://bugs.gnupg.org or post + them direct to the mailing list . + + Please direct questions about GnuPG to the users mailing list or + one of the pgp newsgroups; please do not direct questions to one + of the authors directly as we are busy working on improvements and + bug fixes. The English and German mailing lists are watched by + the authors and we try to answer questions when time allows us to + do so. + + Commercial grade support for GnuPG is available; please see + http://www.gnupg.org/service.html . diff --git a/bin/gpg.exe b/bin/gpg.exe new file mode 100644 index 0000000..3cf1811 Binary files /dev/null and b/bin/gpg.exe differ diff --git a/release/bin/gpg.exe b/release/bin/gpg.exe deleted file mode 100644 index 3cf1811..0000000 Binary files a/release/bin/gpg.exe and /dev/null differ -- cgit v1.2.3