From: "Stephen Henson via RT"
> Thanks for the report. Is there some way you can generate diff files in a=
> more
> standard form? [...]
Date: Wed, 12 Aug 2009 14:05:10 -0500 (CDT)
From: sms@antinode-info (Steven M. Schweda)
Subject: Re: OpenSSL 1.0.0 beta3 release v. V
NINGS+ OPT_TEST
+$ ENDIF
$ IF CCDISABLEWARNINGS .EQS. ""
$ THEN
$ CC4DISABLEWARNINGS = "DOLLARID"
I don't have one, so I haven't actually tested this change using a
compiler which accepts MAYLOSEDATA3, but it looks plausible (to me).
1.0.2-be
where.
These are all Informational ("-I-") complaints, so they cause less
trouble than a real warning ("-W-").
Steven M. Schweda sms@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
___
ected by it in the future will be able to find easily the (hard-won)
solution after you discard it.
------------
Steven M. Schweda sms@antinode-info
38
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
still has the defect. I suspect
that I'm not alone. (But what do I know?)
------------
Steven M. Schweda sms@antinode-info
382 South Warwick Stre
ining support for VMS is not a complete waste of time. But what
do I know?
------------
Steven M. Schweda sms@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
_
he
(small?) performance penalty where/when it's not needed, but what do I
know?
------------
Steven M. Schweda sms@antinode-info
382 South Warwick Street(+1) 651-699-9818
UNCTIONS referenced
in symbol vector option
[...]
but I haven't investigated that one. I haven't yet tried 1.0.0n,
either, but complete success there would be amazing, too.
Steve
ld probably be persuaded, but it might take a few days.
------------
Steven M. Schweda sms@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
__
OpenSSL Project
From: Richard Levitte
> There is some similar package for Perl, isn't there? Is that very
> much of a pain? [...]
I expect it to be one more thing which many people won't have. I
seem to have a Compaq/HP-sourced v5.8.6 ("Compiled at Mar 6 2008
06:07:12"), and newer stuff is probably avail
PENIN, error opening openssl:*.h as input
-RMS-F-FNM, error in file name
%MMS-F-ABORT, For target INSTALL_DEV, CLI returned abort status: %X1067109C.
ALP $
I haven't yet looked into that one.
Things seem to be improved, but not yet perfect.
--
7;s not the most elegant
> coding)
I'll see if I can work up some ambition. Before it died, the
installation procedure seemed to create a new/strange/bad directory for
the header files:
Directory ALP$DKC100:[UTILITY.SOURCE.OPENSSL.1_1_0-pre3.include.openssl]
aes.h;1
kard Development Company, L
.P.
ALP $ cc /version
HP C V7.3-010 on OpenVMS Alpha V8.4
(I haven't verified it yet, but I believe that the "-010" compiler,
recently made available to us lowly hobbyists, fixes the 64-bit argv[]
NULL-termination problems on Alpha.)
n place hurt in any way?
It'll waste a little time, but not enough to matter. Probably safer
to leave it in there until the newer compiler diffuses more. A recent
posting in comp.os.vms said:
$ cc /version
HP C V7.3-009 on OpenVMS Alpha V8.3
so it's clearly not yet re
as I was assembling this message.
More/less/different quotation again?
--------
Steven M. Schweda sms@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
--
openssl-
ening
SYS$SYSDEVICE:[UTILITY.SOURCE.OPENSSL.OPENSSL-1_0_0B.ALPHA.CRYPTO]OPENSSLCONF.H;
as input
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
--------
Steven M. Schweda s...@antinode-info
382
,PQ_TEST,LH_TEST,DIVTEST,TABTEST as well?
$!
$! Additional directory information.
+$ T_D_ASN1TEST := [-.test]
$ T_D_BNTEST := [-.crypto.bn]
$ T_D_ECTEST := [-.crypto.ec]
$ T_D_ECDSATEST := [-.crypto.ecdsa]
These changes let me get to the test/cms-test.pl problems
(27-APR-2010
tination directory renders this file broken. Having it look at where
it is when it's run (as previously suggested) makes more sense to me.
--------
search [...]*.com arguement ! "argument".
-
LITY.SOURCE.OPENSSL.OPENSSL-1_0_1-STABLE-SNAP-20101217.CRYPTO.BN]BN_NIST.C;1.
[...]
------------
Steven M. Schweda s...@antinode-info
382 South Warwick Street
> [...] A revised "test/CA.com" may be found at:
>
> http://antinode.info/ftp/openssl/1_0_1/apps/CA.com
That should have been 'A revised "apps/CA.com"', of course.
SMS.
__
OpenSSL Project
ot;:
if [ -z "$CATOP" ] ; then CATOP=./demoCA ; fi
It seemed reasonable to me for "apps/CA.com" to do that, too, so now it
does.
It must be perfect, now.
------------
Steven M. Schweda s...@ant
passed (or
returned)." I'd guess that you'll need to disable that code on VMS, at
least when 64-bit pointers are used. (It may be unwise to have the
behavior on VMS depend on the pointer size, so it might be better to
disable it always on VMS.) Any such change should include a g
to decide
how to make it work. I suspect that some string copying will be needed
for the RMS stuff.
------------
Steven M. Schweda sms@antinode-info
382 Sout
27;m not
holding my breath while we wait to hear from them.
------------
Steven M. Schweda sms@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
__
OpenSSL Project
he whole idea was to get the OpenSSL builder(s) to
create SSL_LIBCRYPTO_SHR.EXE/OLB, SSL_LIBCRYPTO_SHR32.EXE/OLB,
SSL_LIBSSL_SHR.EXE/OLB, and SSL_LIBSSL_SHR32.EXE/OLB, that is, 32- and
64-bit libraries and shared images. (Even if no one wanted to add the
"SSL_" prefixes.) Did I miss some
macro/typedef/whatever, so I didn't try to find
and fix every place where it ought to be used. If someone could decide
how to do that, then I could revise, collect, and submit my suggested
changes. (Most of which, if experience is any guide, would probably
then vanish without a trace, but that
MS
=> PKCS#7 compatibility test" sequence. Perhaps some file I/O thing?
The perl script doesn't seem to handle an explosion here very well. A
search for "fail" in the test results transcript won't detect the
absence of an "ALL TESTS SUCCESSFUL" message, mak
From: "Steven M. Schweda"
>On a different point, a closer look at the 64-bit-pointer test
> results shows a problem on Alpha (but not on IA64) somewhere in the "CMS
> => PKCS#7 compatibility test" sequence. Perhaps some file I/O thing?
> The perl script
ader file, "crypto/vms_rms.h" to
reduce the code clutter involved with NAM versus NAML (RMS file name)
structures (in "crypto/LPdir_vms.c" and "crypto/dso/dso_vms.c"). I use
essentially similar stuff in many other pr
ter size. The OpenSSL builders trust the user, and don't try to
check anything. I assume that something will explode, but I don't know
what or where.
Wake me when it catches fire.
---
#x27;" 64 ; show time
Note the "64" arguments on all the procedures for the 64-bit build.
Omit the "libz" path, if you don't have/want zlib support.
As one might expect, I'm still awaiting some discussion of the pending
mysteries, so there's still work l
> IT $ type [-]btsi_z.com
> $ pipe show time ; -
>@ makevms.com ALL "" NODEBUG DECC TCPIP "" -
>utility_root:[source.zlib.zlib-1_2_5l] ; -
>show time
> $ pipe show time ; @ [.test]tests.com ; show time
> $ pipe show time ; @ [.vms]mkshared.com -
>utility_root:[source.zlib.zlib-1_2_5
> http://antinode.info/ftp/openssl/1_0_0d/openssl-1_0_0d_s2.zip
For an "install.com" which works better (perhaps even properly):
http://antinode.info/ftp/openssl/1_0_0d/openssl-1_0_0d_s2a.zip
> $ pipe show time ; @ install.com ""'p1'" ; show time
That > ""'p1'" < should have
>2. The argv-using "apps/*.c" programs need reform to use "argc"
> instead of looking for a NULL terminator at the end of "argv[]".
> (Looking for a NULL makes sense for "envp[]", which is expected to be
> NULL-terminated, but not so much for "argv[]", where it causes bad
> behavior on VMS Alp
I apparently forgot to include the modified/new start-up procedures
("VMS/openssl_startup.com", "VMS/openssl_undo.com") in previous update
collections:
http://antinode.info/ftp/openssl/1_0_0d/openssl-1_0_0d_s2c.zip
SMS.
_
From: Arpadffy Zoltan
> I am sorry, I could not test your changes yet - I'll do it, hopefully, duri=
> ng this week.
> ...but to be honest, I am more curious what is Richard's opinion about your=
> changes.
I'm curious about anyone's opinion, but you know as much as I do.
Please let me know
http://antinode.info/ftp/openssl/1_0_0d/openssl-1_0_0d_s2e.zip
Bad "crypto/crypto-lib.com". (Minor error on VAX.) Trust no one, I
always say. (Especially me.) It'll be a while before the VAX build
gets finished, so stay tuned.
There seems to be some evidence that argv[] _should_ b
orget that I'm still waiting for
wisdom on what to add where to get around the "crypto/bn" problems
caused by sizeof size_t != sizeof void*.
------------
Steven M. Schweda sms@antinode-info
382 South Wa
From: "Dr. Stephen Henson"
> [...] A simple workaround would be to copy
> argv into a malloced copy that is properly NULL terminated if you haven't done
> that already. As all the apps go through main() code in apps/openssl.c you
> should only need to change one place.
http://antinode.info
> http://antinode.info/ftp/openssl/1_0_0d/openssl-1_0_0d_s3.zip
>
> Unless I've missed something, [...]
Naturally, that was too good to be true. I now have enough Perl on
my VAX system to run into a test failure:
[...]
---> TEST_CMS
CMS consistency test
CMS => PKCS#7 compatibility test
Today's project: Restore command-line case preservation for
"openssl.exe" (on modern non-VAX systems, with Parse Style: Extended).
New: "apps/vms_decc_init.c". Modified: "apps/makeapps.com", plus a
bunch of "test/*.com" files which depended on DCL+C command-line
downcasing (or were in danger o
VMS before V8.3 did not support symlinks, so VMSTAR typically
extracted symlinks as text files containing a message with the link
text. This tended to create useless junk in "./include/openssl/"
instead of useful symlinks to actual header files. The "makevms.com"
procedure worked around this b
Ooh. So close.
http://antinode.info/ftp/openssl/1_0_0d/openssl-1_0_0d_s3d.zip
Less buggy editions of:
crypto/install-crypto.com
ssl/install-ssl.com
VMS/mkshared.com
SMS.
__
OpenSSL Project
>Ooh. So close.
Progress continues. In my never-ending quest for fun, I tried
linking an OPENSSL.EXE using the shared images (SSL_*_SHR*.EXE) instead
of the object libraries (SSL_*.OLB), which is something the normal VMS
builders don't do. Naturally, it didn't work. But it was pretty cl
> http://antinode.info/ftp/openssl/1_0_0d/openssl-1_0_0d_s3e.zip
>Wheee. Will the fun never end?
Perhaps after I run "VMS/mkshared.com" on a VAX, and notice a few
other careless errors therein.
http://antinode.info/ftp/openssl/1_0_0d/openssl-1_0_0d_s3f.zip
Sigh. No doubt t
New (complete) replacement file kit:
http://antinode.info/ftp/openssl/1_0_0d/openssl-1_0_0d_s4.zip
This includes a "util/libeay.num" with OPENSSL_strcasecmp, and updated
builders. Previously, LINK commands in the builders lacked explicit
/[NO]MAP options, so, in batch mode, where the de
olding my breath. It would be nice, of course, to have a
release actually work properly on VMS when it's released. (0.9.8r was a
pleasant surprise that way, I recently discovered.)
Steven M. Schweda sms@antinode-info
382 South Warwick Street(+1) 651-699-9818
Sai
> There are probably more such items, lost in the mists of time, but these
> were easy to find in the old-complaint pile.
Going back to 3-APR-2010, for example, I provided a fix for a test
problem involving multi-dot file names on an ODS2 file system. I'll try
again.
[...]
2496048:error:02001
From: Richard Levitte
> Got openssl-1_0_0d_s4.zip and openssl-1_0_0d_s4a.zip couple of days
> ago, it's getting tested right now.
My VAX just finished its run through the latest stuff, and it seems
to be happy. (The Perl build finished, some of its tests passed, and it
seems to work well eno
More VMS builder mysteries...
In "makevms.com", I see:
$! P6, if defined, sets a compiler thread NOT needed on OpenVMS 7.1 (and up).
I find this about as clear as mud. Can anyone explain what "sets a
compiler thread" means? What, exactly, is "NOT needed on OpenVMS 7.1
(and up)"? "A comp
From: Richard Levitte
To: openssl-dev@openssl.org, sms@antinode-info
R:
I'm subscribed to the list, so the extra copy isn't needed.
> about your latest changes, it seems that it has SSL_LIBCRYPTO32.OLB
> and SSL_LIBSSL32.OLB as default names (when have specified "" for the
> bits para
> Also, it seems that /POINTER_SIZE=64=ARGV isn't supported with HP C
> 7.1. [...]
I can believe that. SYS$HELP:CC073.RELEASE_NOTES puts it under "5.2
Enhancements in V7.1", but SYS$HELP:CC071.RELEASE_NOTES doesn't mention
it. Trust no one, I always say.
>That's depressing. My first im
From: Richard Levitte
> sms>I'm subscribed to the list, so the extra copy isn't needed.
>
> Plus the extra copy bounces...
Hmmm. I was getting two. Anyway, ...
> However, there's a point here. When /NOPOINTER_SIZE is used ("" was
> specified for size), are the pointers long or short
From: Richard Levitte
> sms> But all the "64" consumers would need to be changed to deal with the new
> sms> "64A" option.
Or an explicit "64" or "64=ARGV"...
> Naah... this is only needed in makeapps.com, as far as I can tell,
> and it wouldn't be too hard to have a spot in the code simply
From: Richard Levitte
> (we're still talking about the case when the user explicitely asks for
> 64 bit pointers, saying "64" to the build scripts, right?)
Right.
> Hmm, previously, we had a hard case with 64=ARGV when the user gave
> "64", no choice there... Now, the build script adapts to
From: Richard Levitte
> richard> sms> 64 Automatic choice of "64" or "64=ARGV".
> richard> sms> 64=ARGVManual choice of "64=ARGV".
> richard> sms> 64=NOARGV Manual choice of plain "64".
> richard> sms>
> richard> sms> Easy for the normal victim, flexible enough for
utl = n;
return 1;
}
Several other problems, too, but this one looked easy.
Steven M. Schweda sms@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
___
> 64 Automatic choice of "64" or "64=ARGV".
> 64=ARGVManual choice of "64=ARGV".
> 64=Manual choice of plain "64".
Seems to be done, and the compiler test activity no longer leaves
junk object and/or listing files lying around. Original (*.*_orig) and
chan
From: Richard Levitte
> sms>
> http://antinode.info/ftp/openssl/1_0_0d/openssl-SNAP-20110321_s1.zip
>
> Just to clarify, you used openssl-SNAP-20110321.tar.gz for this?
> That's a different branch than the one 1.0.0d comes from...
Yes. (Or "openssl-SNAP-20110321^.tar.gz;1", as it's k
g mistake to be made.)
This stuff was not in 1.0.0d. Is this the kind of optional-feature
module which can be omitted from the build on VAX, or is "long
long"-free code available, or are we doomed now (on VAX)?
; TEST_CA
Generate and certify a test certificate via the 'ca' program
Making CA certificate ...
Generating a 512 bit RSA private key
[...]
I may be running out of complaints.
------------
Steven M. Schweda
but what could go wrong now?
------------
Steven M. Schweda sms@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
__
OpenSSL Project
directly. Around here,
_XOPEN_SOURCE_EXTENDED seems usually to get more things enabled, not
disabled, so it might be safer eleswhere, too.
Steven M. Schweda
r what?
VMS is, by the way, another one of those systems where select() is
good only on sockets, not on files, so a bunch of the
Windows/MSDOS/et-al. conditionality in this and nearby modules probably
needs to be extended to include VMS.
-
I/O (CR, LF, et c.), I would not bet
that any of this stuff would actually look right (without some extra
effort, anyway). Of course, I'm not overly fond of programs which wait
for user input without putting out an obvious prompt first, so what's my
t?
> I find it weird that the particular \n there would fail... isn't that
> something that C library is supposed to deal with properly? Of
> course, s_client uses BIO_printf(), but that one in turn uses the
> usual C library... so it's to wonder why \n would
.0.0h 12 Mar 2012
built on: 14-MAR-2012 00:22:59.46
platform: VMS ALPHA_64 V8.3
options: bn(64,64) md2(int) rc4(ptr,int) des(ptr,risc1,16,long) idea(int)
blowfish(idx)
compiler: /POINTER_SIZE=64 /DEFINE=ZLIB
OPENSSLDIR: N/A
------------
still haven't looked
closely at anything. (With the current no-patches-for-hobbyists policy,
I'm unlikely to know of, or be able to obtain, anythings newer than
these any time soon.)
Steve
s, so actual test runs may still
collide. (So far, I've tried not to learn too much about the actual
tests.)
If there is interest, how should I package the changes?
------------
Steven M. Schweda s...@antinode-in
of those positive
tests for Alpha instead of .NOT. VAX. The (truly sloppy) fixes used in
the builder to accomodate IA64 left the VAX build broken (and the Alpha
build suboptimal, apparently unnoticed). It's a trend. I'll take my
chances.
-
-------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
__
OpenSSL Project
able, now.
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
__
OpenSSL Project http://www.openssl.org
De
when the
VAX re-build is finished. (Those 20-year-old computers just aren't as
fast as they were when they were new.)
------------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 651-699-
One more oops (all my fault):
http://antinode.info/ftp/openssl/0_9_8j/test/tests.com
------------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 651-699-981
://antinode.info/ftp/openssl/0_9_8j/notes_0_9_8j.txt
More builder and installer changes. Shared images now seem to work
on VAX and non-VAX systems. I may have run out of unimportant things to
change.
Steven M. Schweda
iginal ".tar.gz" kit.
------------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
__
OpenSSL Project
/util/libeay.num
> [...] I changed the handling of the
> "capi" problems in the shared image. [...]
Well, now I have. (I _thought_ that I was being careful. Sigh.)
------------
Steven M. Schweda
ing used, and SEARCH finds it in
(0.9.8k) SPEED.OBJ and OPENSSL.EXE, so I'd guess that there would
already be build problems on pre-V7.0 systems, where gettimeofday()
would not be available in the run-time libraries.
-----------
Especially not a native
English speaker. As Count Aristid Karpathy once said, "The English do
not know how to speak their own language. Only foreigners who have been
taught to speak it speak it well." The story's about the same for
writing as it is for speaking.
ffect. Does
anyone care about this stuff on VMS? Is it too much work to rip the
VMS-specific files out of the kit? I see little point in leaving in
what's there now. Applying an occasional band-aid to the corpse seems
to me like a waste of time.
--
the changes I made
for 0.9.8j or 0.9.8k, or are you still working with some Alpha-only
scheme with randomized file/module lists?
--------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 65
changes
I made for 0.9.8j or 0.9.8k, or are you still working with some
Alpha-only scheme with randomized file/module lists?
--------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 65
far back do you
really expect to go?
Wake me when you have a valid complaint.
------------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
l-0_9_8k_s1.zip
----
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
___
se by everyone, which would make changes
easier when the ideal algorithm is determined, but I was trying to
rewrite less than everything. (It may not look that way, but I really
was being about as lazy as I could be. Alphabetical file/module name
lists, for example, make it easier for a lazy person (l
in with the 1.0.0 beta code.
Having had exactly zero apparent success in getting any changes into
the (miserably bad) standard code, I don't feel qualified to advise
anyone on this topic.
Steven M. Schweda s...@antinode-info
382 South Warwick Street
fy> far?
>
> ;-) well, only you can say why you haven't contributed so far ;-)
Yes, contribute, by all means. Or just take a nap. The results seem
to be comparable, except one way you get more sleep.
----
Steve
m with it. (There
is certainly no shortage of problems with the released code.)
--------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
ter than it seems, or does someone think that it
works, or what?
------------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
"diff" for VMS:
http://antinode.info/dec/sw/diffutils.html
No guarantees, but it has worked for me. Wake me (directly) if you have
any questions on it or problems with it.
------------
Steven M. Schweda s...@ant
how, and so on, and why it
wouldn't break a lot of existing stuff.
------------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1) 651-699-9818
Saint Paul MN 55105-2547
e of
those changes seem to have made it to 1.0.0 beta 3, but not all, and I
don't know why. I've asked, but I hear nothing. I can't see a good
reason to make the same changes over and over again if they do not get
adopted, and no one says why they do not get adopted. What am I
miss
> and I'll play...
I'd spend some time looking for a user who would care about VAX C
before I spent any time trying to use it to compile any modern code.
DEC C has been around since about when, mid-1994? On my fastest VAX
(4000 model 200), building this stuff takes a whole d
operly before the
actual release? The beta kits so far have not been encouraging. I've
given up on seeing several previously suggested changed adopted, but it
would be nice if, for example, a simple build simply worked.
find out what happened when I see the next "betaN" kit.
It's not very satisfying, and I've largely stopped caring. (This may or
may not be seen as much of a loss.)
----
Steven M. Schweda s..
a time.
If any of this stuff was even close to working when I downloaded it,
then that argument might carry a little more weight. (Call me a
whiner.)
Steven M. Schweda s...@antinode-info
382 South Warw
nto a local object/executable?
(Surely some lame/goofy rule could be devised, even in that situation.)
------------
Steven M. Schweda s...@antinode-info
382 South Warwick Street(+1
odule T1_LIB file
ALP$DKA0:[UTILITY.SOURCE.OPENSSL.openssl-1^.0^.0-beta5.ALPHA.EXE.SSL]LIBSSL.OLB;1
I assume that these things need to be added to "crypto/symhacks.h"
and/or "util/libeay.num".
----
Steven M.
assume that these things need to be added to "crypto/symhacks.h"
> > and/or "util/libeay.num".
Well, "util/.num". Probably. (Perhaps?)
Steven M. Schweda s...@antino
1 - 100 of 149 matches
Mail list logo
