From f1c6fd67d3ec49851839cf4a2ba77f78e1082df8 Mon Sep 17 00:00:00 2001 From: Paul Schaub Date: Thu, 12 Jan 2023 15:34:22 +0100 Subject: [PATCH] Update sop-java/README --- sop-java/README.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/sop-java/README.md b/sop-java/README.md index 471d510..507ac5b 100644 --- a/sop-java/README.md +++ b/sop-java/README.md @@ -55,16 +55,13 @@ List signatureVerifications = messageInfo.getVerifications(); Furthermore, the API is capable of signing messages and verifying unencrypted signed data, as well as adding and removing ASCII armor. -### Limitations -As per the spec, sop-java does not (yet) deal with encrypted OpenPGP keys. - ## Why should I use this? If you need to use OpenPGP functionality like encrypting/decrypting messages, or creating/verifying signatures inside your application, you probably don't want to start from scratch and instead reuse some library. Instead of locking yourselves in by depending hard on that one library, you can simply depend on the interfaces from -`sop-java` and plug in a library (such as `pgpainless-sop`) that implements said interfaces. +`sop-java` and plug in a library (such as `pgpainless-sop`, `external-sop`) that implements said interfaces. That way you don't make yourself dependent from a single OpenPGP library and stay flexible. Should another library emerge, that better suits your needs (and implements `sop-java`), you can easily switch