Skip to main content
py-3parencryptor
======================

This package provides the user using HPE 3PAR Array as their storage on platforms like docker, k8s and openshift a functionality by whuch they can encrypt their passwords present in configurstion file (hpe.conf).

hpe.conf is a configuration file for accessing 3PAR array.

Downloading the package
=======================

Tis package can be downloaded from pip. Use below command for downloading the package::

$pip install py-3parencryptor

Pre-requisite and Enviornment
=====================================
* Linux(CentOS, Ubuntu, Red Hat, etcd)
* Docker installed
* etcd container running
* hpe.conf configured properly on /etc/hpedockerplugin/hpe.conf
* etcd parameters propelry mentioned in hpe.conf

### Usage

When py-3parencryptor is installed on machine. It can be used with the help of hpe3parencryptor command like below.
You have to use the same passphrase to encrypt all the passwords for a backend.
There can be 4 possible password:
1. hpe3par_password
2. san_password
3. hpe3par_password for replication array
4. san_password for replication array.

After generating the password replace the password with encrypted one.

````
#hpe3parencryptor -a <passphrase> <password>

Example:

#hpe3parencryptor -a "@123#" "password"
SUCCESSFUL: Encrypted password: +CB1E8Je1j8=

````
#### Add the encrypted password in /etc/hpedockerplugin/hpe.conf

Use the encrypted password generated by utility as hpe3par_password in hpe.conf

enable the plugin now

#### Running the utility with -d option
If user wants to remove the current encrypted password and replace it with plain text or new encrypted password,
user need to delete the current password by using -d option in the utility.

````
# hpe3parencryptor -d
Key Successfully deleted
````
## For Multiple backend

#### Encrypting a specific backend
- When multiple backend present in the configuration file(hpe.conf). User can use the utility to encrypt the password on backend basis.
- With --backend option user can provide the backend for which backend they want to encrypt the passwords.

````
#hpe3parencryptor -a <passphrase> <password> --backend <backend_name>

````
#### Removing encrypted password from a specific backend

Users can remove the encrypted password of a specific backend. Users can use the utility to delete that.
There is an additional optional argument with -d, --backend.

````
# hpe3parencryptor -d --backend <backend_name>

````

#### Note :
````
If --backend is not used, in both the case (-a and -d), package will take the default backend for performing the operations.
````


Metadata

Release files for py-3parencryptor 1.0.9

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for py-3parencryptor 1.0.9
File Size Uploaded Provenance Actions
py-3parencryptor-1.0.9.tar.gz 5.1 kB Without provenance Details for py-3parencryptor-1.0.9.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for py-3parencryptor 1.0.9
File Interpreter ABI Platform Actions
py_3parencryptor-1.0.9-py2.7.egg Legacy Egg format - - Details for py_3parencryptor-1.0.9-py2.7.egg
py_3parencryptor-1.0.9-py2-none-any.whl Python 2 none any Details for py_3parencryptor-1.0.9-py2-none-any.whl

Total release size: 21.1 kB

Release files / py-3parencryptor-1.0.9.tar.gz

Download URL py-3parencryptor-1.0.9.tar.gz
Size 5.1 kB
Tags Source
SHA-256 checksum
How to use checksums
e56c19c4d51120a49d9842f3ebe979b1373da7ce6f37dd2319212bd32e25a198
BLAKE2b-256 checksum
How to use checksums
5da733795e74fc4a8a0198b1e35f35a59dd719f0665cb611debbcf1c66610010
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/2.7.12

Release files / py_3parencryptor-1.0.9-py2.7.egg

Download URL py_3parencryptor-1.0.9-py2.7.egg
Size 9.5 kB
Tags Egg
SHA-256 checksum
How to use checksums
5ae18644472c9b67da343a1f064ac0532b7e31e11cf611a5d25a9c4d53d04ddf
BLAKE2b-256 checksum
How to use checksums
f4fb05135e37f564f651616a46e86e1542db028bd69701ad9dba445f4354c584
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/2.7.12

Release files / py_3parencryptor-1.0.9-py2-none-any.whl

Download URL py_3parencryptor-1.0.9-py2-none-any.whl
Size 6.5 kB
Tags Python 2
SHA-256 checksum
How to use checksums
4512900fa828dae881fa64e2b95d10b878c529746061937ca290208d74a8e020
BLAKE2b-256 checksum
How to use checksums
6c8fa79c119e40cf47cb60c04c28a8ff1574d932370ac85c5b8a027a0e83abed
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/2.7.12

Security for py-3parencryptor 1.0.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page