srv/www/cv.html: NOTES: Expand NeoMutt

Signed-off-by: Alejandro Colomar <alx@kernel.org>

1 files changed, 40 insertions, 11 deletions

diff --git a/srv/www/cv.html b/srv/www/cv.html
index c81d98f..cc6d1dd 100644
--- a/srv/www/cv.html
+++ b/srv/www/cv.html
@@ -223,6 +223,46 @@
 		</li>
 
 		<li>
+		<h4 class="inl"><a href="https://neomutt.org/">
+		<span class="name">NeoMutt</span></a></h4>
+		<p>
+		I've added (and continue adding)
+		several crypto features to the project,
+		to improve the security of messages.
+		<ul>
+			<li class="bullet"><h4>
+			-C:
+			<a href="https://neomutt.org/feature/cli-crypto">
+			(feature) Command-line crypto</a>
+			</h4></li>
+			<li class="bullet"><h4>
+			<a href="https://github.com/neomutt/neomutt/pull/4221">
+			(feature) Encryption information block</a>
+			</h4></li>
+		</ul>
+		<p>
+		While doing that,
+		I've also found and helped find
+		several security vulnerabilities
+		in NeoMutt and in other MUAs.
+		<ul>
+			<li class="bullet"><h4>
+			<a href="https://github.com/neomutt/neomutt/issues/4223">
+			(vulnerability) A third party can add itself to an encrypted conversation</a>
+			</h4></li>
+			<li class="bullet"><h4>
+			<a href="https://github.com/neomutt/neomutt/issues/4226">
+			(vulnerability) A third party can resend a signed message in a different conversation</a>
+			</h4></li>
+			<li class="bullet"><h4>
+			<a href="https://github.com/neomutt/neomutt/issues/4234">
+			(vulnerability) BCC recipients in encrypted messages are leaked</a>
+			</h4></li>
+		</ul>
+		</p>
+		</li>
+
+		<li>
 		<h4 class="inl"><a href="https://unit.nginx.org/">
 		<span class="name">NGINX Unit</span></a></h4>
 		</p>
@@ -268,17 +308,6 @@
 			</h4></li>
 		</ul>
 		</li>
-
-		<li>
-		<h4 class="inl">neomutt(1)</h4>
-		<ul>
-			<li class="bullet"><h4>
-			-C:
-			<a href="https://neomutt.org/feature/cli-crypto">
-			(new feature) Command-line crypto</a>
-			</h4></li>
-		</ul>
-		</li>
 	</ul>
 </div>
 <hr/>