Steffen Jaeckel

Looks like there went something wrong while transferring the file. If I use the original file on the device where the backup is created, it seems to work.

I've reopened this issue as I'm not sure where the problem lies and I'd like to have your opinion on it. I've created the backup and transferred the file via...

How can I create one?

The only thing that is printed on failure in the log is ``` directory not found: /storage/emulated/0/Quicksy/Backup directory not found: /storage/emulated/0/Conversations/Backup ```

Yes, Storage permission is set to "Allow". I've also tried to add an attachment to a message via the same logic and that worked.

> Steps to reproduce: > > ``` > Download wolfssl-5.3.0-gplv3-fips-ready.zip from www.wolfssl.com/download/ > update wolfssl-5.3.0-gplv3-fips-ready/wolfcrypt/test/test.c with the test.c from this PR > open wolfssl-5.3.0-gplv3-fips-ready/IDE/WIN10/wolfssl-fips.sln in VS > build and run...

> how can I (easily) get a patchset for this (like the link provided in the email notification on the very 1st comment) If you really need a patch file...

This will only be merged right before the 2.0.0 release, so there's no need to rebase now.

As already discussed via mail I think having to implement this outside of the library would be a bit cumbersome and performance wise really bad and therefor we could add...

TBH I had the impression for already a while that the tuning doesn't really do what it promises... until now I only suspected it, but check out yourself... I executed...