Sumu-Ning/AES
AES and Rijndael encryption and decryption utilities for ABAP, covering six cipher modes and three padding schemes, installed by copying the source or through abapGit.
AES implements AES encryption and decryption in ABAP as a special case of the more general Rijndael cipher, through classes such as ZCL_AES_UTILITY and ZCL_RIJNDAEL_UTILITY. It covers six modes, ECB, CBC, PCBC, CFB, OFB and CTR, and three padding schemes, and the README says PKCS #5 and no padding do not work well with AES unless you know exactly what they do, recommending PKCS #7 instead. Installation is a source file copied straight into the ABAP editor, or pulled in through abapGitabapGitA Git client written in ABAP that runs inside the system, so objects are cloned, pulled and pushed without leaving it; with no package manager in ABAP, a cloned repository is how code is distributed.community org, abap.
Facts
Where it sits
Who is behind it
In the atlas: maintains 1, contributes to 1@Sumu-NingmaintainerjeremycoppeyContributes to this
In the atlas: contributes to 1@jeremycoppeyLars HvamContributes to this
In the atlas: maintains 13, contributes to 92, wrote 1@larshpDaniel WegnerContributes to this
In the atlas: maintains 3, contributes to 10@WegnerDan3 contributors
What it declares
Every artifact
- Type
- Package
- Origin
- Independently maintained
As a package
- Where it runs
- does not say
- Distributed through
- abapGitCopied into the project
Connections
Encrypting, decrypting and signing data from application code
OpenPGP implementation in ABAP, scoped to signing
Download
README
quoted from Sumu-Ning/AES under MIT, readAES algorithm implementation by ABAP
ABAP Utilities for AES encryption, decryption under MIT License.
Actual Implementation is done by the more generic Rijndael way, and AES is treated as a special case.
Supporting:
- Encryption mode: ECB, CBC, PCBC, CFB, OFB, CTR.
- Padding standard: None, PKCS #5, PKCS #7. (Please use PKCS #7, No Padding and PKCS #5 do not work well with AES, unless you know clearly what they are doing.)
Please just copy the source code file into ABAP editor (Source Code-Based mode), and activate it. Or install via abapGit.
Classes:
- ZIF_AES_MODE: Interface for different encryption mode.
- ZCL_AES_MODE_CBC: CBC mode.
- ZCL_AES_MODE_CFB: CFB mode.
- ZCL_AES_MODE_CTR: CTR mode.
- ZCL_AES_MODE_ECB: ECB mode.
- ZCL_AES_MODE_OFB: OFB mode.
- ZCL_AES_MODE_PCBC: PCBC mode.
- ZCL_BYTE_PADDING_UTILITY: Abstract class for Byte padding utilities, including factory method to get concrete class instances.
- ZCL_PADDING_UTILITY_NONE: No padding.
- ZCL_PADDING_UTILITY_PKCS_5: Padding using PKCS #5.
- ZCL_PADDING_UTILITY_PKCS_7: Padding using PKCS #7.
- ZCL_RIJNDAEL_UTILITY: implementation of Rijndael, encrypt and decrypt using xstring.
- ZCL_AES_UTILITY: AES wrapper on ZCL_RIJNDAEL_UTILITY, just need to provide key and data.
- ZCL_AES_UTILITY_TEST:
- Testing cases of ZCL_AES_UTILITY, including encryption mode ECB, CBC, CFB, OFB, CTR, Testing of PCBC is not included yet.
- Testing Data is from http://csrc.nist.gov/publications/nistpubs/800-38a/sp800-38a.pdf
- Testing cases of No padding and PKCS #7 padding, but only in ECB, CBC and CTR mode.
Others providing
Compare all 4 on the Encryption and signing page →- SAP Keystore ServiceSAP Keystore ServiceA repository for cryptographic keys and certificates in SAP BTP's Neo data centres, which an application retrieves at runtime for signing, encryption and SSL communication.sap official, btpKey and certificate repository in SAP BTP's Neo data centresfrom BTP/BAIP
- hhelibeb/blowfish-abaphhelibeb/blowfish-abapA Blowfish cipher implemented directly in ABAP after Bruce Schneier's definition, encrypting and decrypting strings in ECB and CBC mode through one class, on ABAP 750 or higher.independent, abapBlowfish cipher in ABAP, ECB and CBC modesfrom ABAP
- abapPGPabapPGPAn OpenPGP implementation in ABAP, scoped to signing and marked work in progress, whose own README warns that it will most certainly contain severe bugs and points to established PGP software.independent, abapOpenPGP implementation in ABAP, scoped to signingfrom ABAP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
abaplint
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:sumu-ning-aes- JSON
- /artifacts/sumu-ning-aes.json
- MCP
- Connecting an agent