README 1.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. meta-swupdate, Yocto layer for deploy tool
  2. ==========================================
  3. This layer's purpose is to add support for a deployment
  4. mechanism of Yocto's images based on swupdate project.
  5. Layer dependencies
  6. ------------------
  7. This layer depends on:
  8. URI: git://github.com/openembedded/meta-openembedded.git
  9. subdirectory: meta-oe
  10. Image hashing
  11. -------------
  12. During creation of the update file, occurrences of @IMAGE (where IMAGE is an
  13. image filename) are replaced with the sha256 hash of the image.
  14. SWU image signing
  15. ------------
  16. There are 3 signing mechanism supported by meta-swupdate at the moment:
  17. 1. RSA signing:
  18. * Set variable: `SWUPDATE_SIGNING = "RSA"`
  19. * Set `SWUPDATE_PRIVATE_KEY` to the full path of private key file
  20. 2. CMS signing:
  21. * Set variable: `SWUPDATE_SIGNING = "CMS"`
  22. * Set `SWUPDATE_CMS_CERT` to the full path of certificate file
  23. * Set `SWUPDATE_CMS_KEY ` to the full path of private key file
  24. 3. Custom signing tool:
  25. * Set variable: `SWUPDATE_SIGNING = "CUSTOM"`
  26. * Set variable `SWUPDATE_SIGN_TOOL' to custom string that needs to be
  27. executed in order to perform the signing
  28. sw-description is signed and the signature is written to sw-description.sig
  29. which is included in the SWU file.
  30. Encrypted private keys are not currently supported since a secure
  31. mechanism must exist to provide the passphrase.
  32. Maintainer
  33. ----------
  34. Stefano Babic <sbabic@denx.de>
  35. Submitting patches
  36. ------------------
  37. You can submit your patches (or post questions reagarding
  38. this layer to the swupdate Mailing List:
  39. swupdate@googlegroups.com
  40. When creating patches, please use something like:
  41. git format-patch -s --subject-prefix='meta-swupdate][PATCH' <revision range>
  42. Please use 'git send- email' to send the generated patches to the ML
  43. to bypass changes from your mailer.