How to Install and Uninstall opencryptoki-libs.x86_64 Package on Fedora 34
Last updated: July 05,2024
1. Install "opencryptoki-libs.x86_64" package
Please follow the instructions below to install opencryptoki-libs.x86_64 on Fedora 34
$
sudo dnf update
Copied
$
sudo dnf install
opencryptoki-libs.x86_64
Copied
2. Uninstall "opencryptoki-libs.x86_64" package
This tutorial shows how to uninstall opencryptoki-libs.x86_64 on Fedora 34:
$
sudo dnf remove
opencryptoki-libs.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the opencryptoki-libs.x86_64 package on Fedora 34
Last metadata expiration check: 5:14:33 ago on Tue Sep 6 08:10:37 2022.
Available Packages
Name : opencryptoki-libs
Version : 3.16.0
Release : 2.fc34
Architecture : x86_64
Size : 47 k
Source : opencryptoki-3.16.0-2.fc34.src.rpm
Repository : updates
Summary : The run-time libraries for opencryptoki package
URL : https://github.com/opencryptoki/opencryptoki
License : CPL
Description : Opencryptoki implements the PKCS#11 specification v2.11 for a set of
: cryptographic hardware, such as IBM 4764 and 4765 crypto cards, and the
: Trusted Platform Module (TPM) chip. Opencryptoki also brings a software
: token implementation that can be used without any cryptographic
: hardware.
: This package contains the PKCS#11 library implementation, and requires
: at least one token implementation (packaged separately) to be fully
: functional.
Available Packages
Name : opencryptoki-libs
Version : 3.16.0
Release : 2.fc34
Architecture : x86_64
Size : 47 k
Source : opencryptoki-3.16.0-2.fc34.src.rpm
Repository : updates
Summary : The run-time libraries for opencryptoki package
URL : https://github.com/opencryptoki/opencryptoki
License : CPL
Description : Opencryptoki implements the PKCS#11 specification v2.11 for a set of
: cryptographic hardware, such as IBM 4764 and 4765 crypto cards, and the
: Trusted Platform Module (TPM) chip. Opencryptoki also brings a software
: token implementation that can be used without any cryptographic
: hardware.
: This package contains the PKCS#11 library implementation, and requires
: at least one token implementation (packaged separately) to be fully
: functional.