Encryption and signing

Encrypting, decrypting and signing data from application code: a document wrapped for one recipient, a payload signed so its origin can be checked, a value enciphered with a key both sides hold. Encryption of a connection, TLS, is set up in the system and is outside this concern.

Overview

SAP SHIPS

The SSF library for the ABAP stack creates and verifies PKCS#7 digital signatures and encrypts and decrypts documents, through SSF_KRN_SIGN, SSF_KRN_VERIFY, SSF_KRN_ENVELOPE and SSF_KRN_DEVELOPE.

Not covered: At PKCS#7. The SSF page names no call for a symmetric cipher such as AES or Blowfish in a chosen mode, and none for OpenPGP.

How the community cipher implementations relate to the SSF library has not been assessed.

Artifacts3

3 of 3 artifacts
ArtifactSignals
Packages3
abapPGPOpenPGP implementation in ABAP, scoped to signing
Signals
Functional boundary
hhelibeb/blowfish-abapBlowfish cipher in ABAP, ECB and CBC modes
Signals
Quiet
Sumu-Ning/AESAES and Rijndael encryption utilities for ABAP
Signals
none

Details

Coverage
statecore and community, ABAP
assessed
relationshipunassessed
also inBTP/BAIP
For your agent