On Friday, 11/11/2005 at 10:31 EST, Paul Goodwin <[EMAIL PROTECTED]> wrote: > Isn't that a bit of a red herring? I may have missed something earlier, > but why couldn't the effort that went in to writing it in the linux > environment been spent on a native implementation instead?
We chose to use the IBM Global Security Kit (aka GSKit). It is proven technology, but it is not available or supported (by the people who maintain it) for CMS. It is, however, available for Linux on zSeries. The original plan was to include a copy of Linux to provide the "native" implementation. But this was in the Before Times, during the Age of Innocence. One or two things have happened since then, eh? We welcome individual and user group requirements against the SSL server or the security characteristics of z/VM in general. To open a requirement, we prefer, in order: 1. Requirements from user groups that represent the considered interests of a group of customers 2. Individual requirements opened through your IBM rep or IBM Business Partner 3. Individual requirements opened through the Support Center. Because the Support Center's primary job is to solve problems, not handle requirements, I would ask that you try to use #1 or #2 first. All of the requirements end up in the same place and are handled by the same process. As has been noted elsewhere, posting here is even easier, but it isn't the same as an Official Requirement. If a rep or BP seems confused by your request, you may need to whisper the magic phrase "FITS database". This *should* trigger certain chemical changes which will activate the stored memory engram. Alan Altmark z/VM Development IBM Endicott
