Basically fork and take over management of that fork completely going forward, or to accept the changes and make the best of them. Sometimes upstream libraries have changed and the zimbra system has a choice to diverge from the upstream. I get the feeling we are a tiny minority with this issue because of our prior deployment choices. Supporting multiple certs, based on internal/external access would be nice, but if just a few installations have the issue, it is hard to justify the development cost for that. Not checking that certs match the server is a huge security issue (lots of systems have been caught not doing it like Apple), so enabling it is good, even if it is inconvenient for me and you now. After all, this is why we have test systems and run test migrations, right? While I don't know the real reason for this change, there are many valid reasons it can happen, even if it is inconvenient.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |