RE: Trouble building MSDOS version
This has turned out to be much more of a project than I have time in the schedule to complete. My boss is willing to explore bringing in a consultant to speed up the process. Is there anyone out there that can help us re-create enough of an MS-DOS library to do the DH key exchange and RC-4, assuming the full WIN32 version will be on the other end? Thank you, Bob McConnell -Original Message- From: Bob McConnell Sent: Thursday, March 09, 2000 10:02 AM To: '[EMAIL PROTECTED]' Subject: Trouble building MSDOS version Good morning, I know that the older 16 bit support is not being kept up to date, but I'm hoping there is someone that has a suggestion how to fix this. I am trying to build the library for an embedded DR-DOS target running on 386 and 486 processors on PC/104 cards. The target system is Ampro 386/25MHz or 486/133MHz CPUs Boot Diskette image built in Flash ROM (R/O file system) DR-DOS 5.0 NE2000 Ethernet card Novell TCP/IP stack and socket library (Taken from their LAN Workplace SDK) The development platform is NT 4 SP5 ActiveState Perl build 515 VC++ 1.50c MASM 6.00B The plan is to be able to establish an RC4 encrypted connection between this target and a service running on an NT server. Both ends are running our own applications. I want to open the socket, skip the certificate exchange, use DH to exchange a session key and enable the encryption for all traffic until the socket is closed. This is for a POS system that will initiate the connection about 2:30 am, after running an End Of Day audit, and be online until the next EOD. All private secrets will be kept in a local disk file. Thank you, Bob McConnell Principal Communications Programmer The CBORD Group, Inc. 61 Brown Road Ithaca, NY 14850-1247 Phone 607 257-2410 Fax 607 257-1902 email [EMAIL PROTECTED] web www.cbord.com __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
RE: Trouble building MSDOS version
With whom do I discuss these changes? I have added MSDOS switches to four files, and everything compiles. But I also had to change some switches in msdos.mak, and I don't understand what RANLIB is for, so I just commented it out for now. I grabbed unistd.h and stat.h from Bob Stout's SNIPPETS library (SNIP9707). All stat.h does is "#include sys\stat.h" where Micros~1 hides it. My next problem is translating the "ar r" commands to "LIB". Basically, it requires something like: O_CRYPTO= $(LIB_D)\lib$(CRYPTO) for each %o in $(CRYPTOOBJ); do LIB $(O_CRYPTO).lib +%o, $(O_CRYPTO).lst\; ; done But I doubt that I have the syntax correct. The semicolon after $(O_CRYPTO).lst is necessary to tell LIB that the command line is complete, so don't ask for any additional files (non-interactive form). If you don't want a listing file, everything between the comma and semi-colon can be skipped. There were some 'L's missing from shift constants in lines 226, 227 and 228 of crypto\des\set_key.c, but they weren't causing any of my problems. If I really understood all that I know about this stuff, this project might actually be fun. Thank you for listening. Bob McConnell -Original Message- From: Ulf Möller [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 09, 2000 11:47 AM To: Bob McConnell Cc: '[EMAIL PROTECTED]' Subject: Re: Trouble building MSDOS version On Thu, Mar 09, 2000 at 10:02:10AM -0500, Bob McConnell wrote: Looking at the source, it's obvious that it's not expecting to have MSDOS defined, the #IFDEF's only check for WIN32 and __ultrix. You'll have to add the relevent #ifdefs for MSDOS, there's no way around that. This is simple for bss_log.c because DOS has no logging facilities, but it's possible that there will be problems at other places as well. __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Trouble building MSDOS version
Good morning, I know that the older 16 bit support is not being kept up to date, but I'm hoping there is someone that has a suggestion how to fix this. I am trying to build the library for an embedded DR-DOS target running on 386 and 486 processors on PC/104 cards. The target system is Ampro 386/25MHz or 486/133MHz CPUs Boot Diskette image built in Flash ROM (R/O file system) DR-DOS 5.0 NE2000 Ethernet card Novell TCP/IP stack and socket library (Taken from their LAN Workplace SDK) The development platform is NT 4 SP5 ActiveState Perl build 515 VC++ 1.50c MASM 6.00B The plan is to be able to establish an RC4 encrypted connection between this target and a service running on an NT server. Both ends are running our own applications. I want to open the socket, skip the certificate exchange, use DH to exchange a session key and enable the encryption for all traffic until the socket is closed. This is for a POS system that will initiate the connection about 2:30 am, after running an End Of Day audit, and be online until the next EOD. All private secrets will be kept in a local disk file. The initial step was Perl configure no-threads 386 VC-MSDOS I then made some manual changes to the ms\msdos.mak file INSTALLTOP=E:\COMMS\msdos\openssl.095 CC=cl CFLAG=-O1 -DMSDOS -DNO_SOCK /G3 # -O1 optimizes for speed SRC_D=E:\COMMS\msdos\openssl.095 When I actually try to make the library (nmake -f ms\msdos.mak) everything appears to work until it gets to crypto/bio/bss_log.c, where I get the following error: cl -o tmp\bss_log.o -Ioutinc -Itmp -O1 -DMSDOS -DNO_SOCK /G3 -c E:\COM MS\msdos\openssl.095\crypto\bio\bss_log.c Microsoft (R) C/C++ Optimizing Compiler Version 8.00c Copyright (c) Microsoft Corp 1984-1993. All rights reserved. e:\comms\msdos\openssl.095\crypto\bio\bss_log.c e:\comms\msdos\openssl.095\crypto\bio\bss_log.c(73) : fatal error C1083: Cannot open include file: 'syslog.h': No such file or directory NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x2' Stop. Looking at the source, it's obvious that it's not expecting to have MSDOS defined, the #IFDEF's only check for WIN32 and __ultrix. Is there a quick and easy way to remove or screen out this log function and anything that can't work in the MSDOS world? Is there any way? Thank you, Bob McConnell Principal Communications Programmer The CBORD Group, Inc. 61 Brown Road Ithaca, NY 14850-1247 Phone 607 257-2410 Fax 607 257-1902 email [EMAIL PROTECTED] web www.cbord.com __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
