├── .gitignore ├── .travis.yml ├── LICENSE ├── README.md ├── SECURITY.md ├── gadget ├── gadget-amd64.yaml └── gadget-arm64.yaml ├── icon.png ├── legacy-bios ├── Makefile ├── mbr.ld └── mbr.s ├── recovery.md ├── snakeoil ├── OVMF_VARS.snakeoil.fd ├── PkKek-1-snakeoil.key └── PkKek-1-snakeoil.pem ├── snap └── hooks │ ├── configure │ └── prepare-device └── snapcraft.yaml /.gitignore: -------------------------------------------------------------------------------- 1 | parts/ 2 | prime/ 3 | stage/ 4 | pc_*.snap 5 | -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | language: minimal 2 | os: linux 3 | dist: bionic 4 | sudo: enabled 5 | addons: 6 | snaps: 7 | - name: snapcraft 8 | channel: edge 9 | classic: true 10 | - name: core20 11 | channel: edge 12 | 13 | script: 14 | - sudo apt update 15 | - sudo snapcraft snap --provider=host --destructive-mode 16 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 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 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # 64bit PC Gadget Snap 2 | 3 | This repository contains the official Ubuntu Core gadget snap for 64bit 4 | Personal Computers using Intel or AMD processors. 5 | 6 | ## Gadget Snaps 7 | 8 | Gadget snaps are a special type of snaps that contain device specific support 9 | code and data. You can read more about them in the snapd wiki 10 | https://github.com/snapcore/snapd/wiki/Gadget-snap 11 | 12 | ## Reporting Issues 13 | 14 | Please report all issues on the Launchpad project page 15 | https://bugs.launchpad.net/snap-pc/+filebug 16 | 17 | We use Launchpad to track issues as this allows us to coordinate multiple 18 | projects better than what is available with Github issues. 19 | 20 | ## Building 21 | 22 | To build the gadget snap locally please use `snapcraft`. 23 | 24 | ## Launchpad Mirror and Automatic Builds. 25 | 26 | All commits from the master branch of https://github.com/snapcore/pc-amd64 27 | are automatically mirrored by Launchpad to the https://launchpad.net/snap-pc 28 | project. 29 | 30 | The master branch is automatically built from the launchpad mirror and 31 | published into the snap store to the edge channel. 32 | 33 | You can find build history and other controls here: 34 | https://code.launchpad.net/~canonical-foundations/+snap/pc-amd64 35 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security policy 2 | 3 | The release model of the pc snap is following rolling releases. 4 | 5 | The pc snap is a gadget snap that contains the bootloader assets required for booting 6 | an Ubuntu Core system. Most of the files contained in this repository are configuration files 7 | used for system initialization. As such these files can be sensitive and must be treated 8 | carefully. Most of the files published with this snap are sourced from the Ubuntu archives 9 | and as such must adhere to same security policies as established for upstream. 10 | 11 | ## Supported versions 12 | When reporting security issues against the pc snap, only the latest 13 | release of the pc snap is supported. Using the newest revision of this gadget snap is 14 | recommendation. 15 | 16 | The pc snap receives intermittent releases determined by upstream changes. There are two 17 | types of security fixes that can be shipped with new versions of the pc snap. 18 | 19 | - Security fixes that are relevant to the files inside this repository 20 | - Security fixes related to the packages sourced from the official APT archives. 21 | 22 | ## What qualifies as a security issue 23 | 24 | Any vulnerability that allows the pc snap to interfere outside of the intended 25 | restrictions qualifies as a security issue, including vulnerabilities that 26 | allows an unprivileged user on the local system to escalate privileges or cause a 27 | denial of service etc due to the use of the contents of the pc snap on the system. 28 | 29 | ## Reporting a vulnerability 30 | 31 | The easiest way to report a security issue is through 32 | [GitHub](https://github.com/canonical/pc-gadget/security/advisories/new). See 33 | [Privately reporting a security 34 | vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability) 35 | for instructions. 36 | 37 | The Ubuntu Core GitHub admins will be notified of the issue and will work with you 38 | to determine whether the issue qualifies as a security issue and, if so, in 39 | which component. We will then handle figuring out a fix, getting a CVE 40 | assigned and coordinating the release of the fix to the pc snap. 41 | 42 | The [Ubuntu Security disclosure and embargo 43 | policy](https://ubuntu.com/security/disclosure-policy) contains more 44 | information about what you can expect when you contact us, and what we 45 | expect from you. 46 | -------------------------------------------------------------------------------- /gadget/gadget-amd64.yaml: -------------------------------------------------------------------------------- 1 | volumes: 2 | pc: 3 | schema: gpt 4 | # bootloader configuration is shipped and managed by snapd 5 | bootloader: grub 6 | structure: 7 | - name: mbr 8 | type: mbr 9 | size: 440 10 | update: 11 | edition: 1 12 | # This mbr simply writes an error to the console, as this 13 | # gadget supports gpt only 14 | content: 15 | - image: mbr.img 16 | # This one should be removed if we find a way to allow updates 17 | # without keeping all partitions. 18 | - name: BIOS Boot 19 | type: 21686148-6449-6E6F-744E-656564454649 20 | size: 1M 21 | offset: 1M 22 | update: 23 | edition: 2 24 | - name: ubuntu-seed 25 | role: system-seed 26 | filesystem: vfat 27 | # UEFI will boot the ESP partition by default first 28 | type: C12A7328-F81F-11D2-BA4B-00A0C93EC93B 29 | # Size of around two seeds to allow for remodeling 30 | size: 1200M 31 | update: 32 | edition: 3 33 | content: 34 | - source: grubx64.efi 35 | target: EFI/ubuntu/grubx64.efi 36 | - source: shim.efi.signed 37 | target: EFI/ubuntu/shimx64.efi 38 | - source: boot.csv 39 | target: EFI/ubuntu/bootx64.csv 40 | - source: fb.efi 41 | target: EFI/boot/fbx64.efi 42 | - source: shim.efi.signed 43 | target: EFI/boot/bootx64.efi 44 | - name: ubuntu-boot 45 | role: system-boot 46 | filesystem: ext4 47 | type: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 48 | # Around 300M would be enough, but keeping as is to allow 49 | # remodeling from previous releases 50 | size: 750M 51 | update: 52 | edition: 1 53 | content: 54 | - source: grubx64.efi 55 | target: EFI/boot/grubx64.efi 56 | - name: ubuntu-save 57 | role: system-save 58 | filesystem: ext4 59 | type: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 60 | # min-size to allow remodeling from previous releases 61 | min-size: 16M 62 | size: 32M 63 | - name: ubuntu-data 64 | role: system-data 65 | filesystem: ext4 66 | type: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 67 | size: 1G 68 | -------------------------------------------------------------------------------- /gadget/gadget-arm64.yaml: -------------------------------------------------------------------------------- 1 | volumes: 2 | pc: 3 | # bootloader configuration is shipped and managed by snapd 4 | schema: gpt 5 | bootloader: grub 6 | structure: 7 | - name: ubuntu-seed 8 | role: system-seed 9 | filesystem: vfat 10 | # UEFI will boot the ESP partition by default first 11 | type: EF,C12A7328-F81F-11D2-BA4B-00A0C93EC93B 12 | # Size of around two seeds to allow for remodeling 13 | size: 1200M 14 | update: 15 | edition: 3 16 | content: 17 | - source: grubaa64.efi 18 | target: EFI/ubuntu/grubaa64.efi 19 | - source: shim.efi.signed 20 | target: EFI/ubuntu/shimaa64.efi 21 | - source: boot.csv 22 | target: EFI/ubuntu/bootaa64.csv 23 | - source: fb.efi 24 | target: EFI/boot/fbaa64.efi 25 | - source: shim.efi.signed 26 | target: EFI/boot/bootaa64.efi 27 | - name: ubuntu-boot 28 | role: system-boot 29 | filesystem: ext4 30 | type: 83,0FC63DAF-8483-4772-8E79-3D69D8477DE4 31 | # Around 300M would be enough, but keeping as is to allow 32 | # remodeling from previous releases 33 | size: 750M 34 | update: 35 | edition: 1 36 | content: 37 | - source: grubaa64.efi 38 | target: EFI/boot/grubaa64.efi 39 | - name: ubuntu-save 40 | role: system-save 41 | filesystem: ext4 42 | type: 83,0FC63DAF-8483-4772-8E79-3D69D8477DE4 43 | size: 32M 44 | - name: ubuntu-data 45 | role: system-data 46 | filesystem: ext4 47 | type: 83,0FC63DAF-8483-4772-8E79-3D69D8477DE4 48 | size: 1G 49 | -------------------------------------------------------------------------------- /icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/canonical/pc-gadget/6bd17851cfff4a7f9d4e12d8fc4a8dbd4adfc95a/icon.png -------------------------------------------------------------------------------- /legacy-bios/Makefile: -------------------------------------------------------------------------------- 1 | all: mbr.img 2 | 3 | mbr.o: mbr.s 4 | gcc -Wall -O0 -c -m16 $< -o $@ 5 | 6 | mbr.bin: mbr.o mbr.ld 7 | ld -melf_i386 -T mbr.ld mbr.o -o $@ 8 | 9 | mbr.img: mbr.bin 10 | dd if=mbr.bin of=mbr.img bs=440 count=1 11 | 12 | install: 13 | install -m 644 mbr.img $(DESTDIR)/ 14 | 15 | .PHONY: install all 16 | -------------------------------------------------------------------------------- /legacy-bios/mbr.ld: -------------------------------------------------------------------------------- 1 | OUTPUT_FORMAT("binary"); 2 | ENTRY(start); 3 | SECTIONS 4 | { 5 | . = 0x7c00; 6 | .text : AT(0x7c00) { 7 | *(.text); 8 | } 9 | .data : { 10 | *(.data); 11 | } 12 | /DISCARD/ : { 13 | *(*); 14 | } 15 | } 16 | -------------------------------------------------------------------------------- /legacy-bios/mbr.s: -------------------------------------------------------------------------------- 1 | .code16 2 | .section .text 3 | .globl start 4 | 5 | start: 6 | jmp $0, $.entry 7 | .entry: 8 | cli 9 | xorw %ax, %ax 10 | movw %ax, %ss 11 | movw %ax, %ds 12 | movw $0x7c00, %sp 13 | sti 14 | cld 15 | movw $.message, %si 16 | .print: 17 | lodsb 18 | cmp $0, %al 19 | je .done 20 | push %si 21 | movb $0xe, %ah 22 | movw $0x0007, %bx 23 | int $0x10 24 | pop %si 25 | jmp .print 26 | .done: 27 | cli 28 | hlt 29 | 30 | .section .data 31 | .message: 32 | .string "Please boot in EFI mode.\r\n\0" 33 | -------------------------------------------------------------------------------- /recovery.md: -------------------------------------------------------------------------------- 1 | # The recovery partition 2 | 3 | On Ubuntu Core 20 systems there is a new ubuntu-seed partition. It 4 | is big enough to contain a certain number of recovery "systems" that 5 | can then be used to recover or reinstall a broken system. 6 | 7 | A full "seed" to reinstall on a generic amd64 system is roughly 280MB 8 | so the recovery partition is sized to 600MB to be able to store two 9 | recovery systems by default. 10 | 11 | The ubuntu-seed partition is next to the ubuntu-boot partition. Both 12 | are vfat as required by UEFI. 13 | 14 | On full disk encrypted systems the ubuntu-boot partition contains the 15 | unpacked kernel(s) to boot init initramfs that then unencrypts the 16 | ubuntu-data ("writable") partition. The partitions are separate 17 | because we want to write to the recovery partition as rarely as 18 | possible to avoid filesystem issues. 19 | 20 | # Recovery system file layout 21 | 22 | The recovery partition contains the following file layout: 23 | 24 | /system//snaps/{base.snap,kernel.snap,other...} 25 | /system//assertions/ 26 | 27 | Where is an encoded date/time like 20190521-1213. We will 28 | use in the name as well once the details are discussed. 29 | 30 | The partition is FAT so we need to put the assertions in the "stream" 31 | format on disk with short filenames. The assertion files all together 32 | must include exactly one model assertion. 33 | 34 | The names of the kernel and the base are fixed. This allows 35 | us a static grub.cfg menu. The selection of the recovery system will 36 | happen at a later time from initramfs. To do this the recovery system 37 | will boot into a special "select" mode and then the selection is set 38 | via a grubenv "snap_recovery_system=" 39 | 40 | All snaps in snaps/ must be verifiable using the assertions.txt 41 | stream and they will be checked during a "recover" or "install" 42 | boot. 43 | 44 | # Boot sequence 45 | 46 | This section describes the operations without taking the TPM into 47 | account for now. This will change in a later revision of this doc. 48 | 49 | * always boot into system-recovery partition 50 | ** check if system is setup for normal booting 51 | *** if so, chainboot into the system-boot partition 52 | *** if not, boot into recovery bootmode, set snap_recovery_mode="recover" 53 | **** later the initramfs will allow selecting different recovery systems 54 | 55 | We always boot into the system-recovery partition. It contain the 56 | /efi/BOOT/BOOTX64.EFI (shim.efi.signed) and grubx86.efi. We will 57 | present a boot menu with the modes "Normal", "Recovery", "Install". 58 | 59 | The "normal" boot mode will just chainboot into the system-boot 60 | partition and load "grub" from there. 61 | 62 | ## Very first boot (install) 63 | 64 | `snap prepare-image` will setup a grubenv for the recovery that points 65 | to the right recovery-system. The kernel is booted from that recovery 66 | system and the initramfs of this kernel will setup the "writable" 67 | partition, copy the recovery system as into /var/lib/snapd/seed and 68 | setup grubenv for the "system-boot" partition - then the system is 69 | booted in "normal" mode and snapd will just do a first time seeding 70 | (just like today). 71 | 72 | 73 | ## Normal bootmode 74 | 75 | No changes to today, TPM operations will have to be added. 76 | 77 | ## Install mode 78 | 79 | Similar to "firstboot" mode we have today. The differences: 80 | * explicitly enabled via `snap_recovery_mode == "install"` 81 | * requires mounting: 82 | ** create "writable" with a new FDE key 83 | ** mount "writable" to the right place 84 | ** the "right" directory /var/lib/snapd/seed from the recovery partition 85 | 86 | 87 | ## Recovery mode 88 | 89 | * explicitly enabled via `snap_recovery_mode == "recovery"` 90 | * requires mounting: 91 | ** unlock /writable to a different mount point 92 | ** create tmpfs on ${rootmnt}/writable 93 | ** mount the right recovery seed into /var/lib/snapd/seed 94 | ** do an "install" into tmpfs to have all snapd available (e.g. nm) 95 | 96 | 97 | # Testing 98 | 99 | Hacky way to test this: 100 | ``` 101 | $ wget https://people.canonical.com/~mvo/tmp/mvo-amd64.signed 102 | $ snap download pc-kernel=18 core18 snapd 103 | $ cd pc-amd64-gadget 104 | $ snapcraft 105 | $ cd .. 106 | $ ubuntu-image mvo-amd64.signed --extra-snaps ./pc_20-0.1_amd64.snap --extra-snaps ./pc-kernel_*.snap --extra-snaps ./core18_*.snap --extra-snaps ./snapd_*.snap 107 | # use the OVMF.fd from bionc - disco will fail to start 108 | $ kvm -m 1500 -snapshot -bios /usr/share/qemu/OVMF.fd pc.img 109 | ``` 110 | -------------------------------------------------------------------------------- /snakeoil/OVMF_VARS.snakeoil.fd: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/canonical/pc-gadget/6bd17851cfff4a7f9d4e12d8fc4a8dbd4adfc95a/snakeoil/OVMF_VARS.snakeoil.fd -------------------------------------------------------------------------------- /snakeoil/PkKek-1-snakeoil.key: -------------------------------------------------------------------------------- 1 | -----BEGIN RSA PRIVATE KEY----- 2 | MIIEpAIBAAKCAQEAzUDpJwDzDpLo2ytVRSgt/QWRYk/Yjae5fbujitq73XYLuDZ+ 3 | /Wf5U6zpOfyfzX/l5R0KCV9XYUJF47QEmNCnoWpg3cRdRry+3FIYtdnNK151AZ2L 4 | 74OI4sMX1akSE+MfZFgdPFcm+n0uJgQuvRYGyYaR6N1wbhJ/2iOOba+sbKycaKiL 5 | 1fSjip2criHA/05cYSomdUT+rTUZALFdCQuOU+gX8Rqhmfbo8VEE7MpE3nrvHocQ 6 | AFphyYgG8jadjggymE7sQEZGrBqOrwMDHitbpoGNlOI2VdFgL5jRKHuB61iCkqTm 7 | SWuS4lbOEJmms6hhQnTnu/yK7O3NEWegAPMrtQIDAQABAoIBAQClG/Ux8fqTm6wD 8 | Ok2CrzqnUgZMbmyGLwjw0rNRLHl5Qc9VpUjsMeqH3A1VHxmxppPZhU2gknho/XXZ 9 | IOOdxiNCnp9DZgWetJBYDRZhms4HeBlpbkG2Lzo7J7MRpcqsAsUq5BLIilcJow8v 10 | d6fdZU2aaU0QZKlfcjQ01uto4qsyUws1oph1sj5SuzI3zslf1/xg/K7oK9Bf4pLo 11 | M1SVwiLoZzutqLlNSJqPgIG94yTOYduglnq4WvDXes+pbxzNINNeIMy+NCa8Xoaj 12 | pGKf+lReql9+7Ex8gMPSeEVEETgvyy/l2AAEGTL9xgSYZJ+hTgZSrgZiS8NNZkyl 13 | 7jchn9RBAoGBAOnEoYe7jyR3qqh6ZnXbdAwYMBbnh96Vz79WurAwbfD9zyd++qfF 14 | 9UKaC99LGWHPnBFyXInKGquTaq5CQDZbR4NNLB6snxH2g0trK9/HualqA+NQbBXW 15 | zZn3tkmrp15kme3f0A/NdJflGkTQkXaGXJnghaXF0bNDdZ3NgtMPmGvxAoGBAODG 16 | DwmeN5QdankoVHGmP1hYlpyazXaCUafUu8YTwKqV5htfbrXPoHk7zfsvGKjlYNSA 17 | ml6X2FewRu1XQ95i0EyMXWovfEZeKxASq0hlenMl5IIWhnmRy9jPfxS8Qma3xKW8 18 | 5fNpGnAiRwmokIrvSFU7Dmm8KFuvMRL389RR2hAFAoGAJj63Np+m4Y56aynrTWjj 19 | 6X6jj3u9rNrRrDoiPOUPd5fupkWN+JjYcVcGjjeZJXlzzR7qqNhZ2Kw7jdrk6n+w 20 | iXi8uSAAvk2YWWRlPy1L4L2peS0VIdWMuZ3fQtpEfZrz3Aj73zn700X2MD/3LG77 21 | A2nKM77TegKVYYXX23P3ueECgYBWVTxpYU/PoAzJRGhKzqP99ujCdeL85ckfQWJu 22 | DiAuZSzgzqLjSkBE0GepVsmN9axfcpXYR1JdO+PCPYZf4GxJOpCWvG5rSLgZkFIh 23 | mHiTybYfES/NeeZl/Cy/dh+6/FKXphpch74T29aVKx15f7a0pd4/VnnZ3UxoELyi 24 | jF3JUQKBgQCgsHr8ia5YZ722UM48lc1j8st9NvN+9J7E2JzgYdslbT04XDgnsKfU 25 | xxMtBQFZDGKhNbHaQDedT3Q+VDxhaEZF3f+R0E0g5FRh4Tu1aIVzPx/5zUILaLaA 26 | 0UjJMU8pkEx2neSzXrIt3QhKmtYEwoMofPXQoxdafppy4tMSE7ZKAA== 27 | -----END RSA PRIVATE KEY----- 28 | -------------------------------------------------------------------------------- /snakeoil/PkKek-1-snakeoil.pem: -------------------------------------------------------------------------------- 1 | -----BEGIN CERTIFICATE----- 2 | MIIDCTCCAfGgAwIBAgIUSbJC1oRCJUbGkwfWHscBeZrRHZcwDQYJKoZIhvcNAQEL 3 | BQAwFDESMBAGA1UECgwJU25ha2UgT2lsMB4XDTE5MTEwMTIyMDI1NVoXDTE5MTIw 4 | MTIyMDI1NVowFDESMBAGA1UECgwJU25ha2UgT2lsMIIBIjANBgkqhkiG9w0BAQEF 5 | AAOCAQ8AMIIBCgKCAQEAzUDpJwDzDpLo2ytVRSgt/QWRYk/Yjae5fbujitq73XYL 6 | uDZ+/Wf5U6zpOfyfzX/l5R0KCV9XYUJF47QEmNCnoWpg3cRdRry+3FIYtdnNK151 7 | AZ2L74OI4sMX1akSE+MfZFgdPFcm+n0uJgQuvRYGyYaR6N1wbhJ/2iOOba+sbKyc 8 | aKiL1fSjip2criHA/05cYSomdUT+rTUZALFdCQuOU+gX8Rqhmfbo8VEE7MpE3nrv 9 | HocQAFphyYgG8jadjggymE7sQEZGrBqOrwMDHitbpoGNlOI2VdFgL5jRKHuB61iC 10 | kqTmSWuS4lbOEJmms6hhQnTnu/yK7O3NEWegAPMrtQIDAQABo1MwUTAdBgNVHQ4E 11 | FgQUFD7OXb2T6sOysRo3hj2f15SX8I8wHwYDVR0jBBgwFoAUFD7OXb2T6sOysRo3 12 | hj2f15SX8I8wDwYDVR0TAQH/BAUwAwEB/zANBgkqhkiG9w0BAQsFAAOCAQEANZRB 13 | NFVUVZVehpj3QGbbSjp77m0V6JrEYn6u/XjLRFsUNw5Hh35UCR0HkKZ0cLgrVKb/ 14 | 8yL6LaYLOY6yDwEFWMtLXiF2S4noO8raEgW6A7DHawb2Y4ZNFRO4oBkyWbtd36Uu 15 | UfSszs2av048wb5J/pNedRSx8I/FiCNWummzpkBHzx023TdLPd8fmkmG7ZBpStN0 16 | Y//EE4DKTfHxAwt5w7WdZF5EY/KHPopnR+WSrdutRIK6zT+/+vKihtHYZbrv+7Ap 17 | K7xOM/zJ6E9vUROmuOhL3YL3MuLn5qHEvhM0eMxEAlCnSJlFkQE4/RXhDpZJYbR7 18 | x+PQllgoo4H6W30Dew== 19 | -----END CERTIFICATE----- 20 | -------------------------------------------------------------------------------- /snap/hooks/configure: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | # do nothing for now 4 | -------------------------------------------------------------------------------- /snap/hooks/prepare-device: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | # This file is included for reference purposes. If MODEL_APIKEY is not set 4 | # in snapcraft.yaml (as is the default), it is a no-op. For more about how 5 | # to use this script to connect a device to an IoT App Store, see 6 | # - https://ubuntu.com/core/services/guide/serial-vault-overview 7 | # - https://ubuntu.com/core/services/guide/connecting-devices 8 | # - https://snapcraft.io/docs/gadget-snap#heading--prepare 9 | 10 | set -eu 11 | 12 | if [ -z "$MODEL_APIKEY" ] ; then 13 | exit 0 14 | fi 15 | 16 | exec >> $SNAP_COMMON/prepare-device-hook.log 2>&1 17 | 18 | # If you are forking and building your own gadget: 19 | # implement your preferred way of generating a serial number for this device here 20 | snapctl set registration.proposed-serial="\"$(date -u)\"" 21 | 22 | snapctl set device-service.url="https://serial-vault-partners.canonical.com/v1/" 23 | snapctl set device-service.headers="{\"api-key\": \"$MODEL_APIKEY\"}" 24 | -------------------------------------------------------------------------------- /snapcraft.yaml: -------------------------------------------------------------------------------- 1 | name: pc 2 | version: '24-0.2' 3 | type: gadget 4 | base: core24 5 | summary: PC gadget for generic devices 6 | description: | 7 | This gadget enables generic pc devices to work with Ubuntu Core 8 | confinement: strict 9 | grade: stable 10 | icon: icon.png 11 | 12 | #package-repositories: 13 | # - type: apt 14 | # ppa: ucdev/uc-staging-ppa 15 | # priority: always 16 | 17 | hooks: 18 | prepare-device: 19 | environment: 20 | # If you are forking and building your own gadget: 21 | # define your model's API key here 22 | # See https://ubuntu.com/core/services/guide/serial-vault-overview 23 | # for instructions on how to generate an API key 24 | # DO NOT check this API key into a publicly accessible VCS 25 | MODEL_APIKEY: "" 26 | 27 | # Min version to support shim 15.7 28 | assumes: 29 | - snapd2.63 30 | 31 | parts: 32 | mbr: 33 | source: legacy-bios 34 | plugin: make 35 | override-build: | 36 | if [ "${CRAFT_ARCH_BUILD_FOR}" != amd64 ]; then 37 | exit 38 | fi 39 | craftctl default 40 | boot-assets: 41 | plugin: nil 42 | build-packages: 43 | - sbsigntool 44 | stage-packages: 45 | - grub-efi-$CRAFT_ARCH_BUILD_FOR-signed 46 | - shim-signed 47 | override-build: | 48 | set -x 49 | 50 | # Set some variables that depend on the architecture 51 | grub_target=x86_64 52 | grub_bin=grubx64.efi.signed 53 | shim_bin=shimx64.efi.dualsigned 54 | fb_bin=fbx64.efi 55 | boot_csv=BOOTX64.CSV 56 | if [ "${CRAFT_ARCH_BUILD_FOR}" = arm64 ]; then 57 | grub_target=arm64 58 | grub_bin=grubaa64.efi.signed 59 | shim_bin=shimaa64.efi.dualsigned 60 | fb_bin=fbaa64.efi 61 | boot_csv=BOOTAA64.CSV 62 | fi 63 | 64 | # Make sure we have have the right signatures 65 | shim_path="${CRAFT_PART_INSTALL}"/usr/lib/shim/$shim_bin 66 | fb_path="${CRAFT_PART_INSTALL}/usr/lib/shim/${fb_bin}" 67 | bootcsv_path="${CRAFT_PART_INSTALL}/usr/lib/shim/${boot_csv}" 68 | grub_path="${CRAFT_PART_INSTALL}"/usr/lib/grub/"$grub_target"-efi-signed/$grub_bin 69 | sbverify --list "$shim_path" | grep -E 'Canonical Ltd. Secure Boot Signing \(2022 v1\)' 70 | sbverify --list "$grub_path" | grep -E 'Canonical Ltd. Secure Boot Signing \(2022 v1\)' 71 | 72 | # Move shim/grub to the expected path 73 | install -m 644 "$shim_path" "${CRAFT_PART_INSTALL}"/shim.efi.signed 74 | install -m 644 "$grub_path" "${CRAFT_PART_INSTALL}"/${grub_bin%.signed} 75 | install -m 644 "${fb_path}" "${CRAFT_PART_INSTALL}/fb.efi" 76 | install -m 644 "${bootcsv_path}" "${CRAFT_PART_INSTALL}/boot.csv" 77 | 78 | # Remove all the bits we do not need, keeping changelogs and copyrights 79 | # (using organize/prime is not possible due to different names per arch - x64/aa64) 80 | find "${CRAFT_PART_INSTALL}"/ -type f,l \ 81 | -not -path "${CRAFT_PART_INSTALL}"/shim.efi.signed \ 82 | -not -path "${CRAFT_PART_INSTALL}"/${grub_bin%.signed} \ 83 | -not -path "${CRAFT_PART_INSTALL}"/fb.efi \ 84 | -not -path "${CRAFT_PART_INSTALL}"/boot.csv \ 85 | -not -path "${CRAFT_PART_INSTALL}"/usr/share/doc/grub-efi-${CRAFT_ARCH_BUILD_FOR}-signed/'*' \ 86 | -and -not -path "${CRAFT_PART_INSTALL}"/'usr/share/doc/shim-signed/*' \ 87 | -delete 88 | find "${CRAFT_PART_INSTALL}"/ -type d -empty -delete 89 | 90 | # grub.conf lets snapd identify grub as the bootloader on boot 91 | install -m 644 /dev/null "${CRAFT_PART_INSTALL}"/grub.conf 92 | gadget: 93 | plugin: nil 94 | source: gadget 95 | override-build: 96 | # We need to install directly in the project dir as snapcraft checks there 97 | # for gadget.yaml instead of looking first at the prime folder. 98 | install -m 644 gadget-"${CRAFT_ARCH_BUILD_FOR}".yaml "${CRAFT_PROJECT_DIR}"/gadget.yaml 99 | --------------------------------------------------------------------------------