RE: argv/Argv hacks in openssl.c

The amount of time it took me to read the comment and figure out what is going on, and your time to write email explaining it, and Ted's time to chime in about the necessity of doing all this far outweighs the new code which is #ifdef VMS'd Because now main() looks really simple and bog-standar

Re: argv/Argv hacks in openssl.c

From: "Salz, Rich" > Would it work to *always* copy argv on VMS? Sure. It would also work always to copy argv[] _everywhere_. The comments explain where/when it's necessary. It made more sense to me to do the extra work where/when it's needed, rather than impose the (small?) performance pe

RE: argv/Argv hacks in openssl.c

Would it work to *always* copy argv on VMS? -- Principal Security Engineer Akamai Technologies, Cambridge, MA IM: rs...@jabber.me; Twitter: RichSalz __ OpenSSL Project http://www.openssl.org Deve

Re: argv/Argv hacks in openssl.c

From: Theodore Ts'o > Let me get this straight. We're arguing for keeping some hacks in the > source code to support OpenVMS on Alpha? (i.e., a dead OS running on > a dead architecture?) Define "dead". The vendor (HP) claims still to support it: http://h71000.www7.hp.com/index.html

Re: argv/Argv hacks in openssl.c

On Sun, Jul 13, 2014 at 12:23:07PM -0500, Steven M. Schweda wrote: > From: Richard Levitte > > > According to the comments, it sounds like HP C V7.3 ECO01 fixes the > > problems. Do I get that wrong? If I don't, it seems that HP has, in > > fact, provided a compiler without this bug. Or are yo

Re: argv/Argv hacks in openssl.c

In message <14071312230742_2021a...@antinode.info> on Sun, 13 Jul 2014 12:23:07 -0500 (CDT), "Steven M. Schweda" said: sms> From: Richard Levitte sms> sms> > According to the comments, it sounds like HP C V7.3 ECO01 fixes the sms> > problems. Do I get that wrong? If I don't, it seems that HP

Re: argv/Argv hacks in openssl.c

From: Richard Levitte > According to the comments, it sounds like HP C V7.3 ECO01 fixes the > problems. Do I get that wrong? If I don't, it seems that HP has, in > fact, provided a compiler without this bug. Or are you waiting for a > V7.4? According to the comments, "(As this was written,

Re: argv/Argv hacks in openssl.c

In message <14070515034819_2021a...@antinode.info> on Sat, 5 Jul 2014 15:03:48 -0500 (CDT), "Steven M. Schweda" said: sms> From: "Salz, Rich" sms> sms> > There's a bunch of hacks in apps/openssl.c to work around some old VMS rele= sms> > ases; the coment is dated 2011-03-22. [... blah-di-blah

RE: argv/Argv hacks in openssl.c

From: ann-i...@hotmail.com To: openssl-dev@openssl.org Subject: RE: argv/Argv hacks in openssl.c Date: Mon, 7 Jul 2014 01:15:18 +0700 ควยไร ฮะ เหี้ย From: rs...@akamai.com To: openssl-dev@openssl.org Date: Sat, 5 Jul 2014 12:45:34 -0400 Subject: argv/Argv hacks in openssl.c There’s a bunch

RE: argv/Argv hacks in openssl.c

ควยไร ฮะ เหี้ย From: rs...@akamai.com To: openssl-dev@openssl.org Date: Sat, 5 Jul 2014 12:45:34 -0400 Subject: argv/Argv hacks in openssl.c There’s a bunch of hacks in apps/openssl.c to work around some old VMS releases; the coment is dated 2011-03-22.I am going to delete it.Speak up now if

Re: argv/Argv hacks in openssl.c

From: "Salz, Rich" > Thanks for the explanation. I'll refactor it a bit, and keep it. Whew. Now that I look again, I see that there's already an apps/vms_decc_init.c, so if adding something like an apps/vms_argv64_bug.c to do the real work would improve the appareance, it'd be ok with me

RE: argv/Argv hacks in openssl.c

Steve, Thanks for the explanation. I'll refactor it a bit, and keep it. /r$ -- Principal Security Engineer Akamai Technologies, Cambridge, MA IM: rs...@jabber.me; Twitter: RichSalz __ OpenSSL Project

Re: argv/Argv hacks in openssl.c

On Sat, Jul 5, 2014 at 4:03 PM, Steven M. Schweda wrote: > From: "Salz, Rich" > > > There's a bunch of hacks in apps/openssl.c to work around some old VMS > rele= > > ases; the coment is dated 2011-03-22. > > I am going to delete it. > >Thanks for the notice. > >Why? Is your primary goa

Re: argv/Argv hacks in openssl.c

From: "Salz, Rich" > There's a bunch of hacks in apps/openssl.c to work around some old VMS rele= > ases; the coment is dated 2011-03-22. > I am going to delete it. Thanks for the notice. Why? Is your primary goal to remove all support for VMS, or only to cause defective behavior on most

argv/Argv hacks in openssl.c

There's a bunch of hacks in apps/openssl.c to work around some old VMS releases; the coment is dated 2011-03-22. I am going to delete it. Speak up now if you can justify keeping it. -- Principal Security Engineer Akamai Technologies, Cambridge, MA IM: rs...@jabber.me; Twit