21–30 of 217 posts
Terrible name.
Agreed. One of the biggest issues with security-conscious systems is that people don't want to be seen as using something that only "people with something to hide" would be using. The average American watches a show like SVU and learns that TOR is how kiddie porn is traded, not that it is how dissidents in Iran or Russia communicate with Journalists. They hear about the "darknet" and assume that that is where illegal…
As much as I hate promotion emails, I do hope they make sure that companies can still send mass "dark mails" securely, rather than sending the one by one...
Wait wait wait! Requiring very strong encryption may help make spam email computationally infeasible. That alone might be worth it!
Earlier quoted context omitted.
Wait wait wait! Requiring very strong encryption may help make spam email computationally infeasible. That alone might be worth it!
I thought even extremely strong encryption was computationally quite light- it's cracking the crypto that takes computing muscle.
The second is their approach. Overcoming the install base of current email, no matter how much better your new offering, is practically impossible. So instead secure layers on top of existing email is your only feasible option.
Anyone gone through the checklist yet? http://craphound.com/spamsolutions.txt
Terrible name.
A quick search shows SecureMail and PrivateMail are commercially used, but LockedMail and SignedMail aren't.
I don't think it'd be too late to (eventually?) do a rebrand/cobrand for the product, especially if someone comes up w/ something particularly good. I think something that even a slight bit of spitballing would turn up something much better.
Some thoughts on naming:
* If the first word ends in e like securemail/privatemail you actually get email in the word
* something that could be shortened like email, but will connote secure sending - "send me that via pmail/smail"
* something that has familiar connotations of privacy/sealed delivery (registered mail?) or something might work as well
I'm really interested in their solution for solving metadata leakage. I just looked over the SCIMP white paper, and it didn't mention anything about metadata.