From: Christoph Liebender <christoph@liebender.dev>
Subject: Re: NEW: net/mollysocket
To: Stuart Henderson <stu@spacehopper.org>
Cc: ports@openbsd.org
Date: Tue, 4 Mar 2025 17:12:29 +0100

Am 03.03.25 um 10:50 schrieb Stuart Henderson:
> On 2025/03/01 19:47, Christoph Liebender wrote:
>> Comments, ok?
> 
> the readme should follow the template used in other ports, see
> /usr/ports/infrastructure/templates
> 
> I don't have time to look further today

I've made the readme follow the template. I've also shortened it a bit 
for it to be more concise. It is attached. Thanks!

diff --git a/net/mollysocket/pkg/README b/net/mollysocket/pkg/README
index 3bc09414630..c4a101dcaa9 100644
--- a/net/mollysocket/pkg/README
+++ b/net/mollysocket/pkg/README
@@ -1,16 +1,14 @@
-${PKGSTEM} setup on OpenBSD
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
++-------------------------------------------------------------------------------
+| Running ${PKGSTEM} on OpenBSD
+-------------------------------------------------------------------------------

-To finish your mollysocket install, you need to generate a VAPID key 
and append
-it to ${SYSCONFDIR}/mollysocket.conf .
+Finish installing
+=================

-To do this, either run
-
-$ mollysocket vapid gen
-
-and paste its output in the "vapid_privkey" field of the configuration, or:
+You need to generate a VAPID key and append it to 
${SYSCONFDIR}/mollysocket.conf .
+To do this, you may run:

  # sed -i "s|changeme|$(mollysocket vapid gen)|" 
${SYSCONFDIR}/mollysocket.conf

-Make sure that the permissions on ${SYSCONFDIR}/mollysocket.conf stay
-restrictive.
+Since ${SYSCONFDIR}/mollysocket.conf now contains a secret, take care that
+permissions on that file stay restrictive.