feat: blog post on librepgp

_config.yml

@@ -1,5 +1,5 @@
 title: RNP
-description: Email encryption with unrivaled performance, RFC 4880 compliant.
+description: Secure email with unrivaled performance. LibrePGP and RFC 4880 compliant.
 # The above two are used by jekyll-seo-tag for things such as
 # `<title>` and `<meta>` tags, as well as elsewhere by the theme.
 
@@ -10,7 +10,7 @@ algolia_search:
   index_name: 'rnpgp'
 
 tagline: >-
-  Powering end-to-end email encryption in Mozilla Thunderbird.
+  Powering end-to-end email encryption in Mozilla Thunderbird. LibrePGP secure.
 
 landing_priority:
   - software
@@ -21,7 +21,9 @@ landing_priority:
   - man_pages
 
 pitch: >-
-  Secure email with unrivaled performance. RFC&nbsp;4880 compliant.
+  <a href="https://www.librepgp.org"><img title="LibrePGP" src="/assets/librepgp-button.svg"/></a>
+  Secure email with unrivaled performance.
+  <a href="https://www.librepgp.org">LibrePGP</a> and RFC&nbsp;4880 compliant.
 
 author: "Ribose Inc."
 

_pages/feedback.adoc

@@ -4,11 +4,11 @@ title: Feedback and security reports
 permalink: /feedback/
 bodyClass: page
 ---
-== Feedback and security reports
+= Feedback and security reports
 
 We love to hear from you!
 
-=== Reporting bugs and general feedback and bugs
+== Reporting bugs and general feedback and bugs
 
 For general issues or bugs, please enter them at the
 _RNP_ GitHub public issue tracker:
@@ -18,7 +18,7 @@ _RNP_ GitHub public issue tracker:
 NOTE: The RNP GitHub issue tracker is publicly viewable. Please report
 security issues via dedicated channels.
 
-=== Security reporting
+== Security reporting
 
 For reporting security vulnerabilities or security bugs, or
 bugs with sensitive content,

_posts/2024-07-22-rnp-and-librepgp.adoc

@@ -0,0 +1,117 @@
+---
+layout: post
+title: "RNP proudly supports LibrePGP"
+categories: news
+authors:
+  - name: Ronald Tse
+    email: [email protected]
+    social_links:
+      - https://github.com/ronaldtse
+  - name: Nickolay Olshevsky
+    email: [email protected]
+    social_links:
+      - https://github.com/ni4
+excerpt: >-
+  RNP is excited to announce our support for LibrePGP, a new specification of
+  the OpenPGP encryption standard that builds on the lessons learned from 20
+  years of experience with GnuPG, the most widely used and adopted
+  implementation of OpenPGP.
+---
+= RNP proudly supports LibrePGP
+
+At RNP, we are excited to announce our support for
+https://www.librepgp.org[LibrePGP], a new specification of the OpenPGP
+encryption standard that builds on the lessons learned from the 20 years of
+experience with OpenPGP, allowing secure messages in the past to remain secure
+in the future.
+
+
+== What is LibrePGP?
+
+image::/assets/librepgp-button.svg[LibrePGP Logo, width=400]
+
+LibrePGP is a new specification of the OpenPGP secure email standard that is
+designed to ensure the long-term stability, compatibility and security of
+protection communication.
+
+LibrePGP is conceived and backed by https://g10code.com[g10 Code],
+https://www.ribose.com[Ribose], and https://intevation.de[Intevation], and is
+maintained by a study group consisting of the founding group with other
+interested implementers.
+
+== Why is RNP Supporting LibrePGP?
+
+We believe that LibrePGP is an essential step forward in preserving the core
+principles of openness and compatibility in secure communication.
+
+We share the concerns that sparked the LibrePGP initiative: changes made to the
+OpenPGP specification by a subgroup within the IETF OpenPGP working group were
+perceived as potentially disrupting existing implementations, raising concerns
+about interoperability and security.
+
+As a developer of OpenPGP tools, we believe that LibrePGP is a vital effort to
+ensure the long-term stability and compatibility of secure communication
+protocols. Our involvement in LibrePGP reflects our commitment to preserving the
+security, reliability, and flexibility of the OpenPGP standard.
+
+https://www.gnupg.org[GnuPG] (GNU Privacy Guard) has been the de-facto reference
+implementation of OpenPGP for over two decades. Its widespread adoption and use
+have provided valuable insights into the needs and requirements of secure
+communication protocols. LibrePGP builds on these lessons learned, providing a
+robust and flexible specification that is designed to meet the evolving needs of
+secure communication.
+
+== Long-term collaboration with g10 Code and Intevation
+
+As the developer of RNP, Ribose works closely with g10 Code, the developer of
+GnuPG, and Intevation, the developer of Gpg4win, the most prevalent OpenPGP
+implementation available on Windows. Our teams perform a significant amount of
+interoperability testing to ensure that our implementations are compatible and
+secure.
+
+Together, we defend internet mail and sensitive information internationally in a
+trusted manner, all through a commitment to open-source. Our shared goal is to
+ensure that secure communication is accessible to everyone, regardless of
+platform or system.
+
+In fact, RNP and GnuPG were the first two implementations that supported
+https://web.cs.ucdavis.edu/~rogaway/ocb/[OCB (Offset Codebook) encryption], a
+high-performance and secure encryption algorithm designed by Prof. Phillip
+Rogaway.
+
+We successfully interoperated with OCB encryption since 2018, demonstrating our
+commitment to implementing and testing new encryption algorithms. OCB encryption
+is now a mandatory part of the LibrePGP specification, and we are proud to have
+played a key role in its adoption.
+
+== What does this mean for RNP users?
+
+As a user of RNP, you can rest assured that our commitment to LibrePGP will
+ensure that our software remains compatible with existing OpenPGP
+implementations. This includes the https://www.gnupg.org[GnuPG] and
+https://www.gpg4win.org[Gpg4win] projects, which are also supporters of
+LibrePGP.
+
+== What's next?
+
+We will continue to work closely with the LibrePGP community to ensure that the
+RNP implementation meets the evolving needs of secure communication.
+
+== About RNP
+
+RNP is a set of openly-licensed LibrePGP / OpenPGP tools that work on all major
+platforms. RNP provides end-to-end encryption for secure communication,
+including email and file encryption.
+
+Learn more about our projects and how we are committed to preserving the
+security and compatibility of OpenPGP standards.
+
+== About LibrePGP
+
+LibrePGP is a new specification of the OpenPGP encryption standard that builds
+on the lessons learned from global deployment of OpenPGP technology backed with
+over 20 years of experience.
+
+It is designed to ensure the long-term stability and compatibility of secure
+communication protocols. Visit the https://www.librepgp.org[LibrePGP] website to
+learn more about the initiative.

assets/css/style.scss

@@ -52,11 +52,22 @@ body.site--project.layout--home {
     background: rgba(0, 0, 0, 0.4);
   }
   > .underlay.header {
-    > .hero > .text {
-      > .cta .button {
-        border-radius: 25px;
-        padding-left: 32px;
-        padding-right: 32px;
+    > .hero {
+      a {
+        color: #ffffff;
+        text-decoration: underline;
+      }
+      img {
+        float: left;
+        height: 30px;
+        margin-right: 10px;
+      }
+      > .text {
+        > .cta .button {
+          border-radius: 25px;
+          padding-left: 32px;
+          padding-right: 32px;
+        }
       }
     }
   }

custom-intro.html

@@ -1,8 +1,9 @@
 <section class="summary">
   <p>
-    Technical writer?
-    Please take a look at <a href="https://github.com/rnpgp/rnp/tree/master/docs">RNP docs on GitHub</a>
-    and read our <a href="/blog/2021-03-26-rnp-gsod-2021/">Google Season of Docs proposal blog post</a>,
-    contributions are appreciated!
+    Ribose proudly announces full support for
+    <a href="https://www.librepgp.org"><img title="LibrePGP" src="/assets/librepgp-button.svg" style="height:30px;"/></a>: a new specification for
+    OpenPGP that defends secure communication into the future. See the
+    <a href="blog/2024-07-22-rnp-and-librepgp/">announcement</a> for more
+    information.
   </p>
 </section>