History log of /openbsd-src/lib/libcrypto/rc4/rc4.c (Results 1 – 13 of 13)
Revision Date Author Comments
# 902bfdca 27-Jan-2025 jsing <jsing@openbsd.org>

Mop up RC4_INDEX.

The RC4_INDEX define switches between base pointer indexing and per-byte
pointer increment. This supposedly made a huge difference to performance
on x86 at some point, however comp

Mop up RC4_INDEX.

The RC4_INDEX define switches between base pointer indexing and per-byte
pointer increment. This supposedly made a huge difference to performance
on x86 at some point, however compilers have improved somewhat since then.
There is no change (or effectively no change) in generated assembly on
a the majority of LLVM platforms and even when there is some change
(e.g. aarch64), there is no noticable performance difference.

Simplify the (still messy) macros/code and mop up RC4_INDEX.

ok tb@

show more ...


# 09b34817 11-Aug-2024 jsing <jsing@openbsd.org>

Provide and use crypto_arch.h.

Provide a per architecture crypto_arch.h - this will be used in a similar
manner to bn_arch.h and will allow for architecture specific #defines and
static inline funct

Provide and use crypto_arch.h.

Provide a per architecture crypto_arch.h - this will be used in a similar
manner to bn_arch.h and will allow for architecture specific #defines and
static inline functions. Move the HAVE_AES_* and HAVE_RC4_* defines here.

ok tb@

show more ...


# 3715bfbf 28-Mar-2024 jsing <jsing@openbsd.org>

Use static inline for rc4_set_key_internal().


# 42e47793 28-Mar-2024 joshua <joshua@openbsd.org>

Hide symbols in RC4

ok jsing tb beck


# a0d14d73 28-Mar-2024 jsing <jsing@openbsd.org>

Use C functions for RC4 public API.

Rather than having public API switch between C and assembly, always
use C functions as entry points, which then call an assembly
implementation (if available). Th

Use C functions for RC4 public API.

Rather than having public API switch between C and assembly, always
use C functions as entry points, which then call an assembly
implementation (if available). This makes it significantly easier
to deal with symbol aliasing/namespaces and it also means we
benefit from vulnerability prevention provided by the C compiler.

Rename the assembly generated functions from RC4() to rc4_internal()
and RC4_set_key() to rc4_set_key_internal(). Always include rc4.c
and change it to use defines that are similar to those used in BN.

ok beck@ joshua@ tb@

show more ...


# 578c3ea3 27-Mar-2024 jsing <jsing@openbsd.org>

Consolidate rc4 code.

Discussed with tb@


# e9f80f1d 22-Apr-2014 miod <miod@openbsd.org>

Remove meat which either duplicates code found in apps/, or is only of value
for 20th century historians, and can be put in the Attic.


# 4fcf65c5 06-Sep-2008 djm <djm@openbsd.org>

resolve conflicts


# 767fe2ff 12-May-2003 markus <markus@openbsd.org>

merge 0.9.7b with local changes; crank majors for libssl/libcrypto


# da347917 15-May-2002 beck <beck@openbsd.org>

OpenSSL 0.9.7 stable 2002 05 08 merge


# 30c3aa8e 07-Jul-2000 deraadt <deraadt@openbsd.org>

use %s with fprintf


# 913ec974 29-Sep-1999 beck <beck@openbsd.org>

OpenSSL 0.9.4 merge


# 5b37fcf3 05-Oct-1998 ryker <ryker@openbsd.org>

Import of SSLeay-0.9.0b with RSA and IDEA stubbed + OpenBSD build
functionality for shared libs.

Note that routines such as sslv2_init and friends that use RSA will
not work due to lack of RSA in th

Import of SSLeay-0.9.0b with RSA and IDEA stubbed + OpenBSD build
functionality for shared libs.

Note that routines such as sslv2_init and friends that use RSA will
not work due to lack of RSA in this library.

Needs documentation and help from ports for easy upgrade to full
functionality where legally possible.

show more ...