How to Install and Uninstall git-crypt Package on openSuSE Tumbleweed
Last updated: November 26,2024
1. Install "git-crypt" package
Please follow the guidance below to install git-crypt on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
git-crypt
Copied
2. Uninstall "git-crypt" package
This is a short guide on how to uninstall git-crypt on openSuSE Tumbleweed:
$
sudo zypper remove
git-crypt
Copied
3. Information about the git-crypt package on openSuSE Tumbleweed
Information for package git-crypt:
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : git-crypt
Version : 0.7.0-2.5
Arch : x86_64
Vendor : openSUSE
Installed Size : 207.3 KiB
Installed : No
Status : not installed
Source package : git-crypt-0.7.0-2.5.src
Upstream URL : https://www.agwa.name/projects/git-crypt/
Summary : Transparent file encryption in git
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.
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : git-crypt
Version : 0.7.0-2.5
Arch : x86_64
Vendor : openSUSE
Installed Size : 207.3 KiB
Installed : No
Status : not installed
Source package : git-crypt-0.7.0-2.5.src
Upstream URL : https://www.agwa.name/projects/git-crypt/
Summary : Transparent file encryption in git
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.