Large strings cannot be stored in securestorage, and must be chunked. #9

Asday · 2019-06-19T15:28:43Z

Size limit for a value is 2048 bytes. An attempt to store larger values may fail. Currently, we print a warning when the limit is reached, but we will throw an error starting from SDK 35.

https://docs.expo.io/versions/latest/sdk/securestore/

Cretezy · 2019-06-19T17:44:18Z

This is definitely going to be an issue. I will rework this to use AES to allow large blobs soon. Thank you for rising this issue

Asday · 2019-06-19T17:54:37Z

I was thinking of a much cruder solution:

in setItem(), store the size of value / 2048 as key, then chunk value to 2048, and store as key[x];
in getItem(), get the size of the value from key, then retrieve that many chunks, and concatenate them;
in removeItem(), get the size of the value from key, then delete key[0-n].

Cretezy · 2019-06-19T19:06:58Z

I don't think chunking is the right solution, it would create a lot of overhead and would be must less efficient

Asday · 2019-06-20T06:37:02Z

I'm not sure implementing one's own encryption would align with the name of the repo - encrypted by expo or by us, storing large amounts per key in securestore isn't possible.

I may be misunderstanding.

Cretezy · 2019-07-10T06:01:54Z

The usual solution for storing encrypted data on mobile is this (see other libraries implementing the same pattern):

Create AES key, store it in the secure OS store (this library stores data in the secure OS store, just need to store the AES key instead of the data)
When saving data, encrypt it with said key and save it to disk (it is encrypted, and disk has no file limit)
When fetching data, fetch the AES key from the secure OS store, then read disk data and decrypt it

I will create an extension to this package when I have time to allow for this pattern

leviathanbeak · 2019-07-18T10:43:20Z

@Cretezy so should we just wait and ignore the warning for now or ?

Asday · 2019-07-18T11:20:14Z

Depends on your case and environment. You should get an idea of how much stored breaks your intended audience's environments, and how much you're likely to store at most.

If it's looking risky for you, consider helping @Cretezy out with his describe AES solution, or switching to a different storage solution and sacrificing the security.

thargenediad · 2019-07-31T16:32:54Z

We eagerly await the new extension, @Cretezy!

istvan-szilagyi · 2019-08-02T07:19:49Z

We couldn't wait anymore for the new extension, so we created our own package which works as @Cretezy told it should (so big credits for him on the idea).

https://github.com/neverdull-agency/expo-unlimited-secure-store

Cretezy · 2019-08-02T14:34:19Z

@istvan-szilagyi This is great! I'm sorry for being a little bogged down recently.

If you'd like, create a PR with the information in the README.

@Cretezy

This commit creates a series of 3 cryptography utilities used to encrypt the data that will be stored by the application as part of its content. Everytime we want to store an information, the idea is to generate a random encryption key that will be stored part of the SecureStore while the encrypted information using this generated key will be stored in the regular FileSystem. This solution will allow us to not be blocked by the low capacity of the SecureStore allowed on iOS and Android. Part of this commit, we find the `generateEncryptionKey` utility creating a random encryption key having the requested amount of chars. We also have an `encrypt` utility randomly generating a key and using the generated key to encrypt the requested message. And finally we have a `decrypt` key using the provided key to decrypt a provided message. These utilities are based on the work made by @neverdull-agency to implement an unlimited secured expo storage, following the message by @Cretezy in the issue Cretezy/redux-persist-expo-securestore#9.

@Cretezy

This commit creates a series of 3 cryptography utilities used to encrypt the data that will be stored by the application as part of its content. Everytime we want to store an information, the idea is to generate a random encryption key that will be stored part of the SecureStore while the encrypted information using this generated key will be stored in the regular FileSystem. This solution will allow us to not be blocked by the low capacity of the SecureStore allowed on iOS and Android. Part of this commit, we find the `generateEncryptionKey` utility creating a random encryption key having the requested amount of chars. We also have an `encrypt` utility randomly generating a key and using the generated key to encrypt the requested message. And finally we have a `decrypt` key using the provided key to decrypt a provided message. These utilities are based on the work made by @neverdull-agency to implement an unlimited secured expo storage, following the message by @Cretezy in the issue Cretezy/redux-persist-expo-securestore#9.

uxxman · 2020-07-27T16:45:30Z

any update on this?

xmflsct · 2021-01-22T22:55:36Z

Thank you @istvan-szilagyi ! I have switched to use your library.

Cretezy/redux-persist-expo-securestore#9

bleedingAyush · 2021-09-29T04:47:15Z

Guys, you don't need to use this package at all. Just go to the project's main repository and copy the two files index.d.ts and index.js and then make a folder name redux-persist-exposecurestore in and then use it.

Asday · 2021-09-29T05:02:32Z

@Ayush6543 that is exactly using this package, you're just cutting out the NPM step (and taking the responsibility of transpilation).

Also that does absolutely nothing to fix the issue.

bleedingAyush · 2021-10-03T02:03:51Z

@Ayush6543 that is exactly using this package, you're just cutting out the NPM step (and taking the responsibility of transpilation).

What is transpilation?

abdul-megadraws · 2023-10-20T07:37:22Z

Install:
@react-native-async-storage/async-storage

Instead of
expo-secure-store

Hope it will clear warning message! Will solve issue.

…eStore is larger than 2048 bytes. An attempt to store such a value will throw an error in SDK 35." warning. Issue Cretezy#9

Cretezy added the bug Something isn't working label Jun 19, 2019

Asday mentioned this issue Jun 20, 2019

Import SecureStore from expo-secure-store instead. #10

Closed

xmflsct added a commit to tooot-app/app that referenced this issue Jan 23, 2021

Fix size limit for storing avatar

aa467f6

Cretezy/redux-persist-expo-securestore#9

AnantTiwari001 mentioned this issue Sep 12, 2024

chucking down key into 2000 bytes to avoid #26

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Large strings cannot be stored in securestorage, and must be chunked. #9

Large strings cannot be stored in securestorage, and must be chunked. #9

Asday commented Jun 19, 2019 •

edited

Loading

Cretezy commented Jun 19, 2019

Asday commented Jun 19, 2019

Cretezy commented Jun 19, 2019

Asday commented Jun 20, 2019

Cretezy commented Jul 10, 2019

leviathanbeak commented Jul 18, 2019

Asday commented Jul 18, 2019

thargenediad commented Jul 31, 2019

istvan-szilagyi commented Aug 2, 2019

Cretezy commented Aug 2, 2019

uxxman commented Jul 27, 2020

xmflsct commented Jan 22, 2021

bleedingAyush commented Sep 29, 2021

Asday commented Sep 29, 2021

bleedingAyush commented Oct 3, 2021

abdul-megadraws commented Oct 20, 2023

Large strings cannot be stored in securestorage, and must be chunked. #9

Large strings cannot be stored in securestorage, and must be chunked. #9

Comments

Asday commented Jun 19, 2019 • edited Loading

Cretezy commented Jun 19, 2019

Asday commented Jun 19, 2019

Cretezy commented Jun 19, 2019

Asday commented Jun 20, 2019

Cretezy commented Jul 10, 2019

leviathanbeak commented Jul 18, 2019

Asday commented Jul 18, 2019

thargenediad commented Jul 31, 2019

istvan-szilagyi commented Aug 2, 2019

Cretezy commented Aug 2, 2019

uxxman commented Jul 27, 2020

xmflsct commented Jan 22, 2021

bleedingAyush commented Sep 29, 2021

Asday commented Sep 29, 2021

bleedingAyush commented Oct 3, 2021

abdul-megadraws commented Oct 20, 2023

Asday commented Jun 19, 2019 •

edited

Loading