This sounds good. What are your future plans in regards to the latest security leaks (esp. governments capacity for decryption, etc.) Encryption is still something that works, but there are a lot of “weak encryption tools” out there. How do you make sure (from your side, not the users side of password-choosing, end-point-security, etc.) yours keep up with those issues? Using Apples built-in-crypto can be a security issue as well for example. And: Can you guarantee that there is no backdoor in your Software (as it is not open source)? Thank you Very Much.
What are your future plans in regards to the latest security leaks (esp. governments capacity for decryption, etc.)
Barring unforeseen events, you should (hopefully) see something new before the year is out. It will be open source.
How do you make sure (from your side, not the users side of password-choosing, end-point-security, etc.) yours keep up with those issues? Using Apples built-in-crypto can be a security issue as well for example. And: Can you guarantee that there is no backdoor in your Software (as it is not open source)?
These are excellent questions. Please have a look at all of the posts in this thread, which contains (I believe) all of the answers to your questions.
This sounds good. What are your future plans in regards to the latest security leaks (esp. governments capacity for decryption, etc.) Encryption is still something that works, but there are a lot of “weak encryption tools” out there. How do you make sure (from your side, not the users side of password-choosing, end-point-security, etc.) yours keep up with those issues? Using Apples built-in-crypto can be a security issue as well for example. And: Can you guarantee that there is no backdoor in your Software (as it is not open source)? Thank you Very Much.
Hi Dolo, thanks for your questions!
What are your future plans in regards to the latest security leaks (esp. governments capacity for decryption, etc.)
Barring unforeseen events, you should (hopefully) see something new before the year is out. It will be open source.
How do you make sure (from your side, not the users side of password-choosing, end-point-security, etc.) yours keep up with those issues? Using Apples built-in-crypto can be a security issue as well for example. And: Can you guarantee that there is no backdoor in your Software (as it is not open source)?
These are excellent questions. Please have a look at all of the posts in this thread, which contains (I believe) all of the answers to your questions.
Specifically, these two replies I made: one, two.