swupd-client

mirror of https://github.com/clearlinux/swupd-client.git synced 2026-09-07 22:21:32 +00:00

T

This release enables mandatory signature verification, which means the
Manifest.MoM signature MUST verify correctly for an update operation to
continue, else swupd will exit. This ensures that wherever the content comes
from, i.e thru a CDN, clients are guaranteed to receive the "correct" content
that they were intended to consume. It also forces clients to remain on the
secure update path if only verifiable content is allowed on the system.

Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>

2017-01-25 14:58:36 -08:00

certs

Initial commit

2016-02-24 09:34:13 -08:00

data

Move to automatic updates: unit changes.

2016-11-17 00:52:22 -08:00

docs

Add doc about bundle-list sub-command

2017-01-18 09:52:49 -08:00

include

Move signature verification to mandatory

2017-01-25 15:00:24 -08:00

build: track m4 directory to avoid aclocal warning

2016-11-11 10:52:05 -08:00

scripts

Update comment

2016-09-06 11:26:03 -07:00

src

Move signature verification to mandatory

2017-01-25 15:00:24 -08:00

test

Add missing certificate attributes conf

2016-12-21 12:18:08 -08:00

.clang-format

Add Clang format style file

2016-03-07 14:23:18 -08:00

.gitignore

build: ignore file created by autogen.sh

2017-01-24 17:30:42 -08:00

.travis.yml

Add travis-ci integration for functional testing

2016-11-22 15:22:24 -08:00

autogen.sh

Add autogen.sh

2016-11-17 00:52:22 -08:00

configure.ac

Release v3.7.6

2017-01-25 14:58:36 -08:00

COPYING

Initial commit

2016-02-24 09:34:13 -08:00

Makefile.am

Add new bundle-list sub-command

2017-01-18 09:52:49 -08:00

README

Initial commit

2016-02-24 09:34:13 -08:00

swupd.bash

Refresh completion script

2016-06-09 13:36:23 -07:00

template

Initial commit

2016-02-24 09:34:13 -08:00

README

The swupd-client package provides a reference implementation of a software
update client which performs file level updates of an OS, preferentially
using binary deltas whenever possible for efficiency under an assumption
that the OS develops with a release process aimed at rapidly deploying
small incremental changes.