OpenSSL itself as utility is very useful for processing certificates and keys. And it is a dependency library for so many open source products that it is must to have.
S pozdravem * Mit freundlichen Grüßen * Sincerely, Peter Ondruška -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Kirk Wolf Sent: Tuesday, May 22, 2012 5:49 PM To: [email protected] Subject: Re: OpenSSL MAKE problem Magnus, Terry, and all - We were wondering why there seems to be a recent swell of interest in porting OpenSSL to z/OS? Could you comment (offline if you prefer) as to why you need it? Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, May 22, 2012 at 6:36 AM, Magnus Persson <[email protected]>wrote: > Thanks, that did the trick with c99_x. > > I'm now running my MAKE again with c99_x hoping for better luck this time. > > Hälsningar / Best regards, > > Magnus Persson, Mainframe > Tieto > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Ondruška Peter > Sent: den 22 maj 2012 09:17 > To: [email protected] > Subject: Re: OpenSSL MAKE problem > > Hi, I was just trying to figure out this myself and found out you need > to add /usr/lpp/cbclib/xlc/bin to your PATH environment. > > S pozdravem * Mit freundlichen Grüßen * Sincerely, > > Peter Ondruška > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Magnus Persson > Sent: Tuesday, May 22, 2012 9:15 AM > To: [email protected] > Subject: Re: OpenSSL MAKE problem > > Hi Terri! > > I have already followed your "laundry list", that is what have gotten > me this far in installation, so a big THANK YOU! > > The only thing that I can't do in the same way as you do it is the > c99_x, my system can't find c99_x so I ran it with c99 instead. > > I guess that this might cause some trouble, but I can't find any > solution on how to make the c99_x available, when I test it from the > OMVS prompt c99_x only returns an FSUM7351 not found. > > Anybody who knows how to make c99_x reachable??? > > Hälsningar / Best regards, > > Magnus Persson, Mainframe > Tieto > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Shaffer, Terri E > Sent: den 21 maj 2012 15:43 > To: [email protected] > Subject: Re: OpenSSL MAKE problem > > But here is sortof the laundry list of what I found and used with Lots > of help. > > 1) Update the Configure perl script and add this line (after the > existing OS390-Unix line, which isn't used): > > "OS/390","c99_x:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H > -D_ALL_SOURCE::(unknown):::THIRTY_TWO_BIT DES_PTR DES_UNROLL MD2_CHAR > RC4_INDEX RC4_CHAR BF_PTR:::", > > Notice that all I changed was to change the label to "OS/390" and to > use the c99_x command. > - c99 means to use STDC99, which automatically implies LONGLONG. This > avoids the shell quoting issues. > - the c99_x means to compile and link using XPLINK linkage. > > 2) ensure that perl and gmake are in your PATH > > 3) chmod +x tools/* > > 4) export MAKE=gmake > export _C89_CCMODE=1 (not sure that this is needed any more with the > c99 command) > > 5) gmake install failed because of Undeclared identifiers > > ERROR CCN3045 ./b_sock.c:888 Undeclared identifier NI_MAXHOST. > ERROR CCN4324 ./b_sock.c:888 Array size must have integer type. > ERROR CCN3045 ./b_sock.c:888 Undeclared identifier NI_MAXSERV. > ERROR CCN4324 ./b_sock.c:888 Array size must have integer type. > > So, I added these lines to crypto/bio/b_sock.c file starting at line > 102 > > Which was right after these identifiers #ifndef WSAAPI #define WSAAPI > #endif > > Added these > > #ifndef NI_MAXSERV > #define NI_MAXSERV 32 > #endif > > #ifndef NI_MAXHOST > #define NI_MAXHOST 1025 > #endif > > Then I had a few other issues, not sure if it was caused by my > installation or the openssl code. I'm guessing the first. > > In the PROBLEMS doc there is a reference for this issue. > > gmakeÝ2¨: Entering directory `/u/w012108/temp/openssl-1.0.1/apps' > ( :; LIBDEPS="${LIBDEPS:--L.. -lssl -L.. -lcrypto }"; > LDCMD="${LDCMD:-c99_x}"; LDFLAGS="${LDFLAGS:--O -DB_ENDIAN > -DCHARSET_EBCDIC -DNO_SYS_PARAM_H -D_ALL_SOURC E}"; LIBPATH=`for x in > $LIBDEPS; do echo $x; done | sed -e 's/¬ *-L//;t' -e d | uniq`; > LIBPATH=`echo $LIBPATH | sed -e 's/ /:/g'`; > LD_LIBRARY_PATH=$LIBPATH:$LD_ LIBRARY_PATH ${LDCMD} ${LDFLAGS} -o > ${APPNAME:=openssl} openssl.o verify.o asn1p ars.o req.o dgst.o dh.o > dhparam.o enc.o passwd.o gendh.o errstr.o ca.o pkcs7.o c rl2p7.o crl.o > rsa.o rsautl.o dsa.o dsaparam.o ec.o ecparam.o x509.o genrsa.o gen > dsa.o genpkey.o s_server.o s_client.o speed.o s_time.o apps.o s_cb.o > s_socket.o app_rand.o version.o sess_id.o ciphers.o nseq.o pkcs12.o > pkcs8.o pkey.o pkeypara m.o pkeyutl.o spkac.o smime.o cms.o rand.o > engine.o ocsp.o prime.o ts.o srp.o ${ LIBDEPS} ) > FSUM3008 Specify a file with the correct suffix (.c, .i, .s, .o, .x, > .p, .I, or .a), or a corresponding data set name, instead of -L... > gmakeÝ2¨: *** Ýlink_app.¨ Error 1 > gmakeÝ2¨: Leaving directory `/u/w012108/temp/openssl-1.0.1/apps' > gmakeÝ1¨: *** Ýopenssl¨ Error 2 > gmakeÝ1¨: Leaving directory `/u/w012108/temp/openssl-1.0.1/apps' > gmake: *** Ýbuild_apps¨ Error 1 > > Went in and edited the Makefile in apps and test directory > > #LIBCRYPTO=-L.. -lcrypto > #LIBSSL=-L.. -lssl > #Commented out previous lines > #Added the following 2 lines for -L issue per PROBLEMS doc > LIBCRYPTO=../libcrypto.a LIBSSL=../libssl.a > > Then it started to complain about missing CEE.xxxxxx datasets, this > was because my C++ compiler was never customized > > In member /usr/lpp/cbclib/xlc/etc/xlc.cfg was still pointing to default > MVS datasets. > > After that everything magically got solved and I now have a valid > openssl module. > > /temp/openssl-1.0.1/apps > ./openssl version OpenSSL 1.0.1 14 Mar 2012 > > Hope that helps and you hopefully dont have the last few issues. > > I know way too much now about something I thought was ummm simple. > > Thanks > > Ms. Terri E. Shaffer > [email protected] > Engineer > J.P.Morgan Chase & Co. > GTI DCT ECS Core Services zSoftware Group / Emerging Technologies > Office: # 614-213-3467 > Cell: # 412-519-2592 > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Magnus Persson > Sent: Friday, May 11, 2012 2:37 AM > To: [email protected] > Subject: OpenSSL MAKE problem > > Hi. > > I'm trying to install the latest version of OpenSSL, I have followed > the instructions given in som threads here (big THANKS to those > involved) > > My problem is this: > > ERROR CCN3045 ./bss_conn.c:203 Undeclared identifier AF_INET. > WARNING CCN4421 ./bss_conn.c:204 Implicit function declaration for > function "htons". > WARNING CCN4421 ./bss_conn.c:210 Implicit function declaration for > function "htonl". > WARNING CCN4421 ./bss_conn.c:213 Implicit function declaration for > function "socket". > ERROR CCN3045 ./bss_conn.c:213 Undeclared identifier SOCK_STREAM. > WARNING CCN4421 ./bss_conn.c:256 Implicit function declaration for > function "connect". > WARNING CCN4421 ./bss_conn.c:379 Implicit function declaration for > function "shutdown". > CCN0793(I) Compilation failed for file ./bss_conn.c. Object file not > created. > > Since I no NTOHING about C, I am totally lost. > > My GUESS is that I'm missing a #define of SOCKETS or something like that? > > But I haven't got the slightest idea on where to put this define.... > > Hälsningar / Best regards, > > Magnus Persson, Mainframe > > Tieto > [email protected], direct +46 (0)10 4810183, mobile +46 (0)73 > 0203133 Fjärde Bassängvägen 15, 115 83 Stockholm, Sweden, > www.tieto.com > > Please note: The information contained in this message may be legally > privileged and confidential and protected from disclosure. If the > reader of this message is not the intended recipient, you are hereby > notified that any unauthorised use, distribution or copying of this > communication is strictly prohibited. If you have received this > communication in error, please notify us immediately by replying to > the message and deleting it from your computer. Thank You. > > Please consider the environment before printing this e-mail. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN This > communication is for informational purposes only. It is not intended > as an offer or solicitation for the purchase or sale of any financial > instrument or as an official confirmation of any transaction. All > market prices, data and other information are not warranted as to > completeness or accuracy and are subject to change without notice. Any > comments or statements made herein do not necessarily reflect those of > JPMorgan Chase & Co., its subsidiaries and affiliates. > > This transmission may contain information that is privileged, > confidential, legally privileged, and/or exempt from disclosure under > applicable law. If you are not the intended recipient, you are hereby > notified that any disclosure, copying, distribution, or use of the > information contained herein (including any reliance > thereon) is STRICTLY PROHIBITED. Although this transmission and any > attachments are believed to be free of any virus or other defect that > might affect any computer system into which it is received and opened, > it is the responsibility of the recipient to ensure that it is virus > free and no responsibility is accepted by JPMorgan Chase & Co., its > subsidiaries and affiliates, as applicable, for any loss or damage > arising in any way from its use. If you received this transmission in > error, please immediately contact the sender and destroy the material > in its entirety, whether in electronic or hard copy format. Thank you. > > Please refer to http://www.jpmorgan.com/pages/disclosures for > disclosures relating to European legal entities. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
