Açıklama Yok

Adrian Freihofer c904f64793 depend on efibootguard if CONFIG_BOOTLOADER_EBG=y 6 yıl önce
classes 3f8a20e71b Add class to encrypt (AES-CBC) an artifact 6 yıl önce
conf 864b7e6de6 layer.conf: Update layer compatibility to thud 7 yıl önce
recipes-bsp a941cf33a7 libubootenv: rename recipe 6 yıl önce
recipes-core c5ec279abd initscripts-swupdate-usb: inherit allarch class 6 yıl önce
recipes-devtools e4b0fb27e4 Updated to mtd-utils 2.x 8 yıl önce
recipes-extended 3599288a7a swupdate-image.inc: remove unused fix_inittab_swupdate 6 yıl önce
recipes-lua b718d446f0 rescuegui: adjust to sync with SWUpdate 7 yıl önce
recipes-support c904f64793 depend on efibootguard if CONFIG_BOOTLOADER_EBG=y 6 yıl önce
COPYING.MIT 020c327419 Receipes to generate a swupdate image 12 yıl önce
README 9cc6781093 Allow expansion of BitBake variables in sw-description files 7 yıl önce

README

meta-swupdate, Yocto layer for deploy tool
==========================================

This layer's purpose is to add support for a deployment
mechanism of Yocto's images based on swupdate project.

Layer dependencies
------------------

This layer depends on:

URI: git://github.com/openembedded/meta-openembedded.git
subdirectory: meta-oe

BitBake variable expansion
--------------------------

To insert the values of BitBake variables into the update file, pre- and postfix
the names with "@@". For example, to automatically set the version tag, use the
line `version = "@@DISTRO_VERSION@@";` in your sw-description file.

Image hashing
-------------

During creation of the update file, occurrences of @IMAGE (where IMAGE is an
image filename) are replaced with the sha256 hash of the image.

SWU image signing
------------

There are 3 signing mechanisms supported by meta-swupdate at the moment:

1. RSA signing:

* Set variable: `SWUPDATE_SIGNING = "RSA"`

* Set `SWUPDATE_PRIVATE_KEY` to the full path of private key file

2. CMS signing:

* Set variable: `SWUPDATE_SIGNING = "CMS"`

* Set `SWUPDATE_CMS_CERT` to the full path of certificate file

* Set `SWUPDATE_CMS_KEY ` to the full path of private key file

3. Custom signing tool:

* Set variable: `SWUPDATE_SIGNING = "CUSTOM"`

* Set variable `SWUPDATE_SIGN_TOOL' to custom string that needs to be
executed in order to perform the signing

sw-description is signed and the signature is written to sw-description.sig
which is included in the SWU file.

Encrypted private keys are not currently supported since a secure
mechanism must exist to provide the passphrase.

Maintainer
----------

Stefano Babic

Submitting patches
------------------

You can submit your patches (or post questions reagarding
this layer to the swupdate Mailing List:

swupdate@googlegroups.com

When creating patches, please use something like:

git format-patch -s --subject-prefix='meta-swupdate][PATCH'

Please use 'git send-email' to send the generated patches to the ML
to bypass changes from your mailer.