9front - general discussion about 9front
 help / color / mirror / Atom feed
From: mkf9 <mkf9@riseup.net>
To: 9front@9front.org
Subject: Re: [9front] marshal(1) and pgp
Date: Thu, 17 Oct 2024 23:34:17 +0330 (GMT+03:30)	[thread overview]
Message-ID: <95cab9c1-f538-4e0d-b3a7-8ef264e0bc65@riseup.net> (raw)
In-Reply-To: <B9C6B83E09D9865923DFB890A8B6FDEA@chrisfroeschl.de>

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 
> (/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
>     to be piped or offered through the mail client
>     (like an extra nedmail option or something like that)
>     (a better architecture?)
>    
> 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

      parent reply	other threads:[~2024-10-17 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-05 13:00 chris
2024-10-05 13:33 ` Stanley Lieber
2024-10-17 20:04 ` mkf9 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95cab9c1-f538-4e0d-b3a7-8ef264e0bc65@riseup.net \
    --to=mkf9@riseup.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).