> If what I understand from our zOS people is correct, it ISN'T > that simple. It is my understanding that the SSL support on > zOS is done using USS (Unix system services). Since the VM > implementation of unix services is far behind zOS (of > necessity: forking, etc is almost impossible under VM > without LOTS of CP work that would, more than likely, break > lots of things we depend upon), it is probably impossible to > port the zOS SSL to VM.
I would agree. I'd rather see IBM spend their money on other things. I really don't want to see z/OS TCPIP welded into a VM context -- that would be even uglier than the current setup. > This is also the reason (as well as > the lack of customer request) why there is only a VERY > limited Java for VM. Actually, Java for VM has been withdrawn from marketing. IBM no longer support a Java interpreter for CMS. > However, you can do some of what you want > yourself: remember VM is the original open source operating > system, and what you would need to see in order to implement > certificate management, etc., should be available in one form > or another. Yes, they're in the source part of the SSLSERV RPM. There needs to be some thought put into how they should behave, though, and the IBM developers for this stuff would benefit from some conversation on Linux conventions and appliance configuration management. Perhaps this list could provide that discussion. -- db
