SSL authentication requirements(?)
Jim Fulton <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Message-ID | <CAPDm-FigRfQ6BY65-j-J1QF8BwNmsNEpqLtDgeVY8Tkm28fc+A@mail.gmail.com> |
(Meta comment, My statements should be read as questions, and my questions shouldn't be read as arguments. I'm trying to work out the use cases here.) I conclude(/propose) from this discussion (and thinking about it :)) that it only makes sense to use SSL with ZEO if **both** the client and server are authenticated. Initially ======== - The client can authenticate the server in 2 ways: - By having the server(s) ca/cert(s). - By checking a signed server cert and checking for a host name match. - The server can only authenticate the client using given CAs. Therefore, initially, the server will require that CAs be provided. Later ======= We might come up with other schemes, like: - allowing clients to authenticate via user names and passwords over the SSL connection. - Checking cert data (e.g. subject/organizationName) of signed client certs. Thoughts? Jim -- Jim Fulton http://jimfulton.info -- You received this message because you are subscribed to the Google Groups "zodb" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.