tNew repository for Tomb first public release (see changelog for history) - tomb - the crypto undertaker (HTM) git clone git://parazyd.org/tomb.git (DIR) Log (DIR) Files (DIR) Refs (DIR) README (DIR) LICENSE --- (DIR) commit f8ed58afc3bd69e3e4285ca2db219d465f59b369 (HTM) Author: Jaromil <jaromil@dyne.org> Date: Sun, 22 Aug 2010 15:04:19 +0200 New repository for Tomb first public release (see changelog for history) Diffstat: A .gitignore | 23 +++++++++++++++++++++++ A AUTHORS | 1 + A COPYING | 674 +++++++++++++++++++++++++++++++ A ChangeLog | 29 +++++++++++++++++++++++++++++ A INSTALL | 302 +++++++++++++++++++++++++++++++ A Makefile.am | 1 + A NEWS | 0 A README | 18 ++++++++++++++++++ A configure.ac | 114 +++++++++++++++++++++++++++++++ A src/Makefile.am | 1 + A src/tomb | 588 +++++++++++++++++++++++++++++++ 11 files changed, 1751 insertions(+), 0 deletions(-) --- (DIR) diff --git a/.gitignore b/.gitignore t@@ -0,0 +1,23 @@ +\#* +.\#* +*~ +!autogen.sh +aclocal.m4 +autom4te.cache +config.guess +config.h +config.log +config.php +config.status +config.sub +configure +config.h.in +depcomp +install-sh +libtool +ltmain.sh +Makefile +Makefile.in +missing +stamp-h1 +tags (DIR) diff --git a/AUTHORS b/AUTHORS t@@ -0,0 +1 @@ +Denis Roio <jaromil@dyne.org (DIR) diff --git a/COPYING b/COPYING t@@ -0,0 +1,674 @@ + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> + 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. + + <one line to give the program's name and a brief idea of what it does.> + Copyright (C) <year> <name of author> + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation, either version 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 <http://www.gnu.org/licenses/>. + +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: + + <program> Copyright (C) <year> <name of author> + 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 +<http://www.gnu.org/licenses/>. + + 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 +<http://www.gnu.org/philosophy/why-not-lgpl.html>. (DIR) diff --git a/ChangeLog b/ChangeLog t@@ -0,0 +1,29 @@ + +August 2010 + + The first public version of Tomb is released to the public + + +During the year 2009 + + Tomb has been extensively tested, perfectioned and documented + after being used by its author + +Sometime in 2007 + + mknest was refactored to work on the Debian distribution and since + then renamed to Tomb. dyne:bolic specific dependencies where + removed, keeping Zsh as the shell script it is written with. + + + +Back in 2005 + + The "nesting" feature of dyne:bolic GNU/Linux lets users encrypt + their home in a file, using a shell script and a graphical + interface called Taschino. + + Taschino included a shell script wrapping cryptsetup to encrypt + loopback mounted partitions with the algo AES-256 (cbc-essiv + mode): this script was called 'mkNest' and its the ancestor of + Tomb. (DIR) diff --git a/INSTALL b/INSTALL t@@ -0,0 +1,302 @@ +Installation Instructions +************************* + +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, +2006, 2007, 2008, 2009 Free Software Foundation, Inc. + + This file is free documentation; the Free Software Foundation gives +unlimited permission to copy, distribute and modify it. + +Basic Installation +================== + + Briefly, the shell commands `./configure; make; make install' should +configure, build, and install this package. The following +more-detailed instructions are generic; see the `README' file for +instructions specific to this package. + + The `configure' shell script attempts to guess correct values for +various system-dependent variables used during compilation. It uses +those values to create a `Makefile' in each directory of the package. +It may also create one or more `.h' files containing system-dependent +definitions. Finally, it creates a shell script `config.status' that +you can run in the future to recreate the current configuration, and a +file `config.log' containing compiler output (useful mainly for +debugging `configure'). + + It can also use an optional file (typically called `config.cache' +and enabled with `--cache-file=config.cache' or simply `-C') that saves +the results of its tests to speed up reconfiguring. Caching is +disabled by default to prevent problems with accidental use of stale +cache files. + + If you need to do unusual things to compile the package, please try +to figure out how `configure' could check whether to do them, and mail +diffs or instructions to the address given in the `README' so they can +be considered for the next release. If you are using the cache, and at +some point `config.cache' contains results you don't want to keep, you +may remove or edit it. + + The file `configure.ac' (or `configure.in') is used to create +`configure' by a program called `autoconf'. You need `configure.ac' if +you want to change it or regenerate `configure' using a newer version +of `autoconf'. + +The simplest way to compile this package is: + + 1. `cd' to the directory containing the package's source code and type + `./configure' to configure the package for your system. + + Running `configure' might take a while. While running, it prints + some messages telling which features it is checking for. + + 2. Type `make' to compile the package. + + 3. Optionally, type `make check' to run any self-tests that come with + the package. + + 4. Type `make install' to install the programs and any data files and + documentation. + + 5. You can remove the program binaries and object files from the + source code directory by typing `make clean'. To also remove the + files that `configure' created (so you can compile the package for + a different kind of computer), type `make distclean'. There is + also a `make maintainer-clean' target, but that is intended mainly + for the package's developers. If you use it, you may have to get + all sorts of other programs in order to regenerate files that came + with the distribution. + + 6. Often, you can also type `make uninstall' to remove the installed + files again. + +Compilers and Options +===================== + + Some systems require unusual options for compilation or linking that +the `configure' script does not know about. Run `./configure --help' +for details on some of the pertinent environment variables. + + You can give `configure' initial values for configuration parameters +by setting variables in the command line or in the environment. Here +is an example: + + ./configure CC=c99 CFLAGS=-g LIBS=-lposix + + *Note Defining Variables::, for more details. + +Compiling For Multiple Architectures +==================================== + + You can compile the package for more than one kind of computer at the +same time, by placing the object files for each architecture in their +own directory. To do this, you can use GNU `make'. `cd' to the +directory where you want the object files and executables to go and run +the `configure' script. `configure' automatically checks for the +source code in the directory that `configure' is in and in `..'. + + With a non-GNU `make', it is safer to compile the package for one +architecture at a time in the source code directory. After you have +installed the package for one architecture, use `make distclean' before +reconfiguring for another architecture. + + On MacOS X 10.5 and later systems, you can create libraries and +executables that work on multiple system types--known as "fat" or +"universal" binaries--by specifying multiple `-arch' options to the +compiler but only a single `-arch' option to the preprocessor. Like +this: + + ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ + CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ + CPP="gcc -E" CXXCPP="g++ -E" + + This is not guaranteed to produce working output in all cases, you +may have to build one architecture at a time and combine the results +using the `lipo' tool if you have problems. + +Installation Names +================== + + By default, `make install' installs the package's commands under +`/usr/local/bin', include files under `/usr/local/include', etc. You +can specify an installation prefix other than `/usr/local' by giving +`configure' the option `--prefix=PREFIX'. + + You can specify separate installation prefixes for +architecture-specific files and architecture-independent files. If you +pass the option `--exec-prefix=PREFIX' to `configure', the package uses +PREFIX as the prefix for installing programs and libraries. +Documentation and other data files still use the regular prefix. + + In addition, if you use an unusual directory layout you can give +options like `--bindir=DIR' to specify different values for particular +kinds of files. Run `configure --help' for a list of the directories +you can set and what kinds of files go in them. + + If the package supports it, you can cause programs to be installed +with an extra prefix or suffix on their names by giving `configure' the +option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. + +Optional Features +================= + + Some packages pay attention to `--enable-FEATURE' options to +`configure', where FEATURE indicates an optional part of the package. +They may also pay attention to `--with-PACKAGE' options, where PACKAGE +is something like `gnu-as' or `x' (for the X Window System). The +`README' should mention any `--enable-' and `--with-' options that the +package recognizes. + + For packages that use the X Window System, `configure' can usually +find the X include and library files automatically, but if it doesn't, +you can use the `configure' options `--x-includes=DIR' and +`--x-libraries=DIR' to specify their locations. + +Particular systems +================== + + On HP-UX, the default C compiler is not ANSI C compatible. If GNU +CC is not installed, it is recommended to use the following options in +order to use an ANSI C compiler: + + ./configure CC="cc -Ae -D_XOPEN_SOURCE=500" + +and if that doesn't work, install pre-built binaries of GCC for HP-UX. + + On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot +parse its `<wchar.h>' header file. The option `-nodtk' can be used as +a workaround. If GNU CC is not installed, it is therefore recommended +to try + + ./configure CC="cc" + +and if that doesn't work, try + + ./configure CC="cc -nodtk" + + On Solaris, don't put `/usr/ucb' early in your `PATH'. This +directory contains several dysfunctional programs; working variants of +these programs are available in `/usr/bin'. So, if you need `/usr/ucb' +in your `PATH', put it _after_ `/usr/bin'. + + On Haiku, software installed for all users goes in `/boot/common', +not `/usr/local'. It is recommended to use the following options: + + ./configure --prefix=/boot/common + +Specifying the System Type +========================== + + There may be some features `configure' cannot figure out +automatically, but needs to determine by the type of machine the package +will run on. Usually, assuming the package is built to be run on the +_same_ architectures, `configure' can figure that out, but if it prints +a message saying it cannot guess the machine type, give it the +`--build=TYPE' option. TYPE can either be a short name for the system +type, such as `sun4', or a canonical name which has the form: + + CPU-COMPANY-SYSTEM + +where SYSTEM can have one of these forms: + + OS + KERNEL-OS + + See the file `config.sub' for the possible values of each field. If +`config.sub' isn't included in this package, then this package doesn't +need to know the machine type. + + If you are _building_ compiler tools for cross-compiling, you should +use the option `--target=TYPE' to select the type of system they will +produce code for. + + If you want to _use_ a cross compiler, that generates code for a +platform different from the build platform, you should specify the +"host" platform (i.e., that on which the generated programs will +eventually be run) with `--host=TYPE'. + +Sharing Defaults +================ + + If you want to set default values for `configure' scripts to share, +you can create a site shell script called `config.site' that gives +default values for variables like `CC', `cache_file', and `prefix'. +`configure' looks for `PREFIX/share/config.site' if it exists, then +`PREFIX/etc/config.site' if it exists. Or, you can set the +`CONFIG_SITE' environment variable to the location of the site script. +A warning: not all `configure' scripts look for a site script. + +Defining Variables +================== + + Variables not defined in a site shell script can be set in the +environment passed to `configure'. However, some packages may run +configure again during the build, and the customized values of these +variables may be lost. In order to avoid this problem, you should set +them in the `configure' command line, using `VAR=value'. For example: + + ./configure CC=/usr/local2/bin/gcc + +causes the specified `gcc' to be used as the C compiler (unless it is +overridden in the site shell script). + +Unfortunately, this technique does not work for `CONFIG_SHELL' due to +an Autoconf bug. Until the bug is fixed you can use this workaround: + + CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash + +`configure' Invocation +====================== + + `configure' recognizes the following options to control how it +operates. + +`--help' +`-h' + Print a summary of all of the options to `configure', and exit. + +`--help=short' +`--help=recursive' + Print a summary of the options unique to this package's + `configure', and exit. The `short' variant lists options used + only in the top level, while the `recursive' variant lists options + also present in any nested packages. + +`--version' +`-V' + Print the version of Autoconf used to generate the `configure' + script, and exit. + +`--cache-file=FILE' + Enable the cache: use and save the results of the tests in FILE, + traditionally `config.cache'. FILE defaults to `/dev/null' to + disable caching. + +`--config-cache' +`-C' + Alias for `--cache-file=config.cache'. + +`--quiet' +`--silent' +`-q' + Do not print messages saying which checks are being made. To + suppress all normal output, redirect it to `/dev/null' (any error + messages will still be shown). + +`--srcdir=DIR' + Look for the package's source code in directory DIR. Usually + `configure' can determine that directory automatically. + +`--prefix=DIR' + Use DIR as the installation prefix. *Note Installation Names:: + for more details, including other options available for fine-tuning + the installation locations. + +`--no-create' +`-n' + Run the configure checks, but stop before creating any output + files. + +`configure' also accepts some other, not widely useful, options. Run +`configure --help' for more details. + (DIR) diff --git a/Makefile.am b/Makefile.am t@@ -0,0 +1 @@ +SUBDIRS = src (DIR) diff --git a/NEWS b/NEWS (DIR) diff --git a/README b/README t@@ -0,0 +1,18 @@ + + ..... .. + .H8888888h. ~-. . uW8" + 888888888888x `> u. .. . : `t888 +X~ `?888888hx~ ...ue888b .888: x888 x888. 8888 . +' x8.^"*88*" 888R Y888r ~`8888~'888X`?888f` 9888.z88N + `-:- X8888x 888R I888> X888 888X '888> 9888 888E + 488888> 888R I888> X888 888X '888> 9888 888E + .. `"88* 888R I888> X888 888X '888> 9888 888E + x88888nX" . u8888cJ888 X888 888X '888> 9888 888E + !"*8888888n.. : "*888*P" "*88%""*88" '888!` .8888 888" +' "*88888888* 'Y" `~ " `"` `%888*%" + ^"***"` "` + + a simple commandline tool to manage encrypted storage + by Jaromil + + (DIR) diff --git a/configure.ac b/configure.ac t@@ -0,0 +1,114 @@ +dnl ============================================================== +dnl Process this file with autoconf to produce a configure script. +dnl ============================================================== + +dnl require autoconf 2.62 (AS_ECHO/AS_ECHO_N) +AC_PREREQ([2.60]) + +AC_INIT([Tomb],[0.8.0],[jaromil@dyne.org],[tomb]) +AC_CONFIG_MACRO_DIR([m4]) + +AC_CANONICAL_HOST + +dnl backwards compatibility for autoconf >= 2.64 +dnl PACKAGE_URL should be the fifth argument of AC_INIT +m4_define([AC_PACKAGE_URL], [http://crypto.dyne.org]) +AC_DEFINE(PACKAGE_URL, "AC_PACKAGE_URL", [Package URL]) +AC_SUBST(PACKAGE_URL, AC_PACKAGE_URL) + +dnl ============================================================== +dnl Get the operating system and version number... +dnl ============================================================== +AC_MSG_CHECKING([for which platform we are setting up]) + +case "$host_os" in + *linux*) + AC_MSG_RESULT([Linux]) + have_linux=yes + + if test x$have_x86_64 = xyes; then + have_64bit=yes + fi + + if test x$have_x86_32 = xyes; then + have_32bit=yes + fi + ;; + + *darwin*) + AC_MSG_RESULT([Darwin/OSX]) + have_darwin=yes + ;; + + *freebsd*) + AC_MSG_RESULT([FreeBSD]) + have_freebsd=yes + ;; + + *) + AC_MSG_RESULT([$host_os?!]) + AC_MSG_ERROR([[ +[!] Your system architecture is not supported by AutOrg. +]], 0) + ;; +esac + + +dnl ============================================================== +dnl Setup for automake +dnl ============================================================== + +AM_INIT_AUTOMAKE([dist-bzip2 subdir-objects -Wno-portability]) +m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])]) + +AC_CONFIG_SRCDIR([src/tomb]) + +dnl Checks for programs. +AC_PROG_INSTALL +AC_PROG_LN_S +AC_PROG_MAKE_SET + +dnl compatibility with older libtool +dnl m4_ifndef([LT_INIT], [AC_PROG_RANLIB]) + + +dnl versioning info for libtool +DYNE_CURRENT=0 +DYNE_REVISION=0 +DYNE_AGE=0 +DYNE_VERSION_INFO="$DYNE_CURRENT:$DYNE_REVISION:$DYNE_AGE" +dnl Note this is the ABI version which is not the same as our actual +dnl library version +AC_SUBST(DYNE_VERSION_INFO) + + +dnl ########################################################################### +dnl ###### now about compile time paths +AC_MSG_CHECKING([which installation prefix to use]) +if test "x${prefix}" = "xNONE"; then + prefix=`pwd` +fi +AC_MSG_RESULT([${prefix}]) +TOMB_PATH="${prefix}" +AC_SUBST(TOMB_PATH) + + + +dnl alphabetic order on dir/subdir, but Makefile sorts before everything +AC_CONFIG_FILES([ +Makefile +src/Makefile +]) + +AC_OUTPUT + + +dnl autoconf < 2.63 compatibility +m4_ifndef([AS_VAR_APPEND], + AC_DEFUN([AS_VAR_APPEND], $1=$$1$2)) + +dnl convenience function so that INFO messages go to config.log and to stdout, +dnl useful when debugging user problems only config.log is needed + +dnl as above, but no newline at the end + (DIR) diff --git a/src/Makefile.am b/src/Makefile.am t@@ -0,0 +1 @@ + (DIR) diff --git a/src/tomb b/src/tomb t@@ -0,0 +1,588 @@ +#!/bin/zsh +# +# Tomb +# +# a simple commandline tool to create and operate encrypted storage +# +# Copyleft (C) 2007-2010 Denis Roio <jaromil@dyne.org> +# +# thanks to Gabriele "Asbesto Molesto" Zaverio +# for suggesting the perfect name for this tool. +# +# This source code is free software; you can redistribute it and/or +# modify it under the terms of the GNU Public License as published by +# the Free Software Foundation; either version 3 of the License, or +# (at your option) any later version. +# +# This source code 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. +# Please refer to the GNU Public License for more details. +# +# You should have received a copy of the GNU Public License along with +# this source code; if not, write to: +# Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + +VERSION=0.8 +DATE=Aug/2010 + +# standard output message routines +# it's always useful to wrap them, in case we change behaviour later +notice() { echo "[*] $1"; } +act() { echo " . $1"; } +error() { echo "[!] $1"; } +func() { if [ $DEBUG ]; then echo "[D] $1"; fi } + +# user interface (just to ask the password) +ask_password() { + + xhost 2>/dev/null + if [ $? = 0 ]; then # we have access to the X display + + if [ -x /usr/bin/ssh-askpass ]; then # debian has this + export scolopendro="`ssh-askpass "Tomb: provide the password to unlock"`" + return + fi + + else # we'll collect the password from commandline + + act "Tomb: provide the password to unlock" + echo -n " > " + read -s scolopendro + export scolopendro + fi + + # just in case we'd like to have dialog supported too: + # dialog --backtitle "This file is encrypted for privacy protection" \ + # --title "Security check" --insecure \ + # --passwordbox "Enter password:" 10 30 2> /var/run/.scolopendro + +} + +# checks if a file is writable +# differs from -w coz returns true if does not exist but can be created +is_writable() { # arg: filename + + file=$1 + writable=false + + if [ -r $file ]; then # file exists + + if [ -w $file ]; then writable=true; fi + + else # file does not exist + + touch $file 1>/dev/null 2>/dev/null + if [ $? = 0 ]; then + writable=true + rm $file + fi + + fi + + if [ x$writable = xtrue ]; then + echo "true" + else + echo "false" + fi +} + +# appends a new line to a text file, if not duplicate +# it sorts alphabetically the original order of line entries +# defines the APPEND_FILE_CHANGED variable if file changes +append_line() { # args: file new-line + + # first check if the file is writable + # this also creates the file if doesn't exists + if [ `is_writable $1` = false ]; then + error "file $1 is not writable" + error "can't insert line: $2" + return + fi + + tempfile="`basename $1`.append.tmp" + + # create a temporary file and add the line there + cp $1 /tmp/$tempfile + echo "$2" >> /tmp/$tempfile + + # sort and uniq the temp file to temp.2 + cat /tmp/$tempfile | sort | uniq > /tmp/${tempfile}.2 + + SIZE1="`ls -l /tmp/$tempfile | awk '{print $5}'`" + SIZE2="`ls -l /tmp/${tempfile}.2 | awk '{print $5}'`" + if [ $SIZE != $SIZE ]; then + # delete the original + rm -f $1 + # replace it + cp -f /tmp/${tempfile}.2 $1 + # signal the change + APPEND_FILE_CHANGED=true + fi + + # remove the temporary files + rm -f /tmp/$tempfile + rm -f /tmp/${tempfile}.2 + + # and we are done +} + + +PATH=/usr/bin:/usr/sbin:/bin:/sbin + +############################ +### main() +### + +notice "tomb - simple commandline tool for encrypted storage" +act "version $VERSION ($DATE) by Denis J. Roio <jaromil@dyne.org>" +#act "invoked with args \"$*\" " +#act "running on `date`" + +OPTS=`getopt -o hvs:k: -n 'tomb' -- "$@"` + +while true; do + case "$1" in + -h) + notice "SYNOPSIS: tomb [options] COMMAND [FILE|PARTITION] [MOUNTPOINT|NAME]" + notice "OPTIONS:" + act "-h print this help" + act "-v print out the version information for this tool" + act "-s size of the storage file when creating one (in MBytes)" + act "-k path key to be used for decryption (defaults in ~/.tomb)" + notice "COMMANDS:" + act "format format a PARTITION with NAME and generate keys" + act "create create a new encrypted storage FILE and keys" + act "mount mount an existing storage FILE on MOUNTPOINT" + act "umount unmounts a mounted storage MOUNTPOINT" + echo; exit 2 ;; + -v) + act "(c)2007 by Denis Rojo <jaromil@dyne.org> as part of dyne:bolic" + act "thanks to Gabriele \"Asbesto Molesto\" Zaverio" + act "for suggesting the perfect name for this tool" + echo + act " TOMB" + echo + act "This source code is free software; you can redistribute it and/or" + act "modify it under the terms of the GNU Public License as published" + act "by the Free Software Foundation; either version 3 of the License," + act "or (at your option) any later version." + echo + act "This source code is distributed in the hope that it will be useful," + act "but WITHOUT ANY WARRANTY; without even the implied warranty of" + act "MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE." + act "Please refer to the GNU Public License for more details." + echo + act "You should have received a copy of the GNU Public License along with" + act "this source code; if not, write to:" + act "Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA." + echo + act "in case you like to port this tool to any other operating system" + act "please notice us if you succeed, or if you have difficulties you" + act "cannot overcome: http://dyne.org" + echo; exit 2 ;; + -s) SIZE=$2; shift 2 ;; + -k) KEY=$2; shift 2 ;; + --) shift; break ;; + *) CMD=$1; FILE=$2; MOUNT=$3; break ;; + esac +done + +if [ -z $CMD ]; then + error "first argument missing, use -h for help" + exit 0 +fi + +act "command: $CMD for file $FILE" + +tombdir=${HOME}/.tomb +tombtab=${tombdir}/fstab +if ! [ -r ${tombtab} ]; then + act "creating tomb filesystem tab in your home" + mkdir -p ${HOME}/.tomb + echo "# entombed filesystem information, see man tomb" > ${tombtab} + echo "# format here is similar to the system wide fstab" >> ${tombtab} + echo "# <file system> <mount point> <type> <options> <key>" >> ${tombtab} +fi + +format_crypto() { + notice "Formatting partition $FILE as an encrypted storage" + act "give it a name:" + read -s fsname + + act " `fdisk -l | grep ${FILE}`" + mkdir -p /tmp/tomb + + modprobe dm-crypt + modprobe aes-i586 + + act "Generating secret key..." + key="`basename ${FILE}`" + mkdir -p ${HOME}/.tomb + + cat /dev/urandom | strings | dd bs=1 count=256 of=/tmp/tomb/secret + notice "Setup your secret key file ${key}.gpg" + # here user is prompted for password + gpg -o "${HOME}/.tomb/${key}.gpg" --no-options --openpgp -c -a /tmp/tomb/secret + while [ $? = 2 ]; do + gpg -o "${HOME}/.tomb/${key}.gpg" --no-options --openpgp -c -a /tmp/tomb/secret + done + + act "formatting Luks partition" + # dm-crypt only supports sha1 + # but we can use aes-cbc-essiv with sha256 for better security + # see http://clemens.endorphin.org/LinuxHDEncSettings + cryptsetup --cipher aes-cbc-essiv:sha256 --key-size 256 luksFormat ${FILE} /tmp/tomb/secret + if ! [ $? = 0 ]; then + act "operation aborted." + exit 0 + fi + + + cryptsetup --key-file /tmp/tomb/secret --batch-mode --cipher aes luksOpen ${FILE} tomb.tmp + + rm -f /tmp/tomb/secret + + cryptsetup luksDump ${FILE} + + mkfs.ext3 -F -L "${fsname}" -j /dev/mapper/tomb.tmp + + if [ $? = 0 ]; then + act "OK, encrypted partition succesfully formatted with Ext3 filesystem" + else + act "error formatting ${FILE} Ext3 filesystem" + fi + + cryptsetup luksClose tomb.tmp + + notice "done formatting $FILE encrypted partition (using Luks dm-crypt AES/SHA256)" + act "encrypted key stored in file ${tombdir}/${key}.gpg" + append_line ${tombtab} \ + "${FILE} ${tombdir}/`basename ${FILE}` aes-cbc-essiv:sha256 none ${tombdir}/${key}.gpg" +} + +create_crypto() { + + if [ -z $SIZE ]; then + error "size is not specified, please use -s option when creating a storage file" + exit 0 + else + act "size set to $SIZE MB" + fi + + SIZE_4k=`expr \( $SIZE \* 1000 \) / 4` + notice "generating file of ${SIZE}Mb (${SIZE_4k} blocks of 4Kb)" + act "dd if=/dev/zero of=${FILE} bs=4k count=$SIZE_4k" +# now with progress bar! + dd if=/dev/zero bs=4k count=${SIZE_4k} of=${FILE} + + if [ $? = 0 -a -e ${FILE} ]; then + act "OK: `ls -l ${FILE}`" + else + error "Error creating the nest file ${FILE} : (dd if=/dev/zero of=${FILE} bs=4k count=$SIZE_4k)" + sleep 4 + exit 0 + fi + + mkdir -p /tmp/tomb + + modprobe dm-crypt + modprobe aes-i586 + + nstloop=`losetup -f` # get the number for next loopback device + losetup -f ${FILE} # allocates the next loopback for our file + + act "Generating secret key..." + + cat /dev/urandom | strings | dd bs=1 count=256 of=/tmp/tomb/secret + clear + notice "Setup your secret key file ${FILE}.gpg" + # here user is prompted for password + gpg -o "${FILE}.gpg" --no-options --openpgp -c -a /tmp/tomb/secret + while [ $? = 2 ]; do + gpg -o "${FILE}.gpg" --no-options --openpgp -c -a /tmp/tomb/secret + done + + act "formatting Luks mapped device" + # dm-crypt only supports sha1 + # but we can use aes-cbc-essiv with sha256 for better security + # see http://clemens.endorphin.org/LinuxHDEncSettings + cryptsetup --cipher aes-cbc-essiv:sha256 --key-size 256 luksFormat ${nstloop} /tmp/tomb/secret + if ! [ $? = 0 ]; then + act "operation aborted." + exit 0 + fi + + act "formatting Ext3 filesystem" + + cryptsetup --key-file /tmp/tomb/secret --batch-mode --cipher aes luksOpen ${nstloop} tomb.tmp + + rm -f /tmp/tomb/secret + + cryptsetup luksDump ${nstloop} + + mkfs.ext3 -F -j -L "dyne:nest" /dev/mapper/tomb.tmp + + if [ $? = 0 ]; then + act "OK, encrypted storage succesfully formatted with Ext3 filesystem" + else + act "error formatting storage file with Ext3 filesystem" + fi + + cryptsetup luksClose tomb.tmp + losetup -d ${nstloop} + + notice "done creating $FILE encrypted storage (using Luks dm-crypt AES/SHA256)" +} + +mount_crypto() { + if ! [ -r $FILE ]; then + error "file or partition $FILE does not exists" + exit 0 + fi + # check if its a file or partition + file ${FILE} | grep block > /dev/null + if [ $? = 0 ]; then + act "$FILE is a partition" + mount_crypto_partition + else + act "$FILE is a loopback file" + mount_crypto_file + fi +} + +mount_crypto_file() { + + if [ -z $KEY ]; then + enc_key="~/.tomb/`basename $FILE`" + else + enc_key="$KEY" + fi + + notice "mounting $FILE on mountpoint $MOUNT" + if [ -z $MOUNT ]; then + error "you need to specify a MOUNTPOINT for the mount command" + exit 0 + fi + if ! [ -x $MOUNT ]; then + error "mountpoint $MOUNT doesn't exist" + exit 0 + fi + + act "mounting $FILE on mountpoint $MOUNT over loopback device" + nstloop=`losetup -f` + losetup -f ${FILE} + + act "check for a valid LUKS encrypted device" + cryptsetup isLuks ${nstloop} + if [ $? = 0 ]; then # it's a LUKS encrypted nest, see cryptsetup(1) + + # check if key file is present + if ! [ -r "${enc_key}" ]; then + error "encryption key ${enc_key} not found" + error "use -k option to specify which key to use" + losetup -d ${nstloop} + sleep 5 + return + fi + + modprobe dm-crypt + modprobe aes-i586 + + mapper="tomb.`date +%s`" + + notice "Password is required for key ${enc_key}" + for c in 1 2 3; do + + ask_password + + echo "${scolopendro}" \ + | gpg --passphrase-fd 0 --no-tty --no-options \ + -d "${enc_key}" 2>/dev/null \ + | cryptsetup --key-file - luksOpen ${nstloop} ${mapper} + + unset scolopendro + + if [ -r /dev/mapper/${mapper} ]; then + break; # password was correct + fi + + done + + if ! [ -r /dev/mapper/${mapper} ]; then + error "failure mounting the encrypted file" + tail /var/log/messages + losetup -d ${nstloop} + return + fi + + act "encrypted storage filesystem check" + fsck.ext3 -p -C0 /dev/mapper/${mapper} + + mount -t ext3 /dev/mapper/${mapper} ${MOUNT} + + notice "encrypted storage $FILE succesfully mounted on $MOUNT" + append_line /var/run/tombs "${MOUNT} ${mapper} ${nstloop}" + + else + + error "$FILE is not a valid Luks encrypted storage file" + + fi +} + +mount_crypto_partition() { + + if [ -z $KEY ]; then + key=`basename $FILE` + grep -e "^${FILE}" ${tombtab} + if [ $? = 1 ]; then + error "entombed partition $file is not found in ${tombtab}" + error "aborting operation." + exit 1 + fi + if [ -r ${tombdir}/${key}.gpg ]; then + enc_key=${tombdir}/${key}.gpg + else + error "secret encryption key for partition ${FILE} not found in ${tombdir}/${key}.gpg" + error "we cannot decrypt files from partition ${FILE}. sorry." + exit 0 + fi + else + enc_key=${KEY} + act "using key $KEY to unlock" + fi + + + if [ -z $MOUNT ]; then + mount=`grep "^${FILE}" ${tombtab} | awk '{print $2}'` + if ! [ -x $mount ]; then + error "you need to specify a MOUNTPOINT for the mount command" + exit 1 + else + MOUNT=$mount + fi + fi + + notice "mounting entombed partition $FILE on mountpoint $MOUNT" + + if ! [ -x $MOUNT ]; then + error "mountpoint $MOUNT does not exist" + exit 1 + fi + + act "check if nest is a an encrypted Luks device" + cryptsetup isLuks ${FILE} + + if [ $? = 0 ]; then + + act "secret encryption key found in ${enc_key}" + + modprobe dm-crypt + modprobe aes-i586 + + mapper="tomb.${key}.`date +%s`" + + notice "Password is required to unlock the encryption key" + for c in 1 2 3 4 5; do + + ask_password $c + + cat /var/run/.scolopendro \ + | gpg --passphrase-fd 0 --no-tty --no-options \ + -d ${enc_key} 2>/dev/null \ + | cryptsetup --key-file - luksOpen ${FILE} ${mapper} + + rm -f /var/run/.scolopendro + + if [ -r /dev/mapper/${mapper} ]; then + break; # password was correct + else + dialog --sleep 3 --infobox \ + "password invalid, `expr 5 - $attempt` attempts left" 10 30 + fi + + done + + if ! [ -r /dev/mapper/${mapper} ]; then + error "failure mounting the encrypted file" + return # this exits + fi + + act "encrypted storage filesystem check" + fsck.ext3 -p -C0 /dev/mapper/${mapper} + + mount -t ext3 /dev/mapper/${mapper} ${MOUNT} + + notice "encrypted partition $FILE succesfully mounted on $MOUNT" + touch ${tombdir}/mtab + echo "${FILE} ${MOUNT} ${mapper}" >> ${tombdir}/mtab + + else + + error "$FILE is not a valid Luks encrypted partition" + + fi +} + +umount_crypto() { + + if [ -z $FILE ]; then + # TODO: if only one tomb is mounted, unmount that + error "must specify the mountpoint to be unmounted" + exit 0 + fi + + mapper=`mount | grep $FILE | awk '{print $1}'` + + if [ "$mapper" = "" ]; then + error "$FILE is not mounted" + return + fi + + mapper=`basename $mapper` + + if ! [ -r /dev/mapper/${mapper} ]; then + error "tomb doesn't seems to be mounted:" + error "${mapper} is not present in /dev/mapper" + exit 1 + fi + + umount ${FILE} + if ! [ $? = 0 ]; then + error "error occurred in umount ${FILE}" + exit 0 + fi + + cryptsetup luksClose ${mapper} + if ! [ $? = 0 ]; then + error "error occurred in cryptsetup luksClose ${mapper}" + exit 0 + fi + + # echo ${nstloop} | grep loop 1>/dev/null 2>/dev/null + # # if it's a loopback then we need to do losetup -d + # if [ $? = 0 ]; then + # losetup -d ${nstloop} + # if ! [ $? = 0 ]; then + # error "error occurred in losetup -d ${nstloop}" + # exit 0 + # fi + # fi + + if [ $? = 1 ]; then + notice "crypt storage ${mapper} unmounted from $FILE" + fi +} + + +case "$CMD" in + create) create_crypto ;; + format) format_crypto ;; + mount) mount_crypto ;; + umount) umount_crypto ;; + unmount) umount_crypto ;; + *) error "command \"$CMD\" not recognized" + act "try -h for help" + ;; +esac