> You can't imagine anyone having any use for this device? No home users would be able to use this - and that is who they seem to be targeting their marketing

> You can't imagine anyone having any use for this device? No home users would be able to use this - and that is who they seem to be targeting their marketing towards. > What's hilarious about the inherent impossibility of secure closed source software? That you can't get around using closed source software/hardware. You have to put trust into closed source software at some point - do you drive a car? > You "hope" Chrome is "based on" Chromium---what relevance does this hope have for a factual discussion? Like I said before - relating to security I hope certain systems like OpenSSL and CAs are not compromised. I'm a realistic person and I assume they aren't. Do you check and pin every SSL certificate you come across? How do you know that you don't have a bad CA certificate in your store right now? I'm not saying I have irrevocable proof that Chrome's code is a fork of Chromium - but there are enough indications that suggest this[1]. I'm not saying you should or shouldn't use Chrome - go use lynx if that makes you feel better. > And what about Microsoft and Apple? What about them? I'm not saying they are perfect - but I'm also not totally paranoid that I'm going to refuse them on the basis that I can't see their code. > And the many well-reasoned criticisms of browser-based encryption? That's a loaded question if I ever saw one. Web applications like cryptocat are bad because they send the keys with Javascript. I'm no security expert - but something like this seems reasonable to me in the context of the use case of this box [2]. [1] - https://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoogleChrome https://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoo... [2] - https://encrypt.to/ https://encrypt.to/