> Clients must trust their server (or they should find another server). > This means that clients are not currently able to do signing or > encryption.
While it's true that client signatures are not quite as critical as they are in e-mail, there is still the possibility for an account being compromised. But, since your private key is not hosted with your account, but on your local computer (or in a smart card), a signature would be an additional level of authentication and non-repudiation that cannot be provided by the server alone. In personal communication (to friends or family) this is not needed, but in business, this will in many cases be required (as well as in Govt, or DoD settings). Wave will not be able to replace e-mail until is supports client signature and content encryption. > I personally think one way to (ab)use the current architecture is: > > 1. Run your own federated server > > 2. That means you'll need a certificate for your server > > 3. If you want more than signing (such as encryption), you can use the > type of the blip to specify that the data is not "plain text." The nice thing about the wave architecture is that it's not very easy to abuse. Servers that generate bad content (spam, fraud etc..) will be blacklisted or shut down. And servers that fail to police their subscribers will be blacklisted. It is possible to impersonate a server, but only if the server is using a self-signed cert or is using a CA like StartCom AND their DNS records can be forged or altered (either via spoofing or more likely a compromised registration account). -Tad --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
