4 ms·
I'm actually looking forward to seeing how the OpenSSL problem will deal with their own legacy code, compared to how the OpenBSD developers have handled it. It
by mrweasel 12y ago
I'm actually looking forward to seeing how the OpenSSL problem will deal with their own legacy code, compared to how the OpenBSD developers have handled it.
It seems that own of the only ways of dealing with the OpenSSL code is to strip out the code for a large number of, should we say "less used platforms". Is the OpenSSL developers willing to drop support for 16 bit Windows or OpenVMS?
- wmf 12y agoIs the OpenSSL developers willing to drop support for 16 bit Windows or OpenVMS? They either need to properly maintain it or drop it, and they don't have enough money to maintain it.
- jimktrains2 12y agoI just want to know who's still compiling against 16bit windows or OpenVMS. I know my world view isn't infinite, but those systems seem a bit out there.
- daxelrod 12y agoPart of my job involves writing software on OpenVMS. We actually just recently ported something that needed OpenSSL and were happy to find an up-to-date version.
- tribaal 12y agoOut of curiosity (sorry if that's offtopic), but what kind of workload are you running? Is there anything except resources that prevent you from moving to a more modern platform? Of course, "it works" is a valid argument there, too. But you seem to be writing new code, too.
- daxelrod 12y agoNo, nothing except resources is in the way of completion of a move to a more modern platform. It's coming gradually, but we can't drop everything for a year or two to devote all of our engineering resources to getting us there. OpenVMS has some really good ideas baked into the OS that we've had to reimplement or find off-the-shelf solutions for our new platform (for example a distributed key-value store (called "logicals"), a job queue system, and a clustered filesystem) but nothing so earth-shattering that it would keep us on VMS. The biggest downsides are expensive hardware (OpenVMS is designed around clusters of a few beefy boxes, rather than many commodity boxes), lack of community knowledge, and lack of new software available for the platform. (End of life is also looming: http://h71000.www7.hp.com/openvms/openvms_supportchart.html http://h71000.www7.hp.com/openvms/openvms_supportchart.html .)
- Hoff 12y agoYes, there are OpenVMS servers still around. I work with a number of them, and with various folks that are still using them in production. There are recent builds of OpenSSL for OpenVMS: http://polarhome.com/openssl/ http://polarhome.com/openssl/ http://www.openvms.org/stories.php?story=14/04/11/6422157 http://www.openvms.org/stories.php?story=14/04/11/6422157 HP's version is a bit older: http://h71000.www7.hp.com/openvms/products/ssl/ssl.html http://h71000.www7.hp.com/openvms/products/ssl/ssl.html Free OpenVMS accounts: http://deathrow.vistech.net http://deathrow.vistech.net http://decuserve.org http://decuserve.org
- dfc 12y agoOne of my favorite platform removals was support for the Cray T3E, as in the debuted in 1995, Cray Research T3E.[1,2] -/* Added for T3E, address-of fails on bit field (beckman@acl.lanl.gov) */ -#ifndef BIT_FIELD_LIMITS memcpy(&server.sin_addr.s_addr, ip, 4); -#else - memcpy(&server.sin_addr, ip, 4); -#endif [^1]: http://freshbsd.org/commit/openbsd/01f41ed5b37037b963c0de2c25a84f35390455a2 http://freshbsd.org/commit/openbsd/01f41ed5b37037b963c0de2c2... [^2]: https://en.wikipedia.org/wiki/Cray_T3E https://en.wikipedia.org/wiki/Cray_T3E