@SSH - quick question purely out of my own curiosity...
One of the problems with any encryption utility is how well you can trust the author to (a) have written good code, and (b) not to have put a backdoor in it. Which is two of the reasons (i.e. QC and transparency) why things like
TrueCrypt have open sourced their code, and all major encryption methods have (AFAIK) published their algorithms.
As an independent developer, how do you address those concerns?
Please don't take my question as a challenge or criticism. Not being a software developer I'm interested more from a
business perspective since I'm a systems person who is professionally involved with data and signal security.
