× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



SSL was first added to the operating system in (IIRC) v4r3. And, frankly, was so buggy it was hard to use... there were major changes from v4r3 -> v4r4 -> v4r5 -> v5r1. Then the changes cooled down a bit.

I don't think I'd even attempt to code SSL on v4r4 (much less v4r2!).

I suggest coding it to the v5r1 level, and tell customers that the minimum release for SSL support is v5r1. You'd be doing them a disservice, quite frankly, to try to make SSL work earlier than that. If for no other reason than because the SSL standards available back then aren't considered secure anymore today.

On 11/12/2010 3:48 PM, James H. H. Lampert wrote:
Scott Klement wrote:
You have the source code, you can make it do anything you want.

Quite true.

But I'm afraid that what I know about coding for SSL, and a buck, might
get you a cup of coffee.

Then again, it's now rather painfully obvious that the first thing I'm
going to have to "make it do" is compile on a V4R4 box with a V4R2
compiler. Because while we can compile "/free" on our V6 box, doing so
is utterly meaningless in terms of something we can actually release,
because we test on (and advertise compatibility all the way back to) V4R4.

--
JHHL
(Who fervently believes that when a programming language's most basic
syntactic construction is changed deeply, fundamentally, and beyond
recognition, it becomes a new language, and should have a new name.)


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.