26.1-rc1: Gnus issue when signing message / prompting for passphrase

26.1-rc1: Gnus issue when signing message / prompting for passphrase

[Joseph Mingrone]

[-- Attachment #1: Type: text/plain, Size: 462 bytes --]

Hello,

I have been running 26.1-rc1 since the 16th and things have been smooth.

I did have to change the value of `epa-pinentry-mode' to 'loopback to get prompted for a passphrase when opening an encrypted file.  But, when sending messages in Gnus with `mml-secure-message-sign', instead of being prompted for the passphrase, a 'Wrong type argument: char-or-string-p, nil' error is reported, which I believe occurs in or around `mml-compute-boundary'.

Joseph

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

Re: 26.1-rc1: Gnus issue when signing message / prompting for passphrase

[Lars Ingebrigtsen]

Joseph Mingrone <jrm@ftfl.ca> writes:

> I did have to change the value of `epa-pinentry-mode' to 'loopback to
> get prompted for a passphrase when opening an encrypted file.  But,
> when sending messages in Gnus with `mml-secure-message-sign', instead
> of being prompted for the passphrase, a 'Wrong type argument:
> char-or-string-p, nil' error is reported, which I believe occurs in or
> around `mml-compute-boundary'.

Please (setq debug-on-error t) to get a backtrace and report this bug
with `M-x report-emacs-bug'.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: 26.1-rc1: Gnus issue when signing message / prompting for passphrase

[Noam Postavsky]

On 24 April 2018 at 21:18, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Joseph Mingrone <jrm@ftfl.ca> writes:
>
>> I did have to change the value of `epa-pinentry-mode' to 'loopback to
>> get prompted for a passphrase when opening an encrypted file.  But,
>> when sending messages in Gnus with `mml-secure-message-sign', instead
>> of being prompted for the passphrase, a 'Wrong type argument:
>> char-or-string-p, nil' error is reported, which I believe occurs in or
>> around `mml-compute-boundary'.
>
> Please (setq debug-on-error t) to get a backtrace and report this bug
> with `M-x report-emacs-bug'.

Isn't this Bug#26298?

Re: 26.1-rc1: Gnus issue when signing message / prompting for passphrase

[Joseph Mingrone]

[-- Attachment #1: Type: text/plain, Size: 789 bytes --]

Noam Postavsky <npostavs@gmail.com> writes:

> On 24 April 2018 at 21:18, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>> Joseph Mingrone <jrm@ftfl.ca> writes:

>>> I did have to change the value of `epa-pinentry-mode' to 'loopback to
>>> get prompted for a passphrase when opening an encrypted file.  But,
>>> when sending messages in Gnus with `mml-secure-message-sign', instead
>>> of being prompted for the passphrase, a 'Wrong type argument:
>>> char-or-string-p, nil' error is reported, which I believe occurs in or
>>> around `mml-compute-boundary'.

>> Please (setq debug-on-error t) to get a backtrace and report this bug
>> with `M-x report-emacs-bug'.

> Isn't this Bug#26298?

This does describe what I am seeing.  Thanks and apologies for missing it before posting here.

Joseph

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

Re: 26.1-rc1: Gnus issue when signing message / prompting for passphrase

[Noam Postavsky]

>>>> I did have to change the value of `epa-pinentry-mode' to 'loopback to
>>>> get prompted for a passphrase when opening an encrypted file.  But,
>>>> when sending messages in Gnus with `mml-secure-message-sign', instead
>>>> of being prompted for the passphrase, a 'Wrong type argument:
>>>> char-or-string-p, nil' error is reported, which I believe occurs in or
>>>> around `mml-compute-boundary'.

>> Isn't this Bug#26298?
>
> This does describe what I am seeing.

I've proposed a patch there which renames `epa-pinentry-mode' into
`epg-pinentry-mode', any comments would be appreciated; we're
stumbling towards a solution but the bug thread is somewhat lacking
input from people with a strong grasp of how epg and epa code fits
together...

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26298#63