Re: [Widgets requirements]

On 12/30/06, Ed Voas <voas@yahoo-inc.com> wrote:
>
>
> The problem I see with encrypting content is that you'll need to use
> a shared secret. That secret will be in the source code of the widget
> runner. This is something that I know our security peeps would have
> an issue with. This is actually the main reason we don't have any
> true encryption in our stuff to date. Does anyone know a good way to
> pull this off with no shared secrets?


That's the aim of asymetric encryption
The emittor has a private key
Emit a public key out of that private one
And encrypt with his private key
You can decrypt with the public key
But nobody can encrypt with the public key, so nobody share the secret with
the emittor

Does this help you?

Xmlizer