forked from pool/python-kiwi
- Bump version: 9.18.11 → 9.18.12
- Added MicroOS integration test The future technologies team is implementing a coreOS derivate based on btrfs and some overlay technology. For supporting them some changes were required in kiwi and thus we should add an integration test build which makes use of this features. - Add required cryptomount coding for EFI boot For non EFI boot grub2-install has code which gets activated through the GRUB_ENABLE_CRYPTODISK setting. However for the EFI boot case no installation of boot code is needed and therefore the grub earlyboot script has to run cryptomount - Add /mnt to list of protected paths On recursive removal make sure /mnt belong to the protected elements. This Fixes #1170 - Added full encrypted image build test - Extended LUKS encryption support We supported luks encrypted images with the exception of the boot partition because grub was not able to read from an encrypted device at that time. Since some time grub is able to read from an encrypted partition and this commit add support for it. With this patch luks encrypted images will no longer create an extra boot partition and the entire system will be encrypted. The opening of the luks container happens on the grub level only once. Customers can still specify to use an unencrypted extra boot partition with the OBS-URL: https://build.opensuse.org/package/show/Virtualization:Appliances:Builder/python-kiwi?expand=0&rev=147
This commit is contained in:
parent
2e450ea010
commit
cf18206513
@ -1,3 +1,114 @@
|
||||
-------------------------------------------------------------------
|
||||
Tue Aug 20 09:48:00 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Bump version: 9.18.11 → 9.18.12
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 19 18:33:50 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Added MicroOS integration test
|
||||
|
||||
The future technologies team is implementing a coreOS derivate
|
||||
based on btrfs and some overlay technology. For supporting them
|
||||
some changes were required in kiwi and thus we should add an
|
||||
integration test build which makes use of this features.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 19 18:28:46 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Add required cryptomount coding for EFI boot
|
||||
|
||||
For non EFI boot grub2-install has code which gets activated
|
||||
through the GRUB_ENABLE_CRYPTODISK setting. However for the
|
||||
EFI boot case no installation of boot code is needed and
|
||||
therefore the grub earlyboot script has to run cryptomount
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 19 14:34:08 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Add /mnt to list of protected paths
|
||||
|
||||
On recursive removal make sure /mnt belong to the protected
|
||||
elements. This Fixes #1170
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 19 11:17:35 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Added full encrypted image build test
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Fri Aug 16 17:49:09 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Extended LUKS encryption support
|
||||
|
||||
We supported luks encrypted images with the exception of the
|
||||
boot partition because grub was not able to read from an
|
||||
encrypted device at that time. Since some time grub is able
|
||||
to read from an encrypted partition and this commit add
|
||||
support for it. With this patch luks encrypted images will
|
||||
no longer create an extra boot partition and the entire
|
||||
system will be encrypted. The opening of the luks container
|
||||
happens on the grub level only once. Customers can still
|
||||
specify to use an unencrypted extra boot partition with the
|
||||
bootpartition="true" flag. In this case the opening of the
|
||||
luks containers happens on the systemd level as before.
|
||||
This is related to Issue #1162
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Thu Aug 15 09:52:27 CEST 2019 - Stefan Seyfried <stefan.seyfried@sap.com>
|
||||
|
||||
- remove '-z' option from rsync local copy calls
|
||||
|
||||
rsync's "compress" option just does not make any sense when rsync is
|
||||
used to copy files locally, it only increases CPU usage and slows down
|
||||
the process ;-)
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Wed Aug 14 14:45:13 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Delete SuSEfirewall2 from test builds
|
||||
|
||||
The package seems to be no longer present on suse
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Wed Aug 14 12:01:34 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Bump version: 9.18.10 → 9.18.11
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 12 18:17:02 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Allow dracut initrd to be used with pxe type
|
||||
|
||||
The pxe image type builds a simple filesystem image plus a
|
||||
custom initrd. That initrd is usually build from the kiwi
|
||||
netboot image descriptions which implements a workflow to
|
||||
fetch the filesystem image and deploy it as rootfs for a
|
||||
pxe client. User who wants to implement their own handling
|
||||
of the rootfs image in e.g a custom dracut module were not
|
||||
able to build this image type because we did not allow
|
||||
the initrd_system attribute for the pxe type
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 12 10:53:08 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Use message variable for long message text
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 12 10:42:11 CEST 2019 - Marcus Schäfer <ms@suse.de>
|
||||
|
||||
- Fixed handling of bool values in initrd code
|
||||
|
||||
Some values evaluated in the initrd code are created in
|
||||
the kiwi builder and passed in as a profile file. bool
|
||||
values created by kiwi for use in shell scripts takes
|
||||
the string 'true' or 'false' or are not set at all if not
|
||||
specified in the kiwi XML description. Some code paths
|
||||
in the initrd code uses the '-n' switch to check for bool
|
||||
values, however if the string 'false' is passed '-n' will
|
||||
do the wrong thing. Therefore a method for the initrd
|
||||
code has been introduced to clearly handle bool values
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 05 09:55:02 CEST 2019 - David Cassany <dcassany@suse.com>
|
||||
|
||||
|
@ -43,7 +43,7 @@
|
||||
%endif
|
||||
|
||||
Name: python-kiwi
|
||||
Version: 9.18.10
|
||||
Version: 9.18.12
|
||||
Provides: kiwi-schema = 7.1
|
||||
Release: 0
|
||||
Url: https://github.com/SUSE/kiwi
|
||||
|
@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:abbadafed91d1d882a815072de52294af90171e788d33194dad3b1b757c75876
|
||||
size 1609429
|
||||
oid sha256:d1caaee90db4a38f94be782c5714021eb610aa3e2a28a31a629c66e0cfeb84d3
|
||||
size 1622420
|
||||
|
Loading…
Reference in New Issue
Block a user