Solution

[Alaric Dailey]

ok maybe I throw out my idea for solving these problems.
 
1. require SSL for any data transfer from IdP to RP ( assuming data isn't
going the other way)
2. sign or encrypt the logon token (however or whereever it is stored)
3. expire the logon after a certain period of time (  )
4. require ssl for IdPs for logon pages etc...
5. Heavily recommend that IdP's use

*	DNSSec
*	Salted passwords with strong hashing algos (ie NOT MD5 or SHA1)
*	locked down systems (patches, AV, firewalls, etc)

 
Thus RP's do not require an SSL cert, and data can be trusted, and it could
be proven that it has not been modified.
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20061023/3288c2be/attachment-0002.htm>