[](https://travis-ci.org/Solution4Future/crypto-allauth)
[](https://requires.io/github/Solution4Future/crypto-allauth/requirements/?branch=master)
[](https://pypi.python.org/pypi/crypto-allauth)
[](https://gitter.im/solution4future/crypto-allauth?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
(DISCLAIMER! This software is early alpha and doesn't have tests yet so you are using it on your own)
Crypto-allauth is a library that adds support for some advanced login methods.
It was first drafted at the TREZOR 2 Hackathon in Prague.
Right now you can only use Trezor but plans are to support other hardware encryption solutions.
## Installation
```sh
$ pip install crypto-allauth
```
```py
INSTALLED_APPS = {
...
'allauth',
'allauth.account',
'allauth.socialaccount',
...
'crypto_allauth.providers.trezor',
...
}
```
And you're all set up.
For the "Login with TREZOR" button to work properly you either need a Chrome plugin or a trezor-bridge daemon. Go to [satoshilabs.com/trezor](http://satoshilabs.com/trezor/) to learn more.
## Roadmap
- U2F support (Yubikey and others)
- Offline Trezor support
- Keybase support
## Final notes
Feel free to create pull requests.
If you feel generous you can donate: [1AnrshDKmzRU57GTNJ2ki1bTKK45NDd2Dn](http://i.imgur.com/hlhWwOO.png)
Metadata
Release files for crypto-allauth 0.0.5
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 |
|---|---|---|---|---|
| crypto-allauth-0.0.5.tar.gz | 18.1 kB | Without provenance | Details for crypto-allauth-0.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| crypto_allauth-0.0.5-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for crypto_allauth-0.0.5-py2.py3-none-any.whl |
Total release size: 34.9 kB
Release files / crypto-allauth-0.0.5.tar.gz
| Download URL | crypto-allauth-0.0.5.tar.gz |
|---|---|
| Size | 18.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
09391622424a15066ab3e4acd54ec2c5f8d0caa39f7f8f1ead9c227b5130507a
|
|
BLAKE2b-256 checksum How to use checksums |
72df22fbaa21891ebdba576501d42b945ceb76bedbb04f64707a7a797e1fb313
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / crypto_allauth-0.0.5-py2.py3-none-any.whl
| Download URL | crypto_allauth-0.0.5-py2.py3-none-any.whl |
|---|---|
| Size | 16.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
397eaa71beb83374caab396a21a61bb3437eed24ed2a065fba259e51d0e780d9
|
|
BLAKE2b-256 checksum How to use checksums |
122cd61793cabaa62db8011d21f241ba4da1b2832437aa3d5544bf9d5dda87fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for crypto-allauth 0.0.5
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.