Fix for 2.4 is rG2aacd843ad

Thank you for your reply! I'll modify my testcase

I figured out the situation.

Ah, I found that we have very bad example use case in tests/t-mpi-point.c. This should be fixed at first.

Thank you for your report. IIUC, it is called unexpected way, like invalid/wrong KEYPARMS. Possibly, KEYPARMS == NULL, or something like that.

works

Thanks. Commited to master.

When I look at the stack information, I find that because E->p is not assigned in the function mpi_ec_get_elliptic_curve(), this produces a null pointer，but it didn't get to the branch : if (errc) goto leave;

If you pass NULL to that function, the calling code is wrong. No need for an explicit check in nomralize - check should be done in the public API (if at all).

I tried to fix the segmentation fault, so I added a null pointer check at the end to protect it.

Here is my try of next, after 0001.

In T6309#166019, @ametzler1 wrote:

Missed some, will post an updated patch.

Regarding armored files: Well the whole point of armoring is that there is only a plain 7-bit ASCII channel.

It seems that we removed the support for the BOM at some point in the past. Probably because config files are anyway suppossed to be utf-8 encoded.

Here is my try:

works

works: the process is canceled without any notification.

works

Fixed by reverting to 2.5.5

Problem is that Kleopatra uses the latest libassuan from Git and not the released version. Replacing the libassuan DLL with the one from the gnupg directory fixes the bug.

Missed some, will post an updated patch.