We have had this in the past but it led to subtle build and, worse, runtime problems. Thus the decision to provide architecture dependent files and have configure complain for wrong files. Right, you sometimes get false warnings for non-matching cpu-vendor-os strings but I consider this less severe than the old problem.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 29 2020
That patch fixes the build problem I got into today when trying to build 2.3 for windows. So ? from me and please commit the patch as it is already required when assuan and gpgrt config no longer emit ws2_32 in their pgk-config --libs line.
I just saw that there is related discussion and a patch for this in T4994 so I will close again here.
to give you any help I would need to know the exact error. I can only tell you that this is not a problem related to Gpg4win something else must be messy on your system. The Uninstaller of Gpg4win cleans up all registry keys that do not contain user config and all files should be removed unless some other process on the system interferes.
This change broke for me the compilation of GPGME which I fixed with: 52f930c1ed7eee6336a41598c90ef3605b7ed02b I found that fix there OK because GPGME explicitly uses ws2_32.
Linking $(NETLIB) is required when the executable uses WSAStartup.
Jul 28 2020
Jul 27 2020
Phabricator allows it again to upload patches. It's D507
In Kleopatra/src/dialogs/subkeyswidget.cpp there is already a context menu for subkeys.
Well, it is now defined. We use a CMS object containing an OpenPGP keyblock container. Right, there is no open standard for it but with OIDs you don't really need them. it is a bit of a hack but it works with the majority of deployed cards and the overhead is quite small.
Still an issue, just noticed that with the 3.1.12 release announcement, it really looks ugly.
@wener But it uses undefined data structure of "certificate" DO, IIUC. My point is defining DOs for OpenPGP, so that host side can construct OpenPGP object from those DOs.
Jul 26 2020
Item 2 and 3 have already been solved by allowing to store a minimal key.
Jul 24 2020
Jul 23 2020
Jul 22 2020
Jul 21 2020
Jul 20 2020
I deferred this thing because I hoped to implement this in the keyboxd. Another option is to use a truncated fingerprint - for displaying purposes we anyway truncate to 25 byte and 20 byte should also be okay until we can move this to keyboxd. But okay, if you want to add support please go ahead but make sure that there are no fatal conditions if a gpg 2.2 accesses the v5 enabled trustdb.
Dear gnupg developers.
I have contacted the Microsoft to get their analysis as well.
A Case #:20812681 has been registered. Where Microsoft stated that third party developers of plugins like GpgOL have their channels and should contact Microsoft directly in cases like this. Further analysis has been denied to me.
Here is the patch for trustdb and keybox. Not introduced new record structure, but RECTYPE_TRUST_SHA2 saving only 20-byte.
Something like:
- 1-byte: TYPE
- 1-byte: Reserved
- 32-byte: fingerprint
- 1-byte; ownertrust / min_ownertrust
- 1-byte: depth
- 4-byte: validlist recnum
Any news on this?
Jul 19 2020
- - it get stuck with empty window
Jul 18 2020
I started "gpgconf --launch gpg-agent" and afterwards PuTTY. Then I am asked to "login as:". After entering the username, the error "PuTTY Fatal Error: No supported authentication methods available (server sent: publickey)" occurred.
Jul 17 2020
Here is another thing worth reporting. I found that passphrase-repeat is entirely ignored, regardless of the value set.
Do you configured gpg so that you did not get a passphrase confirmation?
That could also be the reason for some strange behaviour I have sometimes with my bunch or readers. I have not had the time to look into this and thus opted for a gpgconf --kill scdaemon which fixes things quickly but of course this is a bad workaround.
C++ interface is also availabale in 1.14.0 (see rM690d967196d9).
I just learned that WSAStartup can be called multiple times. So, it doesn't cause any erroneous behavior which I had been afraid of.