From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <9front-bounces@9front.inri.net>
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI
	autolearn=ham autolearn_force=no version=3.4.4
Received: from 9front.inri.net (9front.inri.net [168.235.81.73])
	by inbox.vuxu.org (Postfix) with ESMTP id 09E162B312
	for <ml@inbox.vuxu.org>; Thu, 17 Oct 2024 22:05:32 +0200 (CEST)
Received: from mx0.riseup.net ([198.252.153.6]) by 9front; Thu Oct 17 16:04:24 -0400 2024
Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	by mx0.riseup.net (Postfix) with ESMTPS id 4XTzLt3JZDz9wXN
	for <9front@9front.org>; Thu, 17 Oct 2024 20:04:22 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
	t=1729195462; bh=UjRpsO2mhSxx1+RKXhkrnhyK43dngD5cbwp0/PUc1w0=;
	h=Date:From:To:In-Reply-To:References:Subject:From;
	b=sW4naMo/e/uZU0aX2fTvjL/3unSO5LY825A27ibrsl3gPytbySRSEvfp3I4S6pZwU
	 Mcpy9QV3t9saru0IGt80VGgXSWuEsy3dqO48RiDUD6NnxJV75DS3SYasc6HL1jExpl
	 C/0lNVLRMYtLs8DBR0Vgl2F94IptR9ctdvctYFAc=
X-Riseup-User-ID: C09D953DE0D3571359261469ECB5EC951A0535FCC64D333F2395A51050D58F1B
Received: from [127.0.0.1] (localhost [127.0.0.1])
	 by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4XTzLs5SfRzFvnk
	for <9front@9front.org>; Thu, 17 Oct 2024 20:04:21 +0000 (UTC)
Date: Thu, 17 Oct 2024 23:34:17 +0330 (GMT+03:30)
From: mkf9 <mkf9@riseup.net>
To: 9front@9front.org
Message-ID: <95cab9c1-f538-4e0d-b3a7-8ef264e0bc65@riseup.net>
In-Reply-To: <B9C6B83E09D9865923DFB890A8B6FDEA@chrisfroeschl.de>
References: <B9C6B83E09D9865923DFB890A8B6FDEA@chrisfroeschl.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Correlation-ID: <95cab9c1-f538-4e0d-b3a7-8ef264e0bc65@riseup.net>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: decentralized anonymous session-oriented blockchain 
Subject: Re: [9front] marshal(1) and pgp
Reply-To: 9front@9front.org
Precedence: bulk

take a look at contrib, I recall some version did existed there.

walk contrib | grep '(ppg|gpg)'

Oct 5, 2024 4:33:56 PM chris@chrisfroeschl.de:

> marshal(1) advertises the -pe and -ps flags to encrypt/sign the input.
>
> The flags are indeed implemented=20
> (/sys/src/cmd/upas/marshal/marshal.c:389) using
> a /bin/pgp (/sys/src/cmd/upas/marshal/marshal.c:1171) .
>
> Does anyone know what this pgp exec is? Some historic relict?
>
> I'm only aware of moody's https://github.com/majiru/pgp .
>
> I see three options:
> 1. Remove those flags since there is no real standard pgp
> 2. Define/Ship a standard pgp for 9front
> 3. Move pgp logic into it's own more independent component
> =C2=A0=C2=A0=C2=A0 to be piped or offered through the mail client
> =C2=A0=C2=A0=C2=A0 (like an extra nedmail option or something like that)
> =C2=A0=C2=A0=C2=A0 (a better architecture?)
> =C2=A0=C2=A0=C2=A0
> I would work out a patch if an appropiate solution is found.
>
> I'm currently using moodys pgp with a patched marshal. Regarding 2.,
> I don't think that the golang pgp implemenation would really fit into
> the 9front release, since this would be the first golang project to
> be part of the standard build.
>
> Feel free to comment.
>
> chris