cyphr | : shipit : Humane encryption | Encryption library

by ropensci R Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | cyphr Summary

cyphr is a R library typically used in Security, Encryption applications. cyphr has no bugs, it has no vulnerabilities and it has low support. However cyphr has a Non-SPDX License. You can download it from GitHub.

High-level functions for supporting encryption and decryption of data from R. This allows secure storage and exchange of information, while trying to keep the encryption/decryption code from taking over your analyses. cyphr wraps the lower-level support from sodium and openssl. This package is designed to be easy to use, rather than the most secure thing (you're using R, remember - for examples of what cyphr can't protect against see jammr, rpwnd and evil.R.).

Support

Quality

Security

License

Reuse

Support

cyphr has a low active ecosystem.

It has 86 star(s) with 9 fork(s). There are 7 watchers for this library.

It had no major release in the last 6 months.

There are 3 open issues and 25 have been closed. On average issues are closed in 172 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of cyphr is current.

Quality

cyphr has 0 bugs and 0 code smells.

Security

cyphr has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

cyphr code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

cyphr has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

cyphr releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of cyphr

Get all kandi verified functions for this library.

cyphr Key Features

No Key Features are available at this moment for cyphr.

cyphr Examples and Code Snippets

No Code Snippets are available at this moment for cyphr.

Community Discussions

Trending Discussions on cyphr

How to enter key manually using R's cyphr library

Error : Failed to decrypt key as session key has changed | shinyapps.io | R

R language | sodium | cyphr | How to save and transfer a KEY

QUESTION

How to enter key manually using R's cyphr library

Asked 2021-May-31 at 02:21

Suppose I create a key using R's cyphr library

...

ANSWER

Answered 2021-May-31 at 02:21

One option is split the string at the space with strsplit, loop over the list of values, convert to raw through hexmode

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

QUESTION

Error : Failed to decrypt key as session key has changed | shinyapps.io | R

Asked 2020-Mar-13 at 08:16

Note: This (lengthy) question is a follow-up to my previous post.

I would like to achieve the encryption of data locally (local RStudio) and decrypt the encrypted data remotely (application hosted on shinyapps.io).

The first part of the code intrinsically encrypts a data-frame using a key. The second part of the code is a shiny application that decrypts the data-frame using the same key and thereby using this data-frame for authentication purposes within the application. The code works just alright on my machine.

However, it throws an error when published to shinyapps.io (cloud-based hosting service) as shown below:

1.Code for encrypting the data-frame.

...

ANSWER

Answered 2020-Mar-13 at 08:16

Reason for the issue

The problem is by design as cyphr::key_sodium creates a key which is valid, well, only for the current session. That is, it is not possible to share it across different session let alone different systems.

Hence, the problem is not at all related to shinyitself, but to the fact that you are trying to use cyphr keys across different sessions.

From the vignette:

When using key_openssl, keypair_openssl, key_sodium, or keypair_sodium we generate something that can decrypt data. The objects that are returned by these functions can encrypt and decrypt data and so it is reasonable to be concerned that if these objects were themselves saved to disk your data would be compromised.

To avoid this, cyphr does not store private or symmetric keys directly in these objects but instead encrypts the sensitive keys with a cyphr-specific session key that is regenerated each time the package is loaded. This means that the objects are practically only useful within one session, and if saved with save.image (perhaps automatically at the end of a session) the keys cannot be used to decrypt data.

Reprex of the issue

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

QUESTION

R language | sodium | cyphr | How to save and transfer a KEY

Asked 2020-Feb-28 at 14:31

I'm working on encrypting a csv. file as a local user and decrypting the same file as a remote user, using R language with the help of sodium and cyphr packages. I came across this documentation which suffices the requirement (https://www.rdocumentation.org/packages/cyphr/versions/1.0.2/topics/key_sodium). However, I face a stumbling block in saving and transferring the key to the remote user.

Adapted example from the documentation (limiting to a string instead of csv.):

...

ANSWER

Answered 2020-Feb-28 at 14:31

As for how to transmit a key to a remote user, see this Information Security Stack Exchange post.

The error comes from the fact that saveRDS does not return a value. And you have not saved anything to a file, that code line gives an error. The right way of encrypting and saving to a file would be

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

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

Vulnerabilities

No vulnerabilities reported

Install cyphr

Install cyphr from CRAN with. To install a development version from github, you can use remotes.

Support

The functions supported so far are:. However, there are bound to be more functions that could be useful to add here (e.g., readxl::read_excel). Either pass the name of the file argument to cyphr::encrypt / cyphr::decrypt as.

Find more information at: