The release contains several bugfixes. This change also adds some upstream
patches that fixes backward incompatibilities changes that were introduced
in the 3.1.0 release.
Resolves: rhbz#1625647
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
tpm2-tools 3.0.4 version is just a minor release that contains several
fixes, the most important being a fix for how private keys were stored.
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
The tpm2-tools 3.0.2 version is just a minor release that fixes undefined
references in libmarshal and makes tools that don't use the TPM device to
not attempt to create a connection.
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
The tpm2-tools 3.0.2 version was released, this is just a minor release
that fixes buffer overflows, other issues and adds integration tests to
the generated tarball. Update the package to this latest version.
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
The tpm2-tools 3.0.1 version was released, this is just a minor release
that fixes an issue that the LICENSE file and other docs were not added
to the generated tarball.
Update the package to this version and also use the generated tarball
instead of the source code tarball, now that includes a license file.
resolves: rhbz#1512743
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
This commit updates tpm2-tools to version 3.0-rc1. It also does some
cleanups to the package such as using the latest URL for the project
repository.
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
This commit updates the tpm2-tools package to version 2.1.1. It also does
some cleanups such as changing the prefixes to tpm2-tools that is the new
name for the upstream project repository. Since this matches the pkg name
the global pkg_prefix can be removed.
It also removes the downstream patches since these are already present in
the latest upstream release.
resolves: rhbz#1504438
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
The source tarballs don't need to be in the package git repository, since
tools building the package will obtain the source url from the SPEC file
and download it before doing the build.
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
