Lutz Jaenicke:
>> I have already worked in the cipher selection routines yesterday with
>> respect to PR#130. I will add an appropriate "NOTDEFAULT" selection
>> keyword that will cover cipher suites not selected by default.
>> As this is a new feature I intend to only add it to 0.9.7 (and later
Lutz Jaenicke:
>> I have already worked in the cipher selection routines yesterday with
>> respect to PR#130. I will add an appropriate "NOTDEFAULT" selection
>> keyword that will cover cipher suites not selected by default.
>> As this is a new feature I intend to only add it to 0.9.7 (and later)
[jaenicke - Wed Jul 10 08:50:56 2002]:
> [bodo - Thu Jul 4 10:34:15 2002]:
>
> > However, it would still be a good idea to create a "NONE" cipher
suite
> > group alias because it is useful in the other scenarios given in the
> > problem description.
>
> I have already worked in the cipher se
[bodo - Thu Jul 4 10:34:15 2002]:
> However, it would still be a good idea to create a "NONE" cipher suite
> group alias because it is useful in the other scenarios given in the
> problem description.
I have already worked in the cipher selection routines yesterday with
respect to PR#130. I wi
RFC3268 makes the AES cipher suites official, so the "AESdraft" problem
no longer exists.
However, it would still be a good idea to create a "NONE" cipher suite
group alias because it is useful in the other scenarios given in the
problem description.
_
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
