Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build separate Debian package for libuta provisioning tools #12

Open
zeschg opened this issue Mar 7, 2022 · 2 comments
Open

Build separate Debian package for libuta provisioning tools #12

zeschg opened this issue Mar 7, 2022 · 2 comments

Comments

@zeschg
Copy link
Collaborator

zeschg commented Mar 7, 2022

Currently the TPM implementation needs the installation of further tools and helper scripts for key provisioning. After the provisioning step, these tools are not needed anymore. We should consider to implement an option to uninstall the provisioning tools.

To avoid the installation of the Debian package "tss2", we could implement our own provisioning tool based on libtss0 instead of using the shell script.

@StefanSchroeder
Copy link

An alternative would be to split up the package into the deployment-package and the persistent package. The deployment package would have the required dependencies for installation and it would have the persistent package as a dependency. After the installation, the obsolete deployment package could then be garbage-collected.

@ralisi
Copy link

ralisi commented Mar 9, 2022

Such maneuvers would cover a rather broad area of the current debian packaging, which is currently using the non-standard debian/configure script. It seems that the same task could also be done through DEB_BUILD_PROFILES.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants