├── .github └── PULL_REQUEST_TEMPLATE.md ├── .gitignore ├── CHANGELOG ├── CONTRIBUTING.rst ├── COPYING ├── DEVELOPER-CERTIFICATE ├── README.rst ├── debian ├── changelog ├── compat ├── control ├── copyright ├── gbp.conf ├── links ├── rules └── source │ ├── format │ └── lintian-overrides ├── git-remote-gcrypt ├── install.sh ├── redhat └── git-remote-gcrypt.spec └── tests └── system-test.sh /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | Thank you for your interest in contributing to this project! 2 | 3 | Please **do not** submit a pull request on GitHub. This repository is 4 | an automated mirror, and I don't develop using GitHub's platform. 5 | 6 | Instead, please see CONTRIBUTING.md for patch submission info. 7 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | /debian/files 2 | /debian/git-remote-gcrypt.substvars 3 | /debian/git-remote-gcrypt 4 | -------------------------------------------------------------------------------- /CHANGELOG: -------------------------------------------------------------------------------- 1 | debian/changelog -------------------------------------------------------------------------------- /CONTRIBUTING.rst: -------------------------------------------------------------------------------- 1 | Submitting patches 2 | ================== 3 | 4 | Thank you for your interest in contributing to this project! 5 | 6 | Please **do not** submit a pull request on GitHub. The repository 7 | there is an automated mirror, and I don't develop using GitHub's 8 | platform. 9 | 10 | Project mailing lists 11 | ===================== 12 | 13 | There are two low-volume project mailing lists, shared with some other 14 | small free software projects: 15 | 16 | - sgo-software-announce -- 17 | 18 | 19 | For release announcements. 20 | 21 | - sgo-software-discuss -- 22 | 23 | 24 | For bug reports, posting patches, user questions and discussion. 25 | 26 | Please prepend ``[git-remote-gcrypt]`` to the subject line of your e-mail, 27 | and for patches, pass ``--subject-prefix="PATCH git-remote-gcrypt"`` to 28 | git-send-email(1). 29 | 30 | Posting to sgo-software-discuss 31 | ------------------------------- 32 | 33 | If you're not subscribed to the list, your posting will be held for 34 | moderation; please be patient. 35 | 36 | Whether or not you're subscribed, chiark.greenend.org.uk has 37 | aggressive antispam. If your messages aren't getting through, we can 38 | easily add a bypass on chiark; please contact . 39 | 40 | If you don't want to deal with the mailing list and just want to send 41 | patches, you should feel free to pass ``--to=spwhitton@spwhitton.name`` 42 | to git-send-email(1). 43 | 44 | Alternatively, publish a git branch somewhere publically accessible (a 45 | GitHub fork is fine) and write to me asking me to merge it. I may 46 | convert your branch back into patches when sending you feedback :) 47 | 48 | Reporting bugs 49 | ============== 50 | 51 | Please read "How to Report Bugs Effectively" to ensure your bug report 52 | constitutes a useful contribution to the project: 53 | 54 | 55 | Signing off your commits 56 | ======================== 57 | 58 | Contributions are accepted upstream under the terms set out in the 59 | file ``COPYING``. You must certify the contents of the file 60 | ``DEVELOPER-CERTIFICATE`` for your contribution. To do this, append a 61 | ``Signed-off-by`` line to end of your commit message. An easy way to 62 | add this line is to pass the ``-s`` option to git-commit(1). Here is 63 | an example of a ``Signed-off-by`` line: 64 | 65 | :: 66 | 67 | Signed-off-by: Sean Whitton 68 | -------------------------------------------------------------------------------- /COPYING: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /DEVELOPER-CERTIFICATE: -------------------------------------------------------------------------------- 1 | Developer Certificate of Origin 2 | Version 1.1 3 | 4 | Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 5 | 1 Letterman Drive 6 | Suite D4700 7 | San Francisco, CA, 94129 8 | 9 | Everyone is permitted to copy and distribute verbatim copies of this 10 | license document, but changing it is not allowed. 11 | 12 | 13 | Developer's Certificate of Origin 1.1 14 | 15 | By making a contribution to this project, I certify that: 16 | 17 | (a) The contribution was created in whole or in part by me and I 18 | have the right to submit it under the open source license 19 | indicated in the file; or 20 | 21 | (b) The contribution is based upon previous work that, to the best 22 | of my knowledge, is covered under an appropriate open source 23 | license and I have the right under that license to submit that 24 | work with modifications, whether created in whole or in part 25 | by me, under the same open source license (unless I am 26 | permitted to submit under a different license), as indicated 27 | in the file; or 28 | 29 | (c) The contribution was provided directly to me by some other 30 | person who certified (a), (b) or (c) and I have not modified 31 | it. 32 | 33 | (d) I understand and agree that this project and the contribution 34 | are public and that a record of the contribution (including all 35 | personal information I submit with it, including my sign-off) is 36 | maintained indefinitely and may be redistributed consistent with 37 | this project or the open source license(s) involved. 38 | -------------------------------------------------------------------------------- /README.rst: -------------------------------------------------------------------------------- 1 | ================= 2 | git-remote-gcrypt 3 | ================= 4 | 5 | -------------------------------------- 6 | GNU Privacy Guard-encrypted git remote 7 | -------------------------------------- 8 | 9 | :Manual section: 1 10 | 11 | Description 12 | =========== 13 | 14 | git-remote-gcrypt is a git remote helper to push and pull from 15 | repositories encrypted with GnuPG, using a custom format. This remote 16 | helper handles URIs prefixed with `gcrypt::`. 17 | 18 | Supported backends are `local`, `rsync://` and `sftp://`, where the 19 | repository is stored as a set of files, or instead any `` 20 | where gcrypt will store the same representation in a git repository, 21 | bridged over arbitrary git transport. Prefer `local` or `rsync://` if 22 | you can use one of those; see "Performance" below for discussion. 23 | 24 | There is also an experimental `rclone://` backend for early adoptors 25 | only (you have been warned). 26 | 27 | The aim is to provide confidential, authenticated git storage and 28 | collaboration using typical untrusted file hosts or services. 29 | 30 | Installation 31 | ............ 32 | 33 | * use your GNU/Linux distribution's package manager -- Debian, Ubuntu, 34 | Fedora, Arch and some smaller distros are known to have packages 35 | 36 | * run the supplied ``install.sh`` script on other systems 37 | 38 | Quickstart 39 | .......... 40 | 41 | Create an encrypted remote by pushing to it:: 42 | 43 | git remote add cryptremote gcrypt::rsync://example.com/repo 44 | git push cryptremote master 45 | > gcrypt: Setting up new repository 46 | > gcrypt: Remote ID is :id:7VigUnLVYVtZx8oir34R 47 | > [ more lines .. ] 48 | > To gcrypt::[...] 49 | > * [new branch] master -> master 50 | 51 | Configuration 52 | ============= 53 | 54 | The following ``git-config(1)`` variables are supported: 55 | 56 | ``remote..gcrypt-participants`` 57 | .. 58 | ``gcrypt.participants`` 59 | Space-separated list of GPG key identifiers. The remote is encrypted 60 | to these participants and only signatures from these are accepted. 61 | ``gpg -k`` lists all public keys you know. 62 | 63 | If this option is not set, we encrypt to your default key and accept 64 | any valid signature. This behavior can also be requested explicitly 65 | by setting participants to ``simple``. 66 | 67 | The ``gcrypt-participants`` setting on the remote takes precedence 68 | over the repository variable ``gcrypt.participants``. 69 | 70 | ``remote..gcrypt-publish-participants`` 71 | .. 72 | ``gcrypt.publish-participants`` 73 | By default, the gpg key ids of the participants are obscured by 74 | encrypting using ``gpg -R``. Setting this option to ``true`` disables 75 | that security measure. 76 | 77 | The problem with using ``gpg -R`` is that to decrypt, gpg tries each 78 | available secret key in turn until it finds a usable key. 79 | This can result in unnecessary passphrase prompts. 80 | 81 | ``gcrypt.gpg-args`` 82 | The contents of this setting are passed as arguments to gpg. 83 | E.g. ``--use-agent``. 84 | 85 | ``remote..gcrypt-signingkey`` 86 | .. 87 | ``user.signingkey`` 88 | (The latter from regular git configuration) The key to use for signing. 89 | You should set ``user.signingkey`` if your default signing key is not 90 | part of the participant list. You may use the per-remote version 91 | to sign different remotes using different keys. 92 | 93 | ``remote..gcrypt-rsync-put-flags`` 94 | .. 95 | ``gcrypt.rsync-put-flags`` 96 | Flags to be passed to ``rsync`` when uploading to a remote using the 97 | ``rsync://`` backend. If the flags are set to a specific remote, the 98 | global flags, if also set, will not be applied for that remote. 99 | 100 | ``remote..gcrypt-require-explicit-force-push`` 101 | .. 102 | ``gcrypt.require-explicit-force-push`` 103 | A longstanding bug is that every git push effectively has a ``--force``. 104 | 105 | If this flag is set to ``true``, git-remote-gcrypt will refuse to push, 106 | unless ``--force`` is passed, or refspecs are prefixed with ``+``. 107 | 108 | There is a potential solution here: https://bugs.debian.org/877464#32 109 | 110 | Environment variables 111 | ===================== 112 | 113 | *GCRYPT_FULL_REPACK* 114 | When set (to anything other than the empty string), this environment 115 | variable forces a full repack when pushing. 116 | 117 | Examples 118 | ======== 119 | 120 | How to set up a remote for two participants:: 121 | 122 | git remote add cryptremote gcrypt::rsync://example.com/repo 123 | git config remote.cryptremote.gcrypt-participants "KEY1 KEY2" 124 | git push cryptremote master 125 | 126 | How to use a git backend:: 127 | 128 | # notice that the target git repo must already exist and its 129 | # `next` branch will be overwritten! 130 | git remote add gitcrypt gcrypt::git@example.com:repo#next 131 | git push gitcrypt master 132 | 133 | The URL fragment (``#next`` here) indicates which backend branch is used. 134 | 135 | Notes 136 | ===== 137 | 138 | Collaboration 139 | The encryption of the manifest is updated for each push to match the 140 | participant configuration. Each pushing user must have the public 141 | keys of all collaborators and correct participant config. 142 | 143 | Dependencies 144 | ``rsync``, ``curl`` and ``rclone`` for remotes ``rsync:``, ``sftp:`` and 145 | ``rclone:`` respectively. The main executable requires a POSIX-compliant 146 | shell that supports ``local``. 147 | 148 | GNU Privacy Guard 149 | Both GPG 1.4 and 2 are supported. You need a personal GPG key. GPG 150 | configuration applies to algorithm choices for public-key 151 | encryption, symmetric encryption, and signing. See ``man gpg`` for 152 | more information. 153 | 154 | Remote ID 155 | The Remote ID is not secret; it only ensures that two repositories 156 | signed by the same user can be distinguished. You will see 157 | a warning if the Remote ID changes, which should only happen if the 158 | remote was re-created. 159 | 160 | Performance 161 | Using an arbitrary `` or an `sftp://` URI requires 162 | uploading the entire repository history with each push. This 163 | means that pushes of your repository become slower over time, as 164 | your git history becomes longer, and it can easily get to the 165 | point that continued usage of git-remote-gcrypt is impractical. 166 | 167 | Thus, you should use these backends only when you know that your 168 | repository will not ever grow very large, not just that it's not 169 | large now. This means that these backends are inappropriate for 170 | most repositories, and likely suitable only for unusual cases, 171 | such as small credential stores. Even then, use `rsync://` if you 172 | can. Note, however, that `rsync://` won't work with a repository 173 | hosting service like Gitolite, GitHub or GitLab. 174 | 175 | rsync URIs 176 | The URI format for the rsync backend is ``rsync://user@host/path``, 177 | which translates to the rsync location ``user@host:/path``, 178 | accessed over ssh. Note that the path is absolute, not relative to the 179 | home directory. An earlier non-standard URI format is also supported: 180 | ``rsync://user@host:path``, which translates to the rsync location 181 | ``user@host:path`` 182 | 183 | rclone backend 184 | In addition to adding the rclone backend as a remote with URI like 185 | ``gcrypt::rclone://remote:subdir``, you must add the remote to the 186 | rclone configuration too. This is typically done by executing 187 | ``rclone config``. See rclone(1). 188 | 189 | The rclone backend is considered experimental and is for early 190 | adoptors only. You have been warned. 191 | 192 | Repository format 193 | ................. 194 | 195 | | `EncSign(X):` Sign and Encrypt to GPG key holder 196 | | `Encrypt(K,X):` Encrypt using symmetric-key algorithm 197 | | `Hash(X):` SHA-2/256 198 | | 199 | | `B:` branch list 200 | | `L:` list of the hash (`Hi`) and key (`Ki`) for each packfile 201 | | `R:` Remote ID 202 | | 203 | | To write the repository: 204 | | 205 | | Store each packfile `P` as `Encrypt(Ki, P)` → `P'` in filename `Hi` 206 | | where `Ki` is a new random string and `Hash(P')` → `Hi` 207 | | Store `EncSign(B || L || R)` in the manifest 208 | | 209 | | To read the repository: 210 | | 211 | | Get manifest, decrypt and verify using GPG keyring → `(B, L, R)` 212 | | Warn if `R` does not match previously seen Remote ID 213 | | for each `Hi, Ki` in `L`: 214 | | Get file `Hi` from the server → `P'` 215 | | Verify `Hash(P')` matches `Hi` 216 | | Decrypt `P'` using `Ki` → `P` then open `P` with git 217 | 218 | Manifest file 219 | ............. 220 | 221 | Example manifest file (with ellipsis for brevity):: 222 | 223 | $ gpg -d 91bd0c092128cf2e60e1a608c31e92caf1f9c1595f83f2890ef17c0e4881aa0a 224 | 542051c7cd152644e4995bda63cc3ddffd635958 refs/heads/next 225 | 3c9e76484c7596eff70b21cbe58408b2774bedad refs/heads/master 226 | pack :SHA256:f2ad50316...cd4ba67092dc4 z8YoAnFpMlW...3PkI2mND49P1qm 227 | pack :SHA256:a6e17bb4c...426492f379584 82+k2cbiUn7...dgXfyX6wXGpvVa 228 | keep :SHA256:f2ad50316...cd4ba67092dc4 1 229 | repo :id:OYiSleGirtLubEVqJpFF 230 | 231 | Each item extends until newline, and matches one of the following: 232 | 233 | `` `` 234 | Git object id and its ref 235 | 236 | ``pack :: `` 237 | Packfile hash (`Hi`) and corresponding symmetric key (`Ki`). 238 | 239 | ``keep :: `` 240 | Packfile hash and its repack generation 241 | 242 | ``repo `` 243 | The remote id 244 | 245 | ``extn ...`` 246 | Extension field, preserved but unused. 247 | 248 | Detecting gcrypt repos 249 | ====================== 250 | 251 | To detect if a git url is a gcrypt repo, use: ``git-remote-gcrypt --check url`` 252 | Exit status is 0 if the repo exists and can be decrypted, 1 if the repo 253 | uses gcrypt but could not be decrypted, and 100 if the repo is not 254 | encrypted with gcrypt (or could not be accessed). 255 | 256 | Note that this has to fetch the repo contents into the local git 257 | repository, the same as is done when using a gcrypt repo. 258 | 259 | Known issues 260 | ============ 261 | 262 | Every git push effectively has ``--force``. Be sure to pull before 263 | pushing. 264 | 265 | git-remote-gcrypt can decide to repack the remote without warning, 266 | which means that your push can suddenly take significantly longer than 267 | you were expecting, as your whole history has to be reuploaded. 268 | This push might fail over a poor link. 269 | 270 | git-remote-gcrypt might report a repository as "not found" when the 271 | repository does in fact exist, but git-remote-gcrypt is having 272 | authentication, port, or network connectivity issues. 273 | 274 | See also 275 | ======== 276 | 277 | git-remote-helpers(1), gpg(1) 278 | 279 | Credits 280 | ======= 281 | 282 | The original author of git-remote-gcrypt was GitHub user bluss. 283 | 284 | The de facto maintainer in 2013 and 2014 was Joey Hess. 285 | 286 | The current maintainer, since 2016, is Sean Whitton 287 | . 288 | 289 | License 290 | ======= 291 | 292 | This document and git-remote-gcrypt are licensed under identical terms, 293 | GPL-3 (or 2+); see the git-remote-gcrypt file. 294 | 295 | .. this document generates a man page with rst2man 296 | .. vim: ft=rst tw=72 sts=4 297 | -------------------------------------------------------------------------------- /debian/changelog: -------------------------------------------------------------------------------- 1 | git-remote-gcrypt (1.6-1) UNRELEASED; urgency=medium 2 | 3 | * New integration test for gitception, tests/system-test.sh. 4 | Thanks to Cathy J. Fitzpatrick for the script. 5 | * README: Add a link regarding fixing the longstanding force push issue. 6 | Thanks to Joey Hess for writing up the proposal. 7 | * README: Clarify description of GCRYPT_FULL_REPACK. 8 | The variable must be set to a non-empty string to have an effect. 9 | Thanks to Cathy J. Fitzpatrick for the patch. 10 | 11 | -- Sean Whitton Sun, 29 Dec 2024 09:37:05 +0000 12 | 13 | git-remote-gcrypt (1.5-1) unstable; urgency=medium 14 | 15 | * Pass --error-on-no-transfer to 'rclone copyto'. 16 | Thanks to Nathan Todd-Stone for the patch. 17 | * README.md: 18 | - explain why the arbitrary and sftp:// backends are 19 | inappropriate for most git repositories 20 | - use stronger language to say that one should use local or rsync:// 21 | instead, and also say it up in "Description". 22 | 23 | -- Sean Whitton Sun, 21 Aug 2022 14:38:58 -0700 24 | 25 | git-remote-gcrypt (1.4-1) unstable; urgency=medium 26 | 27 | Upstream: 28 | * Add gcrypt.require-explicit-force-push configuration key. 29 | Thanks to Jay Colson for the idea and a patch. 30 | * Support rsync URIs like "rsync://user@host/path" (Closes: #980397). 31 | Thanks to Joey Hess for the patch. 32 | * CONTRIBUTING.rst: 33 | - Add mailing list information. 34 | - Add link to "How to Report Bugs Effectively". 35 | * PULL_REQUEST_TEMPLATE.md: replace patch submission instructions with 36 | reference to CONTRIBUTING.md. 37 | 38 | -- Sean Whitton Thu, 21 Jan 2021 18:46:38 -0700 39 | 40 | git-remote-gcrypt (1.3-1) unstable; urgency=medium 41 | 42 | Upstream: 43 | * README.md: Clarify how to use GCRYPT_FULL_REPACK. 44 | Thanks Félix Sipma for the patch. 45 | * Updates to redhat/git-remote-gcrypt.spec. 46 | Thanks Frank Grüllich and Dusty Mabe for patches. 47 | * install.sh: try rst2man.py if rst2man binary not available. 48 | Thanks Dmitry Zhlobo for the patch. 49 | * Add git-config option to set rsync put flags. 50 | Thanks Travis Chen for the patch. 51 | 52 | Debian packaging: 53 | * Switch build-dep python-docutils -> python3-docutils (Closes: #943099). 54 | 55 | -- Sean Whitton Sat, 08 Feb 2020 23:01:15 -0700 56 | 57 | git-remote-gcrypt (1.2-1) unstable; urgency=low 58 | 59 | Upstream: 60 | * When the repository cannot be found, but the repo ID is set, output the 61 | stderr of other commands to help the user figure out what's wrong 62 | (Closes: #914059). 63 | * Note that git-remote-gcrypt's "not found" error can be misleading. 64 | Thanks Ulrike Uhlig for the patch. 65 | 66 | -- Sean Whitton Mon, 26 Nov 2018 22:08:19 -0700 67 | 68 | git-remote-gcrypt (1.1-1) unstable; urgency=medium 69 | 70 | Upstream: 71 | * Add CONTRIBUTING.md and DEVELOPER-CERTIFICATE. 72 | * Add experimental rclone backend (for early adoptors only). 73 | Thanks Beren Minor for the patch. 74 | 75 | Debian packaging: 76 | * Suggest rclone. 77 | 78 | -- Sean Whitton Sat, 28 Apr 2018 13:32:48 -0700 79 | 80 | git-remote-gcrypt (1.0.3-1) unstable; urgency=medium 81 | 82 | * Don't pass '-m 700' to mkdir under Windows, which fails. 83 | Thanks to Steven R. Loomis for the patch. 84 | * Add redhat/git-remote-gcrypt.spec 85 | Thanks, Frank Grüllich. 86 | * Add note about non-standard rsync:// URI format. 87 | Thanks Jane Soko for pointing this out. 88 | * Improve first section of manpage. 89 | * Add "Known issues". 90 | 91 | -- Sean Whitton Fri, 09 Mar 2018 11:18:04 -0700 92 | 93 | git-remote-gcrypt (1.0.2-1) unstable; urgency=medium 94 | 95 | Bug fixes: 96 | * Correctly handle the case where gcrypt.gpg-args contains more than one 97 | argument, separated by spaces. 98 | Thanks Etienne Brodu for the patch. 99 | 100 | Documentation: 101 | * Drop section "Note to users of GnuPG version 2". 102 | The issue was a regression in GnuPG 2.x, fixed in version 2.1.16. 103 | * Add a note about performance when not using the rsync:// or local backends. 104 | * Add section containing author and maintainer information. 105 | * Add `apt-get` installation instructions, for the benefit of GitHub users. 106 | * Other minor edits and formatting changes. 107 | 108 | Debian packaging: 109 | * Replace quilt patch with code in d/rules to remove installation 110 | instructions from the manpage. 111 | * Depend on gpg | gnupg1 and demote gnupg to a Recommends (Closes: #873498). 112 | At least with passwordless PGP keys, git-remote-gcrypt works fine with 113 | only the gpg package installed. 114 | Thanks to Yuri D'Elia for the report. 115 | * Bump copyright years. 116 | * Bump standards version to 4.1.0 (no changes required). 117 | 118 | -- Sean Whitton Fri, 01 Sep 2017 14:34:35 -0700 119 | 120 | git-remote-gcrypt (1.0.1-1) unstable; urgency=low 121 | 122 | Upstream: 123 | * Add authorship details to script header. 124 | 125 | Debian packaging: 126 | * Update Homepage: to point to my website. 127 | * Bump debhelper build-dep & compat to 10. 128 | * Use shorter URI in Vcs-Browser. 129 | 130 | -- Sean Whitton Tue, 10 Jan 2017 20:17:08 -0700 131 | 132 | git-remote-gcrypt (1.0.0-1) unstable; urgency=medium 133 | 134 | Upstream: 135 | * Taking over as upstream maintainer. 136 | * Remove notice about repository format potentially changing. 137 | * Implement gcrypt.gpg-args git config setting (Closes: #771011). 138 | * Respect git config gpg.program if configured. 139 | Thanks Christian Amsüss. (Closes: #827943) 140 | * Don't reset the remote ID when a gcrypt remote is not available. 141 | Thanks Sebastian Reuße. (Closes: #827943) 142 | * Suppress bogus warning about keyid matching multiple fingerprints. 143 | Based on work by Raphaël Droz. 144 | Closes https://github.com/joeyh/git-remote-gcrypt/pull/2 145 | * Add "Note to users of GnuPG version 2" section to README.rst. 146 | See https://github.com/joeyh/git-remote-gcrypt/pull/1 147 | 148 | Debian packaging: 149 | * Drop patch containing changes by Joey Hess: incorporated in release. 150 | - Update d/copyright accordingly. 151 | * Patch README.rst to remove references to installation. 152 | * Add d/links to avoid duplicate changelogs Lintian warning. 153 | * Drop Lintian override of no-upstream-changelog. 154 | * Update URIs in old changelog entries. 155 | * Add a comment to d/source/lintian-overrides. 156 | * Bump standards version to 3.9.8 (no changes required). 157 | 158 | -- Sean Whitton Mon, 04 Jul 2016 19:18:48 +0900 159 | 160 | git-remote-gcrypt (0.20130908-8) unstable; urgency=medium 161 | 162 | * Adopt git-remote-gcrypt package (Closes: #771020). 163 | * Install man page using rst2man, rather than just installing README.rst 164 | (Closes: #725455). 165 | * Add Vcs-Git: & Vcs-Browser: pointing at my repository. 166 | * Switch dpkg-source format to 3.0 (quilt). 167 | * Move changes by Joey Hess into a quilt patch. 168 | Update debian/copyright accordingly. 169 | * Bump Standards-Version. 170 | * Add debian/gbp.conf. 171 | * Override Lintian tags no-upstream-changelog & debian-watch-file-is-missing. 172 | 173 | -- Sean Whitton Thu, 07 Jan 2016 11:03:01 -0700 174 | 175 | git-remote-gcrypt (0.20130908-7) unstable; urgency=medium 176 | 177 | * Added gcrypt.publish-participants configuration setting. 178 | 179 | -- Joey Hess Tue, 15 Jul 2014 17:40:22 -0400 180 | 181 | git-remote-gcrypt (0.20130908-6) unstable; urgency=medium 182 | 183 | * Fix to work when there is no controlling terminal, but GPG_AGENT_INFO 184 | is set. Pass --no-tty to gpg in this situation. This is needed 185 | to interoperate with the git-annex assistant, which often runs without 186 | a controlling terminal, and will in a new version always do so. 187 | 188 | -- Joey Hess Thu, 15 May 2014 14:35:03 -0400 189 | 190 | git-remote-gcrypt (0.20130908-5) unstable; urgency=low 191 | 192 | * Better signature validation for subkeys. 193 | Closes https://github.com/bluss/git-remote-gcrypt/pull/7 194 | * Stop passing --fast-list to gpg as this sometimes causes it to not 195 | display key fingerprints, which git-remote-gcrpyt needs. 196 | Closes https://github.com/bluss/git-remote-gcrypt/issues/8 197 | 198 | -- Joey Hess Thu, 26 Sep 2013 15:58:52 -0400 199 | 200 | git-remote-gcrypt (0.20130908-4) unstable; urgency=low 201 | 202 | * Added --check option. 203 | 204 | -- Joey Hess Thu, 19 Sep 2013 12:10:24 -0400 205 | 206 | git-remote-gcrypt (0.20130908-3) unstable; urgency=low 207 | 208 | * Add remote..gcrypt-signingkey config. 209 | 210 | -- Joey Hess Tue, 17 Sep 2013 15:33:35 -0400 211 | 212 | git-remote-gcrypt (0.20130908-2) unstable; urgency=low 213 | 214 | * Set --trust-model=always when encrypting. 215 | Needed to interoperate with git-annex. 216 | Closes https://github.com/bluss/git-remote-gcrypt/issues/3 217 | 218 | -- Joey Hess Mon, 16 Sep 2013 15:49:16 -0400 219 | 220 | git-remote-gcrypt (0.20130908-1) unstable; urgency=low 221 | 222 | * Initial release. 223 | 224 | -- Joey Hess Sun, 08 Sep 2013 20:08:23 -0400 225 | -------------------------------------------------------------------------------- /debian/compat: -------------------------------------------------------------------------------- 1 | 10 2 | -------------------------------------------------------------------------------- /debian/control: -------------------------------------------------------------------------------- 1 | Source: git-remote-gcrypt 2 | Section: vcs 3 | Priority: optional 4 | Build-Depends: debhelper (>= 10), python3-docutils (>= 0.12+dfsg) 5 | Maintainer: Sean Whitton 6 | Standards-Version: 4.1.0 7 | Homepage: https://spwhitton.name/tech/code/git-remote-gcrypt/ 8 | Vcs-Git: https://git.spwhitton.name/git-remote-gcrypt 9 | Vcs-Browser: https://git.spwhitton.name/git-remote-gcrypt 10 | 11 | Package: git-remote-gcrypt 12 | Architecture: all 13 | Depends: git, gpg | gnupg1, ${misc:Depends} 14 | Recommends: rsync, curl, gnupg 15 | Suggests: rclone 16 | Description: encrypted git repositories 17 | This lets git store git repositories in encrypted form. 18 | It supports storing repositories on rsync or sftp servers. 19 | It can also store the encrypted git repository inside a remote git 20 | repository. All the regular git commands like git push and git pull 21 | can be used to operate on such an encrypted repository. 22 | . 23 | The aim is to provide confidential, authenticated git storage and 24 | collaboration using typical untrusted file hosts or services. 25 | -------------------------------------------------------------------------------- /debian/copyright: -------------------------------------------------------------------------------- 1 | Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ 2 | Source: https://git.spwhitton.name/git-remote-gcrypt 3 | 4 | Files: * 5 | Copyright: (C) 2013 engla 6 | (C) 2013, 2014, 2021 Joey Hess 7 | (C) 2016-2022 Sean Whitton and contributors 8 | (C) 2023 Cathy J. Fitzpatrick 9 | License: GPL-2+ 10 | 11 | Files: debian/* 12 | Copyright: (C) 2015-2017 Sean Whitton 13 | (C) 2013, 2014 Joey Hess 14 | License: GPL-2+ 15 | 16 | License: GPL-2+ 17 | On Debian systems, the complete text of the GPL-2 can be found in 18 | /usr/share/common-licenses/GPL-2. 19 | -------------------------------------------------------------------------------- /debian/gbp.conf: -------------------------------------------------------------------------------- 1 | [DEFAULT] 2 | 3 | # Debian package maintainer is upstream project maintainer, so 4 | # everything lives on the master branch (from ver. 1.0.0-1 onwards) 5 | upstream-branch = master 6 | debian-branch = master 7 | # However, separate tags (e.g. one commit tagged both 1.0.0 and 8 | # debian/1.0.0-1) because git-remote-gcrypt is meant to be usable 9 | # outside of Debian 10 | upstream-tag = %(version)s 11 | debian-tag = debian/%(version)s 12 | 13 | # Some standard gbp settings 14 | sign-tags = True 15 | pristine-tar = True 16 | pristine-tar-commit = True 17 | 18 | color = on 19 | compression = xz 20 | compression-level = 9 21 | -------------------------------------------------------------------------------- /debian/links: -------------------------------------------------------------------------------- 1 | /usr/share/doc/git-remote-gcrypt/changelog /usr/share/doc/git-remote-gcrypt/changelog.Debian 2 | -------------------------------------------------------------------------------- /debian/rules: -------------------------------------------------------------------------------- 1 | #!/usr/bin/make -f 2 | 3 | manpage = debian/git-remote-gcrypt/usr/share/man/man1/git-remote-gcrypt.1 4 | 5 | %: 6 | dh $@ 7 | 8 | override_dh_auto_build: 9 | true 10 | override_dh_auto_clean: 11 | true 12 | 13 | override_dh_auto_install: 14 | prefix=/usr DESTDIR=debian/git-remote-gcrypt ./install.sh 15 | # remove installation instructions from manpage (this is 16 | # essentially an automatically-refreshing quilt patch) 17 | gunzip ${manpage}.gz 18 | sed -i ${manpage} -e \ 19 | '/^.SS Installation$$/,/^.SS/{ /^.SS Installation$$/d; /^.SS/!d }' 20 | gzip -n ${manpage} 21 | -------------------------------------------------------------------------------- /debian/source/format: -------------------------------------------------------------------------------- 1 | 3.0 (quilt) 2 | -------------------------------------------------------------------------------- /debian/source/lintian-overrides: -------------------------------------------------------------------------------- 1 | # upstream maintainer is Debian maintainer 2 | debian-watch-file-is-missing 3 | -------------------------------------------------------------------------------- /git-remote-gcrypt: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | # git-remote-gcrypt 4 | # 5 | # Copyright (c) 2013 engla 6 | # Copyright (c) 2013, 2014 Joey Hess 7 | # Copyright (c) 2016, 2018 Sean Whitton and contributors 8 | # 9 | # This program is free software: you can redistribute it and/or modify 10 | # it under the terms of the GNU General Public License as published by 11 | # the Free Software Foundation, either version 3 of the License, or 12 | # (at your option) version 2 or any later version. 13 | # 14 | # This program is distributed in the hope that it will be useful, 15 | # but WITHOUT ANY WARRANTY; without even the implied warranty of 16 | # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 17 | # GNU General Public License for more details. 18 | # 19 | # You should have received a copy of the GNU General Public License 20 | # along with this program. If not, see . 21 | # 22 | # See README.rst for usage instructions 23 | 24 | set -e # errexit 25 | set -f # noglob 26 | set -C # noclobber 27 | 28 | export GITCEPTION="${GITCEPTION:-}+" # Reuse $Gref except when stacked 29 | Gref="refs/gcrypt/gitception$GITCEPTION" 30 | Gref_rbranch="refs/heads/master" 31 | Packkey_bytes=63 # nbr random bytes for packfile keys, any >= 256 bit is ok 32 | Hashtype=SHA256 # SHA512 SHA384 SHA256 SHA224 supported. 33 | Manifestfile=91bd0c092128cf2e60e1a608c31e92caf1f9c1595f83f2890ef17c0e4881aa0a 34 | Hex40="[a-f0-9]" 35 | Hex40=$Hex40$Hex40$Hex40$Hex40$Hex40$Hex40$Hex40$Hex40 36 | Hex40=$Hex40$Hex40$Hex40$Hex40$Hex40 # Match SHA-1 hexdigest 37 | GPG="$(git config --get "gpg.program" '.+' || echo gpg)" 38 | 39 | Did_find_repo= # yes for connected, no for no repo 40 | Localdir="${GIT_DIR:=.git}/remote-gcrypt" 41 | Tempdir= 42 | 43 | Repoid= 44 | Refslist= 45 | Packlist= 46 | Keeplist= 47 | Extnlist= 48 | Repack_limit=25 49 | 50 | Recipients= 51 | 52 | # compat/utility functions 53 | # xfeed: The most basic output function puts $1 into the stdin of $2..$# 54 | xfeed() 55 | { 56 | local input_= 57 | input_=$1; shift 58 | "$@" <&2; } 66 | echo_die() { echo_info "$@" ; exit 1; } 67 | 68 | isnull() { case "$1" in "") return 0;; *) return 1;; esac; } 69 | isnonnull() { ! isnull "$1"; } 70 | iseq() { case "$1" in "$2") return 0;; *) return 1;; esac; } 71 | isnoteq() { ! iseq "$1" "$2"; } 72 | negate() { ! "$@"; } 73 | 74 | # Execute $@ or die 75 | pipefail() 76 | { 77 | "$@" || { echo_info "'$1' failed!"; kill $$; exit 1; } 78 | } 79 | 80 | isurl() { isnull "${2%%$1://*}"; } 81 | islocalrepo() { isnull "${1##/*}" && [ ! -e "$1/HEAD" ]; } 82 | 83 | xgrep() { command grep "$@" || : ; } 84 | 85 | # setvar is used for named return variables 86 | # $1 *must* be a valid variable name, $2 is any value 87 | # 88 | # Conventions 89 | # return variable names are passed with a @ prefix 90 | # return variable functions use f_ prefix local vars 91 | # return var consumers use r_ prefix vars (or Titlecase globals) 92 | setvar() 93 | { 94 | isnull "${1##@*}" || echo_die "Missing @ for return variable: $1" 95 | eval ${1#@}=\$2 96 | } 97 | 98 | Newline=" 99 | " 100 | 101 | # $1 is return var, $2 is value appended with newline separator 102 | append_to() 103 | { 104 | local f_append_tmp_= 105 | eval f_append_tmp_=\$${1#@} 106 | isnull "$f_append_tmp_" || f_append_tmp_=$f_append_tmp_$Newline 107 | setvar "$1" "$f_append_tmp_$2" 108 | } 109 | 110 | # Pick words from each line 111 | # $1 return variable name 112 | # $2 input value 113 | pick_fields_1_2() 114 | { 115 | local f_ret= f_one= f_two= 116 | while read f_one f_two _ # from << here-document 117 | do 118 | f_ret="$f_ret$f_one $f_two$Newline" 119 | done </dev/null && 167 | obj_id="$(git ls-tree "$Gref" | xgrep -E '\b'"$2"'$' | awk '{print $3}')" && 168 | isnonnull "$obj_id" && git cat-file blob "$obj_id" && ret_=: || 169 | { ret_=false && : ; } 170 | [ -e "$fet_head.$$~" ] && command mv -f "$fet_head.$$~" "$fet_head" || : 171 | $ret_ 172 | } 173 | 174 | anon_commit() 175 | { 176 | GIT_AUTHOR_NAME="root" GIT_AUTHOR_EMAIL="root@localhost" \ 177 | GIT_AUTHOR_DATE="1356994801 -0400" GIT_COMMITTER_NAME="root" \ 178 | GIT_COMMITTER_EMAIL="root@localhost" \ 179 | GIT_COMMITTER_DATE="1356994801 -0400" \ 180 | git commit-tree "$@" </dev/null >&2 || : 224 | git rev-parse -q --verify "$Gref" >/dev/null && return 0 || 225 | commit_id=$(anon_commit "$empty_tree") && 226 | git update-ref "$Gref" "$commit_id" 227 | } 228 | ## end gitception 229 | 230 | # Fetch repo $1, file $2, tmpfile in $3 231 | GET() 232 | { 233 | if isurl sftp "$1" 234 | then 235 | (exec 0>&-; curl -s -S -k "$1/$2") > "$3" 236 | elif isurl rsync "$1" 237 | then 238 | (exec 0>&-; rsync -I -W "$(rsynclocation "$1")"/"$2" "$3" >&2) 239 | elif isurl rclone "$1" 240 | then 241 | (exec 0>&-; rclone copyto --error-on-no-transfer "${1#rclone://}"/"$2" "$3" >&2) 242 | elif islocalrepo "$1" 243 | then 244 | cat "$1/$2" > "$3" 245 | else 246 | gitception_get "${1#gitception://}" "$2" > "$3" 247 | fi 248 | } 249 | 250 | # Put repo $1, file $2 or fail, tmpfile in $3 251 | PUT() 252 | { 253 | if isurl sftp "$1" 254 | then 255 | curl -s -S -k --ftp-create-dirs -T "$3" "$1/$2" 256 | elif isurl rsync "$1" 257 | then 258 | rsync $Conf_rsync_put_flags -I -W "$3" "$(rsynclocation "$1")"/"$2" >&2 259 | elif isurl rclone "$1" 260 | then 261 | rclone copyto --error-on-no-transfer "$3" "${1#rclone://}"/"$2" >&2 262 | elif islocalrepo "$1" 263 | then 264 | cat >| "$1/$2" < "$3" 265 | else 266 | gitception_put "${1#gitception://}" "$2" < "$3" 267 | fi 268 | } 269 | 270 | # Put all PUT changes for repo $1 at once 271 | PUT_FINAL() 272 | { 273 | if isurl sftp "$1" || islocalrepo "$1" || isurl rsync "$1" || isurl rclone "$1" 274 | then 275 | : 276 | else 277 | git push --quiet -f "${1#gitception://}" "$Gref:$Gref_rbranch" 278 | fi 279 | } 280 | 281 | # Put directory for repo $1 282 | PUTREPO() 283 | { 284 | if isurl sftp "$1" 285 | then 286 | : 287 | elif isurl rsync "$1" 288 | then 289 | rsync $Conf_rsync_put_flags -q -r --exclude='*' \ 290 | "$Localdir/" "$(rsynclocation "$1")" >&2 291 | elif isurl rclone "$1" 292 | then 293 | rclone mkdir "${1#rclone://}" >&2 294 | elif islocalrepo "$1" 295 | then 296 | mkdir -p "$1" 297 | else 298 | gitception_new_repo "${1#gitception://}" 299 | fi 300 | } 301 | 302 | # For repo $1, delete all newline-separated files in $2 303 | REMOVE() 304 | { 305 | local fn_= 306 | if isurl sftp "$1" 307 | then 308 | # FIXME 309 | echo_info "sftp: Ignore remove request $1/$2" 310 | elif isurl rsync "$1" 311 | then 312 | xfeed "$2" rsync -I -W -v -r --delete --include-from=- \ 313 | --exclude='*' "$Localdir"/ "$(rsynclocation "$1")/" >&2 314 | elif isurl rclone "$1" 315 | then 316 | xfeed "$2" rclone delete -v --include-from=/dev/stdin "${1#rclone://}/" >&2 317 | elif islocalrepo "$1" 318 | then 319 | for fn_ in $2; do 320 | rm -f "$1"/"$fn_" 321 | done 322 | else 323 | for fn_ in $2; do 324 | gitception_remove "${1#gitception://}" "$fn_" 325 | done 326 | fi 327 | } 328 | 329 | CLEAN_FINAL() 330 | { 331 | if isurl sftp "$1" || islocalrepo "$1" || isurl rsync "$1" || isurl rclone "$1" 332 | then 333 | : 334 | else 335 | git update-ref -d "$Gref" || : 336 | fi 337 | } 338 | 339 | ENCRYPT() 340 | { 341 | rungpg --batch --force-mdc --compress-algo none --trust-model=always --passphrase-fd 3 -c 3<&1 && 369 | status_=$(rungpg --status-fd 3 -q -d 3>&1 1>&4) && 370 | xfeed "$status_" grep "^\[GNUPG:\] ENC_TO " >/dev/null && 371 | (xfeed "$status_" grep -e "$1" >/dev/null || { 372 | echo_info "Failed to verify manifest signature!" && 373 | echo_info "Only accepting signatories: ${2:-(none)}" && 374 | return 1 375 | }) 376 | } 377 | 378 | # Generate $1 random bytes 379 | genkey() 380 | { 381 | rungpg --armor --gen-rand 1 "$1" 382 | } 383 | 384 | gpg_hash() 385 | { 386 | local hash_= 387 | hash_=$(rungpg --with-colons --print-md "$1" | tr A-F a-f) 388 | hash_=${hash_#:*:} 389 | xecho "${hash_%:}" 390 | } 391 | 392 | rungpg() 393 | { 394 | if isnonnull "$Conf_gpg_args"; then 395 | set -- "$Conf_gpg_args" "$@" 396 | fi 397 | # gpg will fail to run when there is no controlling tty, 398 | # due to trying to print messages to it, even if a gpg agent is set 399 | # up. --no-tty fixes this. 400 | if [ "x$GPG_AGENT_INFO" != "x" ]; then 401 | ${GPG} --no-tty $@ 402 | else 403 | ${GPG} $@ 404 | fi 405 | } 406 | 407 | # Pass the branch/ref by pipe to git 408 | safe_git_rev_parse() 409 | { 410 | git cat-file --batch-check 2>/dev/null | 411 | xgrep -v "missing" | cut -f 1 -d ' ' 412 | } 413 | 414 | make_new_repo() 415 | { 416 | echo_info "Setting up new repository" 417 | PUTREPO "$URL" 418 | 419 | # Needed assumption: the same user should have no duplicate Repoid 420 | Repoid=":id:$(genkey 15)" 421 | iseq "${NAME#gcrypt::}" "$URL" || 422 | git config "remote.$NAME.gcrypt-id" "$Repoid" 423 | echo_info "Remote ID is $Repoid" 424 | Extnlist="extn comment" 425 | } 426 | 427 | 428 | # $1 return var for goodsig match, $2 return var for signers text 429 | read_config() 430 | { 431 | local recp_= r_tail= r_keyinfo= r_keyfpr= gpg_list= cap_= conf_part= good_sig= signers_= 432 | Conf_signkey=$(git config --get "remote.$NAME.gcrypt-signingkey" '.+' || 433 | git config --path user.signingkey || :) 434 | conf_part=$(git config --get "remote.$NAME.gcrypt-participants" '.+' || 435 | git config --get gcrypt.participants '.+' || :) 436 | Conf_pubish_participants=$(git config --get --bool "remote.$NAME.gcrypt-publish-participants" '.+' || 437 | git config --get --bool gcrypt.publish-participants || :) 438 | Conf_gpg_args=$(git config --get gcrypt.gpg-args '.+' || :) 439 | Conf_rsync_put_flags=$(git config --get "remote.$NAME.gcrypt-rsync-put-flags" '.+' || 440 | git config --get "gcrypt.rsync-put-flags" '.+' || :) 441 | Conf_force_required=$(git config --get --bool "remote.$NAME.gcrypt-require-explicit-force-push" '.+' || 442 | git config --get --bool gcrypt.require-explicit-force-push '.+' || :) 443 | 444 | # Figure out which keys we should encrypt to or accept signatures from 445 | if isnull "$conf_part" || iseq "$conf_part" simple 446 | then 447 | signers_="(default keyring)" 448 | Recipients="--throw-keyids --default-recipient-self" 449 | good_sig="^\[GNUPG:\] GOODSIG " 450 | setvar "$1" "$good_sig" 451 | setvar "$2" "$signers_" 452 | return 0 453 | fi 454 | 455 | for recp_ in $conf_part 456 | do 457 | gpg_list=$(rungpg --with-colons --fingerprint -k "$recp_") 458 | r_tail_=$(echo "$recp_" | sed -e 's/^0x//') 459 | filter_to @r_keyinfo "pub*" "$gpg_list" 460 | if echo "$recp_" | grep -E -q '^[xA-F0-9]+$'; then # is $recp_ a keyid? 461 | filter_to @r_keyfpr "fpr*$r_tail_*" "$gpg_list" 462 | else 463 | filter_to @r_keyfpr "fpr*" "$gpg_list" 464 | fi 465 | isnull "$r_keyinfo" || isnonnull "${r_keyinfo##*"$Newline"*}" || 466 | echo_info "WARNING: '$recp_' matches multiple keys, using one" 467 | isnull "$r_keyfpr" || isnonnull "${r_keyfpr##*"$Newline"*}" || 468 | echo_info "WARNING: '$recp_' matches multiple fingerprints, using one" 469 | r_keyinfo=${r_keyinfo%%"$Newline"*} 470 | r_keyfpr=${r_keyfpr%%"$Newline"*} 471 | keyid_=$(xfeed "$r_keyinfo" cut -f 5 -d :) 472 | fprid_=$(xfeed "$r_keyfpr" cut -f 10 -d :) 473 | 474 | isnonnull "$fprid_" && 475 | signers_="$signers_ $keyid_" && 476 | append_to @good_sig "^\[GNUPG:\] VALIDSIG .*$fprid_$" || { 477 | echo_info "WARNING: Skipping missing key $recp_" 478 | continue 479 | } 480 | # Check 'E'ncrypt capability 481 | cap_=$(xfeed "$r_keyinfo" cut -f 12 -d :) 482 | if ! iseq "${cap_#*E}" "$cap_"; then 483 | if [ "$Conf_pubish_participants" = true ]; then 484 | Recipients="$Recipients -r $keyid_" 485 | else 486 | Recipients="$Recipients -R $keyid_" 487 | fi 488 | fi 489 | done 490 | 491 | if isnull "$Recipients" 492 | then 493 | echo_info "You have not configured any keys you can encrypt to" \ 494 | "for this repository" 495 | echo_info "Use ::" 496 | echo_info " git config gcrypt.participants YOURKEYID" 497 | exit 1 498 | fi 499 | setvar "$1" "$good_sig" 500 | setvar "$2" "$signers_" 501 | } 502 | 503 | ensure_connected() 504 | { 505 | local manifest_= r_repoid= r_name= url_frag= r_sigmatch= r_signers= \ 506 | tmp_manifest= tmp_stderr= 507 | 508 | if isnonnull "$Did_find_repo" 509 | then 510 | return 511 | fi 512 | Did_find_repo=no 513 | read_config @r_sigmatch @r_signers 514 | 515 | iseq "${NAME#gcrypt::}" "$URL" || r_name=$NAME 516 | 517 | if isurl gitception "$URL" && isnonnull "$r_name"; then 518 | git config "remote.$r_name.url" "gcrypt::${URL#gitception://}" 519 | echo_info "Updated URL for $r_name, gitception:// -> ()" 520 | fi 521 | 522 | # Find the URL fragment 523 | url_frag=${URL##*"#"} 524 | isnoteq "$url_frag" "$URL" || url_frag= 525 | URL=${URL%"#$url_frag"} 526 | 527 | # manifestfile -- sha224 hash if we can, else the default location 528 | if isurl sftp "$URL" || islocalrepo "$URL" || isurl rsync "$URL" || isurl rclone "$URL" 529 | then 530 | # not for gitception 531 | isnull "$url_frag" || 532 | Manifestfile=$(xecho_n "$url_frag" | gpg_hash SHA224) 533 | else 534 | isnull "$url_frag" || Gref_rbranch="refs/heads/$url_frag" 535 | fi 536 | 537 | Repoid= 538 | isnull "$r_name" || 539 | Repoid=$(git config "remote.$r_name.gcrypt-id" || :) 540 | 541 | 542 | tmp_manifest="$Tempdir/maniF" 543 | tmp_stderr="$Tempdir/stderr" 544 | GET "$URL" "$Manifestfile" "$tmp_manifest" 2>| "$tmp_stderr" || { 545 | if ! isnull "$Repoid"; then 546 | cat >&2 "$tmp_stderr" 547 | echo_info "Repository not found: $URL" 548 | echo_info "..but repository ID is set. Aborting." 549 | return 1 550 | else 551 | echo_info "Repository not found: $URL" 552 | return 0 553 | fi 554 | } 555 | 556 | Did_find_repo=yes 557 | echo_info "Decrypting manifest" 558 | manifest_=$(PRIVDECRYPT "$r_sigmatch" "$r_signers" < "$tmp_manifest") && 559 | isnonnull "$manifest_" || 560 | echo_die "Failed to decrypt manifest!" 561 | rm -f "$tmp_manifest" 562 | 563 | filter_to @Refslist "$Hex40 *" "$manifest_" 564 | filter_to @Packlist "pack :*:* *" "$manifest_" 565 | filter_to @Keeplist "keep :*:*" "$manifest_" 566 | filter_to @Extnlist "extn *" "$manifest_" 567 | filter_to @r_repoid "repo *" "$manifest_" 568 | 569 | r_repoid=${r_repoid#repo } 570 | r_repoid=${r_repoid% *} 571 | if isnull "$Repoid" 572 | then 573 | echo_info "Remote ID is $r_repoid" 574 | Repoid=$r_repoid 575 | elif isnoteq "$r_repoid" "$Repoid" 576 | then 577 | echo_info "WARNING:" 578 | echo_info "WARNING: Remote ID has changed!" 579 | echo_info "WARNING: from $Repoid" 580 | echo_info "WARNING: to $r_repoid" 581 | echo_info "WARNING:" 582 | Repoid=$r_repoid 583 | else 584 | return 0 585 | fi 586 | 587 | isnull "$r_name" || git config "remote.$r_name.gcrypt-id" "$r_repoid" 588 | } 589 | 590 | # $1 is the hash type (SHA256 etc) 591 | # $2 the pack id 592 | # $3 the key 593 | get_verify_decrypt_pack() 594 | { 595 | local rcv_id= tmp_encrypted= 596 | tmp_encrypted="$Tempdir/packF" 597 | GET "$URL" "$2" "$tmp_encrypted" && 598 | rcv_id=$(gpg_hash "$1" < "$tmp_encrypted") && 599 | iseq "$rcv_id" "$2" || echo_die "Packfile $2 does not match digest!" 600 | DECRYPT "$3" < "$tmp_encrypted" 601 | rm -f "$tmp_encrypted" 602 | } 603 | 604 | # download all packlines (pack :SHA256:a32abc1231) from stdin (or die) 605 | # $1 destdir (when repack, else "") 606 | get_pack_files() 607 | { 608 | local pack_id= r_pack_key_line= htype_= pack_= key_= 609 | while IFS=': ' read -r _ htype_ pack_ # </dev/null 630 | xecho "pack $pack_id" >> "$Localdir/have_packs$GITCEPTION" 631 | else 632 | git index-pack -v --stdin "$1/${pack_}.pack" >/dev/null 633 | fi 634 | done 635 | } 636 | 637 | # Download and unpack remote packfiles 638 | # $1 return var for list of packfiles to delete 639 | repack_if_needed() 640 | { 641 | local n_= m_= kline_= r_line= r_keep_packlist= r_del_list= 642 | 643 | isnonnull "$Packlist" || return 0 644 | 645 | if isnonnull "${GCRYPT_FULL_REPACK:-}" 646 | then 647 | Keeplist= 648 | Repack_limit=0 649 | fi 650 | 651 | pick_fields_1_2 @r_del_list "$Packlist" 652 | 653 | n_=$(line_count "$Packlist") 654 | m_=$(line_count "$Keeplist") 655 | if iseq 0 "$(( $Repack_limit < ($n_ - $m_) ))"; then 656 | return 657 | fi 658 | echo_info "Repacking remote $NAME, ..." 659 | 660 | mkdir "$Tempdir/pack" 661 | 662 | # Split packages to keep and to repack 663 | if isnonnull "$Keeplist"; then 664 | while read -r _ kline_ _ # < (if sha-1 exists locally) 754 | r_revlist=$(xfeed "$Refslist" cut -f 1 -d ' ' | 755 | safe_git_rev_parse | sed -e 's/^\(.\)/^&/') 756 | fi 757 | 758 | while IFS=: read -r src_ dst_ # << +src:dst 759 | do 760 | if [ $(echo "$src_" | cut -c1) != + ] 761 | then 762 | force_passed=false 763 | fi 764 | 765 | src_=${src_#+} 766 | filter_to ! @Refslist "$Hex40 $dst_" "$Refslist" 767 | 768 | if isnonnull "$src_" 769 | then 770 | append_to @r_revlist "$src_" 771 | obj_=$(xfeed "$src_" safe_git_rev_parse) 772 | append_to @Refslist "$obj_ $dst_" 773 | fi 774 | done < "$tmp_objlist" 797 | 798 | # Only send pack if we have any objects to send 799 | if [ -s "$tmp_objlist" ] 800 | then 801 | key_=$(genkey "$Packkey_bytes") 802 | pack_id=$(export GIT_ALTERNATE_OBJECT_DIRECTORIES=$Tempdir; 803 | pipefail git pack-objects --stdout < "$tmp_objlist" | 804 | pipefail ENCRYPT "$key_" | 805 | tee "$tmp_encrypted" | gpg_hash "$Hashtype") 806 | 807 | append_to @Packlist "pack :${Hashtype}:$pack_id $key_" 808 | if isnonnull "$r_pack_delete" 809 | then 810 | append_to @Keeplist "keep :${Hashtype}:$pack_id 1" 811 | fi 812 | fi 813 | 814 | # Generate manifest 815 | echo_info "Encrypting to: $Recipients" 816 | echo_info "Requesting manifest signature" 817 | 818 | tmp_manifest="$Tempdir/maniP" 819 | PRIVENCRYPT "$Recipients" > "$tmp_manifest" <&2 869 | } 870 | 871 | setup() 872 | { 873 | mkdir -p "$Localdir" 874 | 875 | # Set up a subdirectory in /tmp 876 | temp_key=$(genkey 9 | tr '/' _) 877 | Tempdir="${TMPDIR:-/tmp}/git-remote-gcrypt-${temp_key}.$$" 878 | case "${MSYSTEM:-unknown}" in 879 | MSYS*|MINGW*) 880 | mkdir "${Tempdir}" 881 | echo_info "Warning: Not securing tempdir ${Tempdir} because we are on mingw/msys" 882 | ;; 883 | unknown|*) 884 | mkdir -m 700 "${Tempdir}" 885 | ;; 886 | esac 887 | 888 | trap cleanup_tmpfiles EXIT 889 | trap 'exit 1' 1 2 3 15 890 | 891 | if isurl rclone "$URL"; then 892 | echo_info "WARNING: rclone support is experimental." 893 | echo_info "WARNING: Early adoptors only. Keep backups." 894 | fi 895 | } 896 | 897 | # handle git-remote-helpers protocol 898 | gcrypt_main_loop() 899 | { 900 | local input_= input_inner= r_args= temp_key= 901 | 902 | NAME=$1 # Remote name 903 | URL=$2 # Remote URL 904 | 905 | setup 906 | 907 | while read input_ 908 | do 909 | case "$input_" in 910 | capabilities) 911 | do_capabilities 912 | ;; 913 | list|list\ for-push) 914 | do_list 915 | ;; 916 | fetch\ *) 917 | r_args=${input_##fetch } 918 | while read input_inner 919 | do 920 | case "$input_inner" in 921 | fetch*) 922 | r_args= #ignored 923 | ;; 924 | *) 925 | break 926 | ;; 927 | esac 928 | done 929 | do_fetch "$r_args" 930 | ;; 931 | push\ *) 932 | r_args=${input_##push } 933 | while read input_inner 934 | do 935 | case "$input_inner" in 936 | push\ *) 937 | append_to @r_args "${input_inner#push }" 938 | ;; 939 | *) 940 | break 941 | ;; 942 | esac 943 | done 944 | do_push "$r_args" 945 | ;; 946 | ?*) 947 | echo_die "Unknown input!" 948 | ;; 949 | *) 950 | CLEAN_FINAL "$URL" 951 | exit 0 952 | ;; 953 | esac 954 | done 955 | } 956 | 957 | if [ "x$1" = x--check ] 958 | then 959 | NAME=dummy-gcrypt-check 960 | URL=$2 961 | setup 962 | ensure_connected 963 | git remote remove $NAME 2>/dev/null || true 964 | if iseq "$Did_find_repo" "no" 965 | then 966 | exit 100 967 | fi 968 | else 969 | gcrypt_main_loop "$@" 970 | fi 971 | -------------------------------------------------------------------------------- /install.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | set -e 4 | 5 | : ${prefix:=/usr/local} 6 | : ${DESTDIR:=} 7 | 8 | verbose() { echo "$@" >&2 && "$@"; } 9 | install_v() 10 | { 11 | # Install $1 into $2/ with mode $3 12 | verbose install -d "$2" && 13 | verbose install -m "$3" "$1" "$2" 14 | } 15 | 16 | install_v git-remote-gcrypt "$DESTDIR$prefix/bin" 755 17 | 18 | if command -v rst2man >/dev/null 19 | then 20 | rst2man='rst2man' 21 | elif command -v rst2man.py >/dev/null # it is installed as rst2man.py on macOS 22 | then 23 | rst2man='rst2man.py' 24 | fi 25 | 26 | if [ -n "$rst2man" ] 27 | then 28 | trap 'rm -f git-remote-gcrypt.1.gz' EXIT 29 | verbose $rst2man ./README.rst | gzip -9 > git-remote-gcrypt.1.gz 30 | install_v git-remote-gcrypt.1.gz "$DESTDIR$prefix/share/man/man1" 644 31 | else 32 | echo "'rst2man' not found, man page not installed" >&2 33 | fi 34 | -------------------------------------------------------------------------------- /redhat/git-remote-gcrypt.spec: -------------------------------------------------------------------------------- 1 | Name: git-remote-gcrypt 2 | Version: 1.2 3 | Release: 1%{?dist} 4 | Summary: GNU Privacy Guard-encrypted git remote 5 | 6 | Group: Development Tools 7 | License: GPLv3 8 | URL: https://git.spwhitton.name/%{name} 9 | Source0: https://git.spwhitton.name/%{name}/snapshot/%{name}-%{version}.tar.gz 10 | 11 | BuildArch: noarch 12 | 13 | BuildRequires: python3-docutils 14 | Requires: gnupg2 git-core 15 | 16 | %description 17 | This lets git store git repositories in encrypted form. 18 | It supports storing repositories on rsync or sftp servers. 19 | It can also store the encrypted git repository inside a remote git 20 | repository. All the regular git commands like git push and git pull 21 | can be used to operate on such an encrypted repository. 22 | 23 | The aim is to provide confidential, authenticated git storage and 24 | collaboration using typical untrusted file hosts or services. 25 | 26 | %prep 27 | %setup -q -n %{name}-%{version} 28 | 29 | %build 30 | : 31 | 32 | %install 33 | export DESTDIR="%{buildroot}" 34 | export prefix="%{_prefix}" 35 | ./install.sh 36 | 37 | %files 38 | %{_bindir}/%{name} 39 | %{_mandir}/man1/%{name}.1* 40 | %license COPYING 41 | %doc CHANGELOG CONTRIBUTING.rst README.rst 42 | 43 | %changelog 44 | 45 | -------------------------------------------------------------------------------- /tests/system-test.sh: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env bash 2 | # SPDX-FileCopyrightText: Copyright 2023 Cathy J. Fitzpatrick 3 | # SPDX-License-Identifier: GPL-2.0-or-later 4 | set -efuC -o pipefail 5 | shopt -s inherit_errexit 6 | 7 | # Unlike the main git-remote-gcrypt program, this testing script requires bash 8 | # (rather than POSIX sh) and also depends on various common system utilities 9 | # that the git-remote-gcrypt carefully avoids using (such as mktemp(1)). 10 | # 11 | # The test proceeds by setting up a new repository, making some large commits 12 | # with random data into the repository, pushing the repository to another 13 | # remote using git-remote-gcrypt over the gitception protocol, and then cloning 14 | # the second repository and ensuring that the data it contains is correct. 15 | # 16 | # The random data is obtained from /dev/urandom. This script won't work 17 | # on systems that don't provide /dev/urandom. 18 | # 19 | # The following settings specify the parameters to be used for the test. 20 | num_commits=5 21 | files_per_commit=3 22 | random_source="/dev/urandom" 23 | random_data_per_file=5242880 # 5 MiB 24 | default_branch="main" 25 | test_user_name="git-remote-gcrypt" 26 | test_user_email="git-remote-gcrypt@example.com" 27 | pack_size_limit="12m" # If this variable is unset, there is no size limit. 28 | 29 | readonly num_commits files_per_commit random_source random_data_per_file \ 30 | default_branch test_user_name test_user_email pack_size_limit 31 | 32 | # Pipe text into this function to indent it with four spaces. This is used 33 | # to make the output of this script prettier. 34 | indent() { 35 | sed 's/^\(.*\)$/ \1/' 36 | } 37 | 38 | section_break() { 39 | echo 40 | printf '*%.0s' {1..70} 41 | echo $'\n' 42 | } 43 | 44 | assert() { 45 | (set +e; [[ -n ${show_command:-} ]] && set -x; "${@}") 46 | local -r status=${?} 47 | { [[ ${status} -eq 0 ]] && echo "Verification succeeded."; } || \ 48 | echo "Verification failed." 49 | return "${status}" 50 | } 51 | 52 | fastfail() { 53 | "$@" || kill -- "-$$" 54 | } 55 | 56 | umask 077 57 | tempdir=$(mktemp -d) 58 | readonly tempdir 59 | # shellcheck disable=SC2064 60 | trap "rm -Rf -- '${tempdir}'" EXIT 61 | 62 | # Set up the PATH to favor the version of git-remote-gcrypt from the repository 63 | # rather than a version that might already be installed on the user's system. 64 | PATH=$(git rev-parse --show-toplevel):${PATH} 65 | readonly PATH 66 | export PATH 67 | 68 | # Unset any GIT_ environment variables to prevent them from affecting the test. 69 | git_env=$(env | sed -n 's/^\(GIT_[^=]*\)=.*$/\1/p') 70 | # shellcheck disable=SC2086 71 | IFS=$'\n' unset ${git_env} 72 | 73 | # Ensure a predictable gpg configuration. 74 | export GNUPGHOME="${tempdir}/gpg" 75 | mkdir "${GNUPGHOME}" 76 | # Use a wrapper for gpg(1) to avoid cluttering the test output with unnecessary 77 | # warnings about the obsolete `--secret-keyring` option. These warnings are 78 | # caused by git-remote-gcrypt passing an option to gpg(1) that only makes sense 79 | # for ancient versions of gpg(1), but addressing that (if it should be 80 | # addressed at all) is a task best left for another day. 81 | cat << 'EOF' > "${GNUPGHOME}/gpg" 82 | #!/usr/bin/env bash 83 | set -efuC -o pipefail; shopt -s inherit_errexit 84 | args=( "${@}" ) 85 | for ((i = 0; i < ${#}; ++i)); do 86 | if [[ ${args[${i}]} = "--secret-keyring" ]]; then 87 | unset "args[${i}]" "args[$(( i + 1 ))]" 88 | break 89 | fi 90 | done 91 | exec gpg "${args[@]}" 92 | EOF 93 | chmod +x "${GNUPGHOME}/gpg" 94 | 95 | # Ensure a predictable git configuration. 96 | export GIT_CONFIG_SYSTEM=/dev/null 97 | export GIT_CONFIG_GLOBAL="${tempdir}/gitconfig" 98 | mkdir "${tempdir}/template" # Intentionally empty template directory. 99 | git config --global init.defaultBranch "${default_branch}" 100 | git config --global user.name "${test_user_name}" 101 | git config --global user.email "${test_user_email}" 102 | git config --global init.templateDir "${tempdir}/template" 103 | git config --global gpg.program "${GNUPGHOME}/gpg" 104 | [[ -n ${pack_size_limit:-} ]] && \ 105 | git config --global pack.packSizeLimit "${pack_size_limit}" 106 | 107 | # Prepare the random data that we'll be writing to the repository. 108 | total_files=$(( num_commits * files_per_commit )) 109 | random_data_size=$(( total_files * random_data_per_file )) 110 | random_data_file="${tempdir}/data" 111 | head -c "${random_data_size}" "${random_source}" > "${random_data_file}" 112 | 113 | # Create gpg key and subkey. 114 | echo "Step 1: Creating a new GPG key and subkey to use for testing:" 115 | ( 116 | set -x 117 | gpg --batch --passphrase "" --quick-generate-key \ 118 | "${test_user_name} <${test_user_email}>" 119 | gpg -K 120 | ) 2>&1 | indent 121 | 122 | ### 123 | section_break 124 | 125 | echo "Step 2: Creating new repository with random data:" 126 | { 127 | git init -- "${tempdir}/first" 128 | cd "${tempdir}/first" 129 | for ((i = 0; i < num_commits; ++i)); do 130 | for ((j = 0; j < files_per_commit; ++j)); do 131 | file_index=$(( i * files_per_commit + j )) 132 | random_data_index=$(( file_index * random_data_per_file )) 133 | # shellcheck disable=SC2016 134 | echo "Writing random file $((file_index + 1))/${total_files}:" \ 135 | '${tempdir}'/"first/$(( file_index )).data " 136 | head -c "${random_data_per_file}" > "$(( file_index )).data" < \ 137 | <(tail -c "+${random_data_index}" "${random_data_file}" || :) 138 | if command -v base64 > /dev/null; then 139 | # shellcheck disable=SC2312 140 | echo "First 24 bytes in base64:" \ 141 | "$(fastfail head -c 24 "$(( file_index )).data" | \ 142 | fastfail base64)" | indent 143 | fi 144 | done 145 | git add -- "${tempdir}/first" 146 | git commit -m "Commit #${i}" 147 | done 148 | 149 | echo 150 | echo "For reference, here is the commit log for the repository:" 151 | git log --format=oneline | indent 152 | } | indent 153 | 154 | ### 155 | section_break 156 | 157 | echo "Step 3: Creating an empty bare repository to receive pushed data:" 158 | git init --bare -- "${tempdir}/second.git" | indent 159 | 160 | 161 | ### 162 | section_break 163 | 164 | echo "Step 4: Pushing the first repository to the second one using gitception:" 165 | { 166 | # Note that when pushing to a bare local repository, git-remote-gcrypt uses 167 | # gitception, rather than treating the remote as a local repository. 168 | ( 169 | set -x 170 | cd "${tempdir}/first" 171 | git push -f "gcrypt::${tempdir}/second.git#${default_branch}" \ 172 | "${default_branch}" 173 | ) 2>&1 174 | 175 | if command -v tree > /dev/null; then 176 | echo 177 | echo "For reference, here is the directory tree of second.git:" 178 | tree "${tempdir}/second.git" 179 | fi 180 | 181 | echo 182 | echo "Here is the size of each object file in second.git:" 183 | ( 184 | cd "${tempdir}/second.git/objects" 185 | find . -type f -exec du -sh {} + 186 | ) | indent 187 | 188 | echo 189 | echo "Note that git-pack-objects(1) will try to ensure that each object is" 190 | echo "smaller than pack.packSizeLimit (${pack_size_limit:-unlimited}" \ 191 | "here) but this isn't always" 192 | echo "possible because each object contains at least one of our random" 193 | echo "files, and each random file has a certain minimum size. As a result," 194 | echo "pack.packSizeLimit is more of a suggestion than a hard limit." 195 | } | indent 196 | 197 | ### 198 | section_break 199 | 200 | echo "Step 5: Cloning the second repository using gitception:" 201 | { 202 | ( 203 | set -x 204 | git clone -b "${default_branch}" \ 205 | "gcrypt::${tempdir}/second.git#${default_branch}" -- \ 206 | "${tempdir}/third" 207 | ) 2>&1 208 | 209 | echo 210 | echo "Verifying that the first and third repositories have the same" 211 | echo "commit log as each other:" 212 | # shellcheck disable=SC2312 213 | assert diff \ 214 | <(fastfail cd "${tempdir}/first"; fastfail git log --oneline) \ 215 | <(fastfail cd "${tempdir}/third"; fastfail git log --oneline) \ 216 | 2>&1 | indent 217 | 218 | echo 219 | echo "Verifying that the first and third repositories have the same" 220 | echo "files in their respective working directories:" 221 | show_command=1 assert diff -r --exclude ".git" -- \ 222 | "${tempdir}/first" "${tempdir}/third" 2>&1 | indent 223 | } | indent 224 | --------------------------------------------------------------------------------