The high level details of the encryption I'm using is:
- AndroidKeyStore create/store RSA key
- AES key is created and wrapped with RSA/ECB/PKCS1Padding
- Encrypted AES is saved to disk.
- Data is encrypted with AES/GCM/NoPadding and saved to disk.
- Every encryption operation generates a new initialization vector from the platform secure random. Those are also saved to disk with their data.
The algorithm/transformation used are limited by the platform.
There are known issues on the AndroidKeyStore forgetting keys and I would like to save a known "lorem ipsum" data encrypted on first run. This known data would later be used during initialization to check the consistency of the keys and provide proper status for the system.
So my question: is it safe to store this known hard-coded value next to the real values, or with that I'm leaking everything and making it easy for someone to decrypt the real values?