Re: [sqlite] SEE encryption password

> On May 6, 2019, at 2:56 PM, Scott Doctor wrote: > > Here is a suggestion. You can select between decimal and hexadecimal output. > > https://nousrandom.net/randominteger/index.html > Random data generated using some unspecified algorithm,

Re: [sqlite] SEE encryption password

Here is a suggestion. You can select between decimal and hexadecimal output. https://nousrandom.net/randominteger/index.html - Scott Doctor sc...@scottdoctor.com - On 5/6/2019 13:20, Jens Alfke wrote: On May 5, 2019, at 11:04 PM,

Re: [sqlite] SEE encryption password

> On May 5, 2019, at 11:04 PM, Birajendu Sahu wrote: > > I would like to generate a device specific key upon installation of the > application. Same time I don't want to save the key in device memory too. For AES256, just generate 32 bytes (256 bits) of securely random data and use that as

[sqlite] SEE encryption password

Hi Folks, I am implementing SEE for my multi platform application which supports macOS, Windows and Android. I would like to understand what the best way to provide a strong password for SEE. I would like to generate a device specific key upon installation of the application. Same time I don't