Re: [openssl.org #111] Cross compilation assumption

2002-06-28 Thread johan . adolfsson


- Original Message - 
From: Richard Levitte via RT [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: den 27 juni 2002 17:17
Subject: [openssl.org #111] Cross compilation assumption 


 
 [[EMAIL PROTECTED] - Thu Jun 27 15:49:46 2002]:
 
  Yes, I did notice that after sending, so it's not that big a deal 
 as I
  first thought.  I can see two solutions:
  
   - Add another field to Configure
 
 Yes, that could be a possibility.  Another is to call make like this:
 
 make AR=foo
 
 Also, you haven't answered the implied question: what platform is it 
 that needs something different than 'ar', and what is the name of 
 that alternate command?

When crosscompiling for the CRIS architecture 
(in ETRAX chips from Axis Communciations, Sweden)
the tools are: gcc-cris, ranlib-cris and ar-cris (or cris-xx)
(possibly some extra arguments as well)
I believe some arm toolchains has similar naming.
Perhaps a generic xx$(CROSS) or $(CROSS)xx would be generally usable?

/Johan

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]



[openssl.org #127] AES draft cipher suites

2002-06-28 Thread Bodo Moeller via RT


While the AES cipher suites from draft-ietf-tls-ciphersuite-06.txt are
disabled by default and not part of ALL (the AESdraft group alias
can be used to enable them), they might be accidentily enabled by using
cipher suite strings such as RSA.  The reason for disabling them
unless explicitly requested is that they are not yet official, so it may
be a problem if seemingly innocuous strings such as RSA enable them.

(Similarly, cipher suite strings such as DES will enable ADH cipher
suites that are left out of ALL.  But this is less of a problem
because these cipher suites are official; they are not in ALL simply
because usually anonymous connections are not desired.)

A possible strategy is to define a new group alias for all those cipher
suites that are not part of ALL, which could be called NONE (unless
someone comes up with a more serious name for it).  Then !NONE in a
cihper suite string will disable all cipher suites that are not in
ALL, i.e. RSA:!NONE would be RSA without AESdraft and
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]