Re: C-Kermit 9.0 first Alpha test
- From: Steven Schweda <sms.antinode@xxxxxxxxx>
- Date: Fri, 20 Nov 2009 15:53:12 -0800 (PST)
Frank da Cruz wrote:
: [...]
: #define des_cblock DES_cblock
: ...................^
: %CC-W-MACROREDEF, The redefinition of the macro "des_cblock" conflicts
: with a current definition because the replacement lists differ...
:
I'm not sure why this is even being picked up unless a secure build
is being attempted. In that case, there are some things to be aware
of. First, OpenSSL changed the names of the DES routines between
0.9.6 and 0.9.7; it might be necessary to add -DOPENSSL_097 to the
CC flags. Second (probably not relevant in this case), OS vendors are
starting to remove DES encryption from all their products.
: [...]
Well, of _course_ it's a secure build! Where's the fun if
you don't enable all the options?
Defining OPENSSL_097 seems to do no good. The first
definition of des_cblock is around ckuath.c:195:
#else /* KRB4 */
#ifdef CK_SSL
#define des_cblock Block <---
#ifdef COMMENT
#define const_des_cblock const Block
#endif /* COMMENT */
#define des_key_schedule Schedule <---
#endif /* CK_SSL */
Then, someone drags in <openssl/des_old.h>:
[...]
#ifndef OPENSSL_DES_LIBDES_COMPATIBILITY
#define des_cblock DES_cblock
#define const_des_cblock const_DES_cblock
#define des_key_schedule DES_key_schedule
[...]
which is where we get the %CC-W-MACROREDEF complaints about
des_cblock and des_key_schedule. Defining
OPENSSL_DISABLE_OLD_DES_SUPPORT does evade the problem,
resulting in a nearly clean build. I'm not sure how this
should be fixed.
The remaining complaint (only "%CC-I-QUESTCOMPARE", so not
a big problem) is:
Compiling ALP$DKA0:[UTILITY.SOURCE.KERMIT.v9r0_2009-11-20]CKVTIO.C
while ((n--) && xx_inc(2) >= 0) ; /* Ignore Warning - see
comments */
.........................^
%CC-I-QUESTCOMPARE, In this statement, the unsigned expression "(--
ttxbn>=0?(uns
igned)(ttxbuf[ttxbp++]&0X00000000000000FF):txbufr(...))" is being
compared with
a relational operator to a constant whose value is not greater than
zero. This
might not be what you intended.
at line number 921 in file
ALP$DKA0:[UTILITY.SOURCE.KERMIT.v9r0_2009-11-20]ckvtio.c;1
My (latest) build command:
@ CKVKER.COM SFI D "CK_SSL,OPENSSL_DISABLE_OLD_DES_SUPPORT"
and:
ALP$DKA0:[UTILITY.SOURCE.KERMIT.v9r0_2009-11-20] C-Kermit>show
versions
Versions:
C-Kermit 9.0.299 Alpha.01, 16 Nov 2009
Numeric: 900299
Built for: OpenVMS Alpha
Running on: OpenVMS Alpha 8 V8.3 Alpha
Patches: (none)
Communications I/O 9.0.124, 16 Oct 2009 for OpenVMS Alpha
File support, 9.0.181, 16 Oct 2009 for OpenVMS Alpha
C-Kermit library, 9.0.045, 16 Nov 2009
C-Kermit Protocol Module 9.0.160, 16 Oct 2009
C-Kermit functions, 9.0.229, 15 Feb 2009
Command package 9.0.167, 16 October 2008
User Interface 9.0.295, 10 November 2009
Character Set Translation 9.0.042, 16 Oct 2009
CONNECT Command 8.0.062 5 Apr 2004
Dial Command, 9.0.160, 16 Oct 2009
Script Command, 9.0.032, 16 Oct 2009
Network support, 9.0.293, 16 Oct 2009
Telnet support, 9.0.273, 16 Oct 2009
FTP Client, 9.0.253, 16 Oct 2009
Authentication, 9.0.234, 16 Oct 2009
SSL/TLS support, 9.0.226, 16 Oct 2009
ALP$DKA0:[UTILITY.SOURCE.KERMIT.v9r0_2009-11-20] C-Kermit>
I'm assuming that "FTP Client, 9.0.253, 16 Oct 2009" means
that I got the internal FTP client. It seemed to work, at
least a little, but when I tried "ftp dir" in a populous
directory, I got an uninterruptable listing (which seemed to
go on for a very long time). The normal (TCPIP) FTP client
handles Ctrl/C better (apparently sending an "ABOR" command),
and not running until everything's been spewed to the
terminal.
.
- References:
- Re: C-Kermit 9.0 first Alpha test
- From: Steven Schweda
- Re: C-Kermit 9.0 first Alpha test
- From: Frank da Cruz
- Re: C-Kermit 9.0 first Alpha test
- Prev by Date: Re: C-Kermit 9.0 first Alpha test
- Next by Date: Re: C-Kermit 9.0 first Alpha test
- Previous by thread: Re: C-Kermit 9.0 first Alpha test
- Next by thread: Re: C-Kermit 9.0 first Alpha test
- Index(es):
Relevant Pages
|
