p2pc-secure
Secure P2P-style file transfer via intermediate storage for NAT-restricted Linux systems.
Features
- Local Encryption: AES-256-GCM (authenticated encryption).
- Multiple Providers:
Litterbox(default),File.io,PixelDrain, and Custom Relays. - Visual Progress: Real-time progress bar for uploads/downloads.
- Improved UX: Visual ANSI colors, ASCII banners, and automatic command generation for recipients.
Installation
Linux
./install.sh
Windows
install.bat
Usage
Send a file
p2pc-secure send <file_path> [--password <pass>] [--provider <name>]
Supported providers:
litterbox(default): 1GB limit. Files expire automatically after 1 hour (no manual delete).file.io: 2GB limit. Files are automatically deleted after the first download.pixeldrain: 5GB+ limit. Files expire after 30 days of inactivity.
Custom Relay
If you have your own server that can open ports, you can use it as a relay:
p2pc-secure send <file> --relay-url https://your-relay-server.com/upload
The relay should accept a POST request with the file and return the download URL as plain text.
Receive a file
p2pc-secure receive <url> --password <pass> [--output <path>]
Security
- All files are encrypted locally with AES-256-GCM before upload.
- The intermediate storage server never sees the plaintext data.
- Key derivation uses PBKDF2 with a unique salt.
Metadata
Release files for p2pc-secure 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| p2pc_secure-1.2.0.tar.gz | 9.6 kB | Without provenance | Details for p2pc_secure-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| p2pc_secure-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for p2pc_secure-1.2.0-py3-none-any.whl |
Total release size: 20.4 kB
Release files / p2pc_secure-1.2.0.tar.gz
| Download URL | p2pc_secure-1.2.0.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4cf692ce55762a72de68f99fe58cfcac3b8d9dab8012637e1c2b5247c01e7ed4
|
|
BLAKE2b-256 checksum How to use checksums |
edfabc86218c7eb140c3b4d816066b34140aaa8209be6c05352fe29ad4fadbdc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / p2pc_secure-1.2.0-py3-none-any.whl
| Download URL | p2pc_secure-1.2.0-py3-none-any.whl |
|---|---|
| Size | 10.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
179f1bff1204a56959d9e74938897824a288627295a777ecf21fee493e5229eb
|
|
BLAKE2b-256 checksum How to use checksums |
e1c022fe3387e1b2ae8b703840952b774b098269490efcb40e155c03471e8e19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for p2pc-secure 1.2.0
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.