From 22b05ed942a826fd385d87d442f27f96cabadecb Mon Sep 17 00:00:00 2001 From: Heiko Schaefer Date: Wed, 1 Nov 2023 19:00:33 +0100 Subject: [PATCH] Motivation text for this document --- book/source/01-intro.md | 15 ++------------- 1 file changed, 2 insertions(+), 13 deletions(-) diff --git a/book/source/01-intro.md b/book/source/01-intro.md index 9f00051..cda982f 100644 --- a/book/source/01-intro.md +++ b/book/source/01-intro.md @@ -35,20 +35,9 @@ This document is not intended for end-users or implementers of OpenPGP libraries Instead, this document is focused on the second group, application developers, who use OpenPGP functionality in their software projects. It describes the properties of the OpenPGP system and its uses. It presupposes solid knowledge of software development concepts and of general cryptographic concepts. Thus, this text describes OpenPGP at the "library-level," teaching concepts that will help software developers get started as a user of any implementation (e.g., [OpenPGP.js](https://openpgpjs.org/), [Sequoia-PGP](https://sequoia-pgp.org/)). -```{admonition} TODO -:class: warning +With the emergence of a new crop of modern, high-quality, OpenPGP libraries, and the imminent release of the updated [OpenPGP version 6 specification](https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/), we think that now is a great time to implement OpenPGP functionality in applications, or to modernize existing OpenPGP subsystems. -Heiko, we should elaborate a bit on why here - -arguments: - -- standardized cryptographic system -- long history, broard support -- lately: many high-quality, modern, library implementations (in the past there were no good ways to integrate openpgp into applications) -- the new version of the standard is almost ready, defining a modernized version 6 of the protocol - -- all of this together: it's now easier than ever to add openpgp functionality to applications, and the updated standard brings the cryptographic building blocks up to the state of the art -``` +We aim to offer an implementation-independent introduction to the OpenPGP technology, to help software developers get their bearings more quickly. The text is also intended as a stepping stone to more easily locate relevant information in the RFC, when necessary. ## Why not just use the OpenPGP RFC?