replace shared_preferences with something suitable for sensitive data

[jossef]

shared_preferences is not the best practice for storing sensitive data. use something else

[ghost]

I would recomend Flutter Secure Storage for this, though the downside would be: wrapper for emulating and injecting for Android and iOs for tests and other things.

[jossef]

@RickStanley thanks. Would you like to PR this change?

[hereabdulla]

will this helps??
https://pub.dev/packages/encrypted_shared_preferences

[ianmaciel]

I would recomend Flutter Secure Storage for this, though the downside would be: wrapper for emulating and injecting for Android and iOs for tests and other things.

There is a downside: Flutter Secure Storage works only on Android iOS and Linux. Windows, macOS and Web won't be supported.

[sehnryr]

Hive is cross-platform and has strong encryption built in.

Closing because #58 fixes this issue and implements hive via stash_hive.

[LightInn]

Look like storing sensitive data in cookies is mainly a bad practice.
I think if the devs would like to store sensitive data, it's not a "requests" issue.

[sehnryr]

As @LightIn-death said, it is a bad practice to store sensitive data like passwords, SSN or even credit card numbers in cookies. The possibility where there are sensitive data in the cookie should not concern requests but rather the server that sends you this data.

But there still should be an option to encrypt the data as hive already implements it. #63 will permit that by allowing the end user to chose between using requests out of the box or initializing it with an encryption key.

I've reopened this issue since my previous implementation of stash_hive in #58 did not feature the said encryption by default but it will be fixed with #63.