| 1 |
Source: golang-github-henrybear327-proton-api-bridge |
| 2 |
Section: golang |
| 3 |
Priority: optional |
| 4 |
Maintainer: Debian Go Packaging Team <[email protected]> |
| 5 |
Uploaders: Maytham Alsudany <[email protected]> |
| 6 |
Rules-Requires-Root: no |
| 7 |
Build-Depends: |
| 8 |
debhelper-compat (= 13), |
| 9 |
dh-sequence-golang, |
| 10 |
golang-any, |
| 11 |
golang-github-henrybear327-go-proton-api-dev, |
| 12 |
golang-github-protonmail-gluon-dev, |
| 13 |
golang-github-protonmail-gopenpgp-dev, |
| 14 |
golang-github-relvacode-iso8601-dev, |
| 15 |
golang-golang-x-sync-dev, |
| 16 |
Testsuite: autopkgtest-pkg-go |
| 17 |
Standards-Version: 4.6.2 |
| 18 |
Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-henrybear327-proton-api-bridge |
| 19 |
Vcs-Git: https://salsa.debian.org/go-team/packages/golang-github-henrybear327-proton-api-bridge.git |
| 20 |
Homepage: https://github.com/henrybear327/Proton-API-Bridge |
| 21 |
XS-Go-Import-Path: github.com/henrybear327/Proton-API-Bridge |
| 22 |
|
| 23 |
Package: golang-github-henrybear327-proton-api-bridge-dev |
| 24 |
Architecture: all |
| 25 |
Multi-Arch: foreign |
| 26 |
Depends: |
| 27 |
golang-github-henrybear327-go-proton-api-dev, |
| 28 |
golang-github-protonmail-gluon-dev, |
| 29 |
golang-github-protonmail-gopenpgp-dev, |
| 30 |
golang-github-relvacode-iso8601-dev, |
| 31 |
golang-golang-x-sync-dev, |
| 32 |
${misc:Depends}, |
| 33 |
Description: third-party, open-source Proton API bridge (library) |
| 34 |
proton-go-api provides the basic building blocks of API calls and error |
| 35 |
handling, such as 429 exponential back-off, but it is pretty much just a |
| 36 |
barebone interface to the Proton API. For example, the encryption and |
| 37 |
decryption of the Proton Drive file are not provided in this library. |
| 38 |
. |
| 39 |
This codebase, Proton API Bridge, bridges the gap, so software like rclone can |
| 40 |
be built on top of this quickly. This codebase handles the intricate tasks |
| 41 |
before and after calling Proton APIs, particularly the complex encryption |
| 42 |
scheme, allowing developers to implement features for other software on top of |
| 43 |
this codebase. |
| 44 |
. |
| 45 |
Currently, only Proton Drive APIs are bridged, as we are aiming to implement a |
| 46 |
backend for rclone. |