How to Install and Uninstall git-crypt.x86_64 Package on Oracle Linux 8
Last updated: November 26,2024
1. Install "git-crypt.x86_64" package
Please follow the guidelines below to install git-crypt.x86_64 on Oracle Linux 8
$
sudo dnf update
Copied
$
sudo dnf install
git-crypt.x86_64
Copied
2. Uninstall "git-crypt.x86_64" package
Please follow the guidelines below to uninstall git-crypt.x86_64 on Oracle Linux 8:
$
sudo dnf remove
git-crypt.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the git-crypt.x86_64 package on Oracle Linux 8
Last metadata expiration check: 0:34:41 ago on Mon Sep 12 02:51:38 2022.
Available Packages
Name : git-crypt
Version : 0.6.0
Release : 7.el8
Architecture : x86_64
Size : 98 k
Source : git-crypt-0.6.0-7.el8.src.rpm
Repository : epel
Summary : Transparent file encryption in git
URL : https://www.agwa.name/projects/git-crypt
License : GPLv3+ and MIT
Description : git-crypt enables transparent encryption and decryption of files in a
: git repository. Files which you choose to protect are encrypted when
: committed, and decrypted when checked out. git-crypt lets you freely
: share a repository containing a mix of public and private
: content. git-crypt gracefully degrades, so developers without the
: secret key can still clone and commit to a repository with encrypted
: files. This lets you store your secret material (such as keys or
: passwords) in the same repository as your code, without requiring you
: to lock down your entire repository.
Available Packages
Name : git-crypt
Version : 0.6.0
Release : 7.el8
Architecture : x86_64
Size : 98 k
Source : git-crypt-0.6.0-7.el8.src.rpm
Repository : epel
Summary : Transparent file encryption in git
URL : https://www.agwa.name/projects/git-crypt
License : GPLv3+ and MIT
Description : git-crypt enables transparent encryption and decryption of files in a
: git repository. Files which you choose to protect are encrypted when
: committed, and decrypted when checked out. git-crypt lets you freely
: share a repository containing a mix of public and private
: content. git-crypt gracefully degrades, so developers without the
: secret key can still clone and commit to a repository with encrypted
: files. This lets you store your secret material (such as keys or
: passwords) in the same repository as your code, without requiring you
: to lock down your entire repository.