On 09/07/2013 12:51 AM, Andy Isaacson wrote: > Also please provide design documents for how you plan to keep it > "private" and "secure". -andy
Defining terms also helps a lot. Define encrypted -- what protocols are you using? Is Places based on established technology or new research? Do you offer perfect forward secrecy, and if so, how are you defining *that*? Why should people trust a cloud-based system rather than keeping files encrypted on a USB stick? Why should people trust *your* cloud-based system, rather than someone like Least Authority? If it's free, what's your business model? I like and use lots of closed-source software, and am totally okay with being pitched on new stuff. ~But~ a lot of these companies coming out seem to target an interesting market: people who know enough to be interested in security, but don't know enough about security that they overlook the total absence of details. This is a market that nearly every company targets, so I'm not trying to single Ansamb out, but in an arena that is so marked by bad providers, transparency is a serious asset. ~Griffin -- "Cypherpunks write code not flame wars." --Jurre van Bergen #Foucault / PGP: 0xAE792C97 / OTR: [email protected] My posts are my own, not my employer's. -- Liberationtech is a public list whose archives are searchable on Google. Violations of list guidelines will get you moderated: https://mailman.stanford.edu/mailman/listinfo/liberationtech. Unsubscribe, change to digest, or change password by emailing moderator at [email protected].
