# Utilizing Trusted Lightweight Ciphers To Support Electronic-Commerce Transaction Cryptography
## 2 Related Works of E-Commerce Security
Four distinct message-encoding and -decoding algorithms were found and compared from the five libraries that meet the DDH assumption. However, their proposed problems include applications that generate large numbers without test randomness, and this affects security. Moreover, third-message encryption technology is generally difficult and can only be implemented for a small subset of messages where an account can be solved with a discrete logarithm by BF. In addition, the decryption tool is less important than encryption in the electronic process. Some applications do not use the safe initial setting of the ElGamal scheme, which affects security, and some libraries parse part of the information about the original message, which exposes the system to danger and makes the system unsafe. [PERSON] et al. [15] presented a suggestion about the design of a relational database that covered the creation of a multi-tier secure architecture for integrating the dam management framework with its tasks. They employed the AES technique and generated keys to encrypt and decode the dam data via the password-based key derivation function 2 (PBKDF2), random numbers generator (RNG) sequences generator and the slave key for salting security. However, their suggestion suffered from some problems, including low randomness, complex arithmetic operations efficiency, differences in execution time, encryption and decryption, and long keys being slow due to large dynamic operations. [PERSON] and [PERSON] [16] submitted a proposal to optimize operations in encryption algorithms in order to protect digital data and to provide data security using AES cryptography. To decrease the time required for encryption and decryption while still boosting the security of digital data, they reduced the number of rounds in AES to 14. However, their proposal used large arithmetic operations that make encryption operations slow. The encryption transfer rate depends on the size of the files, as well as the speed of the encryption and decryption processes. Employing a key size of 256 makes the encryption process slower and more complex than AES-80 and AES-128. However, AES-256 is safer for applications that deal with sensitive information such as e-commerce applications. [PERSON] et al. [17] adopted a recommendation regarding high-speed, low-power hardware designs for effective field programmable gate arrays (FPGA). They implemented AES cryptography to support information security. They used AES encryption and decryption in their method. Combinational logical circuits were used in their architecture to achieve SubBytes and InvSubBytes transformation. Look-up tables (LUTs) were removed from their design, eliminating any unnecessary delays, and a sub-pipelining structure was added to increase the performance of the AES algorithm. To lower the overall hardware requirements, the modified positive polarity Reed Muller (MPPRM) approach was added in this case, and comparisons with various implementations were performed utilizing AES-MPPRM. However, there were several drawbacks to their proposal. The process of generating a key led to consuming more time when expanding the key [18], and the cryptanalysis process checked the algorithm security by testing some threats such as a side channel threat, where their method was weak to some attacks such as DDoS and fraud. [PERSON] et al. [19] presented a proposal to use encryption algorithms to secure text document files. They used the ElGamal algorithm. Additionally, they made use of the Fermat prime generator technique, which seeks prime random numbers, from which they derived the randomized prime numbers that made up the public and private keys. Nonetheless, there are some problems with their proposal that may hinder its implementation in real applications. Among these, the ElGamal algorithm suffers from the difficulty of computing the logarithm and large and random arithmetic operations in encryption operations. The algorithm is too complex to encrypt big text files. [PERSON] et al.