|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I'm definitely not saying the passphrase should be stored anywhere. What I was proposing is the one row of metadata, which in case of successful decryption would lead to opened store. If the decryption wouldn't be successful, InvalidKeyException would be thrown. This wouldn't be "trash" for workaround as you say it. It'd be just metadata, encrypted with the same passphrase as the actual data. Thus you'd only need to decrypt the metadata and you'll be sure the passphrase is right. No performance bottleneck with this. It might also be in different table, as one SQLStore is complete database and not just one table. Why exactly you don't like this approach?