Path: ...!weretis.net!feeder8.news.weretis.net!usenet.goja.nl.eu.org!aioe.org!yOKtEt/+TrHtdyDN3pco6A.user.gioia.aioe.org.POSTED!not-for-mail
From: rustbuckett@pm.me (Russell)
Newsgroups: news.software.readers
Subject: Re: Checking PGP/GnuPG Signatures in tin
Date: Mon, 24 May 2021 00:04:09 +0000 (UTC)
Organization: Aioe.org NNTP Server
Lines: 34
Message-ID: <s8eqhp$1vdm$1@gioia.aioe.org>
References: <s8b282$opl$1@gioia.aioe.org> <s8c8cc$h19$1@nntp.de>
NNTP-Posting-Host: yOKtEt/+TrHtdyDN3pco6A.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
X-Complaints-To: abuse@aioe.org
User-Agent: tin/2.4.5-20201224 ("Glen Albyn") (Linux/5.12.5-arch1-1 (x86_64))
X-Notice: Filtered by postfilter v. 0.9.2
Bytes: 2394

Urs Janßen <urs@buil.tin.org> wrote:
> In <s8b282$opl$1@gioia.aioe.org> on Sa, 22 Mai 2021 15:50:59, Russell wrote:
>> entry, but nothing works. Tin hooks the line in mailcap, but I get an
>> error that the command failed. I think I'm on the right track, but I
>> can't figure out the details since tin doesn't have a lot of
>> documentation.
> 
> inline pgp/gpg (none mime) should work via ^G when viewing an article
> (and pgp/gpg was propperly detected/configured at compile time).
> 
> when mime is involved 'V' and mailcap should work
> 
> this is from my ~/.mailcap which I havn't touched for ages, can't say if
> that still works, I don't do gpg.
> 
> application/pgp-signature;\
>         NAME=%s \&\& DATA=`echo $NAME|sed 's,\\(unknown-00.\\)\\.pgp,\\1.asc,'|tr '123456789' '012345678'` \&\& gpg --verify %s $DATA; needsterminal
> 
> and for headersigning (like in control messages) '|'"pgpverify" should do
> it.

That didn't work. I guess it just can't be done. At least I don't
understand enough to get it to work. I almost never see anyone using
inline signatures and I don't know that I've ever seen header signing.
If the developer of tin doesn't have it working, I guess it just doesn't
work. I'm not really a programmer or I'd look into it, but I wouldn't
even know where to start.

Thank you for your suggestions. Please followup if you figure it out.
I'll do the same if I stumble onto a solution. lol!

-- 
rust
0x890FAC3B7DD734A435AB7624FD3E8AFDB2EE6EF0