Updates documentation of RC4_CHAR and RC4_INT: Should not be used for new configurati...
authorFrederik Wedel-Heinen <frederik.wedel-heinen@dencrypt.dk>
Fri, 7 Jul 2023 11:17:11 +0000 (13:17 +0200)
committerTomas Mraz <tomas@openssl.org>
Sun, 20 Aug 2023 11:33:45 +0000 (13:33 +0200)
Fixes: #21358
CLA: trivial

Reviewed-by: Paul Dale <pauli@openssl.org>
Reviewed-by: Hugo Landau <hlandau@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/21391)

(cherry picked from commit c2a8226cba2757b251729620aedffeed23d73623)

Configurations/README.md

index be8c394d0872b2f51aeb64873203883a54e1cd88..de3d8bad8a02d44710635b33f11e946d8c64c71b 100644 (file)
@@ -233,8 +233,14 @@ In each table entry, the following keys are significant:
                                                 is ILP32;
                            RC4_CHAR             RC4 key schedule is made
                                                 up of 'unsigned char's;
+                                                Note: should not be used
+                                                for new configuration
+                                                targets
                            RC4_INT              RC4 key schedule is made
                                                 up of 'unsigned int's;
+                                                Note: should not be used
+                                                for new configuration
+                                                targets
 
 [1] as part of the target configuration, one can have a key called
   `inherit_from` that indicates what other configurations to inherit