works
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 28 2023
works
Sep 27 2023
works
works, VS-Desktop-3.2.0.0-beta214
This is NOT the bug reporting form. You will find the form at https://dev.gnupg.org/maniphest/task/edit/form/5/
Edit: The text below was wrong. The error given below only occurs when the combined path+filenmae is to long on windows.
An emoticon in a file below the folder to be encrypted does not hinder encryption via GpgEX.
Sep 26 2023
works, tested with VS-Desktop-3.2.0.0-beta214.
For the remaining issue with a certain date range see T6736
The choice in the calendar "widget" changed to in 1/2/3 years in all cases. Those options work but the last choice "no date" has no effect.
Works, setting "compatibility-flags vsd-allow-ocb" in the gpg.conf causes new keys to be generated with the AEAD feature flag OCB. And encryption to that key then uses OCB mode as long as the compatibility-flags is set.
Sep 25 2023
Sep 22 2023
Encryption to the ADSK seems to work but I'm not sure if everything is displayed as expected.
How about adding "-2" to a document where before _signed already was in the name, i.e. foo_signed.pdf -> foo_signed-2.pdf and so on: foo_signed-3.pdf, ...
works with VS-Desktop-3.2.0.0-beta214, too.
You are now informed that you do not have permissions to write there.
For VS-Desktop-3.2.0.0-beta214 this does not work yet. If a keystub exists, it is not overwritten.
Kleopatra now shows:
Sep 21 2023
works in 22, too (tested with VS-Desktop-3.2.0.0-beta214)
Does not work yet on VS-Desktop-3.2.0.0-beta214:
Tested in VS-Desktop-3.2.0.0-beta214 by encrypting a large file with Kleopatra. The progress bar shows percentage finished, progress looks all right
I've added a footnote in the VSD user documentation regarding this difference as a very minimal measure and a reminder for support.
Could we then clarify this for the user somehow? Maybe both
a) add "Sign/Encrypt Folder" to the default menu bar - it would need an icon added for that, too
b) make it clear in the documentation
Sep 20 2023
For clarification: encrypting a file via Kleopatra (not GpgEX) with unicode characters in name works, only the folders don't
This is as intended, in Kleopatra you either encrypt files or folders (via File-> Sign/Encrypt Folder).
Sep 19 2023
Sep 18 2023
Tested on the command line with
- a previously valid certificate after setting its root certificate to untrusted
- a expired certificate without the root certificate in the certificate list
With Gpg4win-4.2.1-beta31 I can no longer import the secret part of the edward.tester@demo.gnupg.com.p12 Testkey. Error is "Invalid object".
With VS-Desktop-3.2.0.0-beta214 and Gpg4win-4.2.1-beta31 the error is "Bad Passphrase" in this case.
I do not see a reason why this ticket is still open.
The already resolved Kleopatra Task T5713 is probably a duplicate of this one.
Sep 14 2023
pkcs12 import should be backported, too
Sep 13 2023
andre said this can not be left like this, on windows the name needs to be "Archive (1).tar.gpg", like in Linux.
In the VSD Testversion:
This did not fix the issue on Windows.
Sep 12 2023
works
Yes the error message is better now. In German it is "Entschlüsseln fehlgeschlagen: Fehlerhafte Daten." Which could be a bit more clear, but its ok
well yes, it ends now in "_signiert.pdf" with German language settings and "_signed.pdf" in English.
ok, with the new testversion VS-Desktop-3.2.0.0-beta214 and without Debug redirection (mea culpa), the info window looks like this:
And Debugview shows:
Sep 8 2023
My issue was that it makes no sense to publish a revocation of a local certification...
I'm fine with it in the case if the certification was exportable.
Sep 7 2023
this works now:
Tested at first with GnuPG-VS-Desktop-3.2.0.0-beta178 from 2023-08-29
Sep 6 2023
In T5960#175317, @ikloecker wrote:The previous two changes will hopefully fix the error output of export to server. I'm not entirely sure about the missing line breaks.
In T5960#175318, @ikloecker wrote:Also, please retest T5960#172860 with the latest build.
Another customer case with "always show security-dialog" on (-> external resolver):
Sep 5 2023
[2188] org.kde.pim.libkleo: gpgConfGetConsoleOutputCodePage starting "C:\\Program Files x86)\\GnuPG VS-Desktop\\bin\\..\\GnuPG\\bin\\gpgconf.exe" --show-codepages [2188] org.kde.pim.libkleo: gpgConfGetConsoleOutputCodePage returns 0
[1400] org.kde.pim.kleopatra: "C:\\Program Files (x86)\\GnuPG VS-Desktop\\GnuPG\\bin\\gpg.exe --send-keys 3A12118AD7F4CBB6FF38C6B8F615AD82F702FA1F gestartet ..." [1400] org.kde.pim.kleopatra: "gpg: NOTE: THIS IS A DEVELOPMENT VERSION!\r\ngpg: It is only intended for test purposes and should NOT be\r\ngpg: used in a production environment or with production keys!\r\ngpg: enabled debug flags: memstat trust extprog\r\ngpg: enabled compatibility flags:" [1400] org.kde.pim.kleopatra: "gpg: sende Schlüssel F615AD82F702FA1F auf ldap://" [1400] org.kde.pim.kleopatra: "gpg: Senden an Schlüsselserver fehlgeschlagen: Ungültige LDAP Credentials\r\ngpg: Senden an Schlüsselserver fehlgeschlagen: Ungültige LDAP Credentials\r\ngpg: keydb: handles=1 locks=0 parse=1 get=1\r\ngpg: build=0 update=0 insert=0 delete=0\r\ngpg: reset=0 found=1 not=0 cache=0 not=0\r\ngpg: kid_not_found_cache: count=0 peak=0 flushes=0\r\ngpg: sig_cache: total=2 cached=2 good=2 bad=0\r\ngpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0\r\n outmix=0 getlvl1=0/0 getlvl2=0/0\r\ngpg: rndjent stat: collector=0x00000000 calls=0 bytes=0\r\ngpg: secmem usage: 0/32768 bytes in 0 blocks"
Found in GnuPG-VS-Desktop-3.2.0-beta178, broken ü and no linebreaks:
Sep 4 2023
Aug 18 2023
Backport to VSD, as leaving out WKD is a bug.
result from meeting: