django-encrypted-fields | Django Model Field classes that are encrypted using Keyczar | REST library

 by   defrex Python Version: 1.1.2 License: MIT

kandi X-RAY | django-encrypted-fields Summary

kandi X-RAY | django-encrypted-fields Summary

django-encrypted-fields is a Python library typically used in Web Services, REST applications. django-encrypted-fields has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can install using 'pip install django-encrypted-fields' or download it from GitHub, PyPI.

This is a collection of Django Model Field classes that are encrypted using Keyczar. Keyczar is a crypto library that exposes a simple API by letting the user set things like the algorithm and key size right in the keyfile. It also provides for things like expiring old keys and cycling in new ones. Create a basic keyczar keyset. AES-256 in this case. Use your model as normal and your data will be encrypted in the database. Warning: Once the data is encrypted, it can no longer to used to query or sort. In SQL, these will all look like text fields with random noise in them (which is what you want). Currently build in and unit-tested fields. They have the same APIs as their non-encrypted counterparts. Making new fields is easy! Django Encrypted Fields uses a handy mixin to make upgrading pre-existing fields quite easy. Please report an issues you encounter when trying this, since I've only tested it with the fields above.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              django-encrypted-fields has a low active ecosystem.
              It has 185 star(s) with 55 fork(s). There are 7 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 5 open issues and 18 have been closed. On average issues are closed in 66 days. There are 3 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of django-encrypted-fields is 1.1.2

            kandi-Quality Quality

              django-encrypted-fields has no bugs reported.

            kandi-Security Security

              django-encrypted-fields has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

            kandi-License License

              django-encrypted-fields is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              django-encrypted-fields releases are available to install and integrate.
              Deployable package is available in PyPI.
              Build file is available. You can build the component from source.
              Installation instructions are not available. Examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi has reviewed django-encrypted-fields and discovered the below as its top functions. This is intended to give you an instant insight into django-encrypted-fields implemented functionality, and help decide if they suit your requirements.
            • Get database value
            • Encrypt the value
            • Get the cookiepter
            • Convert database value to python value
            • Decrypt the value
            Get all kandi verified functions for this library.

            django-encrypted-fields Key Features

            No Key Features are available at this moment for django-encrypted-fields.

            django-encrypted-fields Examples and Code Snippets

            No Code Snippets are available at this moment for django-encrypted-fields.

            Community Discussions

            Trending Discussions on django-encrypted-fields

            QUESTION

            Django Encrypted Fields Keys and Gitignore
            Asked 2018-Aug-03 at 16:35

            I'm working on a Django project where one of my models has a field that needs to be encrypted. I'm using django-encrypted-fields for the EncryptedCharField for my model.

            As part of the setup, I have to create some keys for encryption. Since I'm working on my local machine, but will be deploying on AWS (both using the same remote database), I'm wondering if the fieldkeys directory, which contains the keys, should be included in my .gitignore file, or if all machines should use the same keys.

            Thanks.

            ...

            ANSWER

            Answered 2018-Aug-03 at 16:35

            I'm wondering if the fieldkeys directory, which contains the keys, should be included in my .gitignore file,

            Ideally no, in that those files should not be in the Git repo folder in the first place (so no need to add them to a .gitignore file).
            Having them inside a Git repo is too dangerous. Even ignored, they can still be added with a git add -f

            Or if all machines should use the same keys.

            No either: the best practice remains to have a dedicated key by environment, which makes a key revocation easy and won't break all the other environments.

            You need to have a way to reference your key (stored separately outside of the git repo).

            Semi-related: "New AWS Encryption SDK for Python Simplifies Multiple Master Key Encryption".

            Source https://stackoverflow.com/questions/49353038

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install django-encrypted-fields

            You can install using 'pip install django-encrypted-fields' or download it from GitHub, PyPI.
            You can use django-encrypted-fields like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            Install
          • PyPI

            pip install django-encrypted-fields

          • CLONE
          • HTTPS

            https://github.com/defrex/django-encrypted-fields.git

          • CLI

            gh repo clone defrex/django-encrypted-fields

          • sshUrl

            git@github.com:defrex/django-encrypted-fields.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link