Please explain what your problems is. Setting arbitrary debug flags is not helpful for your or us.

In T4906#133954, @JW wrote:

@jukivili,

I'd be interested in seeing the results of testing the patch. Can you provide a link to the results?

Of course, you are absolutely correct. I'll update the text accordingly. I thought EdDSA and EcDSA would be expressing differences between Cv25519 and NIST-256. I am not an expert. :-)

EdDSA is sign only - how do you want to encrypt to such a key? Did you mean cv25519 and ECDH?

I also don't think that key size obfuscation is useful, after all the preferences of the key demand a certain key size.

Small fix to translation - found by my friend

I'd be interested in seeing the results of testing the patch. Can you provide a link to the results?

Clever idea.

I'm testing this as an initial start:

ac_ext=c
ac_objext=o

@jukivili : Thank you. Please apply & push it.

Installer in Win10 / Ukrainian environment:

These changes were reworked into Kleopatra patch for all platforms:
https://phabricator.kde.org/D28580

Today I wanted to check linked issue: main window of Kleopatra doesn't remember size.
I worked on it again full day and found really good solution which is already present in KDE libs.
This is new fix for dialogs mentioned in this ticket and for MainWindow:
https://phabricator.kde.org/D28580

@werner what size of each additionally allocated secure memory area would you recommend? Is this something, that is better to set or leave up to the gpg-agent to decide? Will this additional memory be freed when not needed anymore or will it stay allocated until the process dies? I guess, the documentation could be expanded to answer this.

Attached patch should solve the issue for gcc 7.5 and clang 8.

Patch with my fix: https://dev.gnupg.org/D498
(now I know how to submit it!)

Thanks for looking into this!

Pushed the changes.

You can test with newer compiler.

OK. I reopen this ticket to collect information.

It looks like the recipe to build the source file is missing the necessary arch options. I.e., -mcpu=power7 -mvsx ...

I can't reproduce the error (no problem for build). My (cross-)compiler is:

I think that it is compiler issue for AltiVec (now, VSX) support.
The usage is not ambiguous. It _is_ ambiguous in the header file.

Thansk for your report.

There is nothing spiteful about this other than your actions.

Please stop this and use the mailing list for such ramblings. Usually only one developer reads a bug report and thus you can't participate from the experience of others - use mailing lists - please.

It runs like:

$ gpg-connect-agent "scd devinfo --watch" /bye
S DEVINFO_START
S DEVINFO_END
S DEVINFO_STATUS new
S DEVINFO_START
S DEVICE generic D276000124010200F517000000010000 openpgp
S DEVINFO_END
S DEVINFO_STATUS removal
S DEVINFO_START
S DEVINFO_END
OK
$ 

Push the change to master.

werner closed this task as Spite.

We do not use Github.

See my comments on the other bugs you posted today.

Please see my other comments; we need proper bug reports and not just arbitrary snippets.

That are all development versions and they may require the latest changes from the repo of other libraries.

Please write proper bug reports and do not just post snippets from some arbitrary build process. In addition master is non-released software and thus it is in general better to ask at gcrypt-devel@gnupg.org for help.

Sorry, if you use your own copy of GnuPG on GitHub, it is all up to you. We do not use Github.