Agreed for the manual page. We will think about this.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 19 2009
Am sorry about this. This is an unslved problem existing in GpgOL for years.
In some cases Outlook somehow caches the content of the Window or syncs it back
to MAPI. I have found no way to reliable avoid that. GpgOL does all kinds of
tricks to avoid this but it is not bulletproof.
I leave this decision to you. I agree to the reporter, that everything is a bit
"wildly" ordered atm. However, I cannot speak for an unexperienced user. I've
asked the reported for feedback/his opinion.
Duplicate of T1107
Same as 1107, please see there.
It is only shown on the very first start. FWIW:
Hmmm. I didn't notice the hint at the first startup.
I received an encrypted email (encrypted by gpgol 0.9.92) which used to work in
OL2003. When decrypting the email I had to pass the passphrase and the email has
been display decrypted in the very same window. Closing the window the email was
still left encrypted.
Using gpgol 1.0.0 the email has been decrypted the first time. Since then when
moving to the email no text could be seen, the passphrase has to entered (the
first time visiting the email) and the email was display decrypted as long as I
didn't close OL. Since deinstalling gpg4win the email is decrypted! The only
difference I noticed is that the icon changed from "read mail" to "unread mail"
and even doesn't change to "read" when the email is left.
That would be hard to implement. Consider that an alpahbetic order makes most
sense only to English speaking users, whereas others will likely use the
translated description.
I can duplicate this and found a way to fix it. However that fix would bring
back a problem with the outlook window not being repainted. I am a bit puzzled
that nobody found this problem since it must have been tehre since gpg4win
1.9.14 from March.
Can you please give some details? The de-installation does not touch your data
files or messages.
Aug 18 2009
I can now make gpg key backup during generated key directly on the opengpg V2
smartcard.
Escchange does not work - that is as expected. GpgOL even tells about this
during its first startup.
Note that
http://lists.wald.intevation.org/pipermail/gpg4win-users-en/2009-August/000340.html
reported a recpient not found problem with OL2007, MS Exhange 2003 and
2.0.0rc1.
Ap,
can you state the version of Exchange you have been successful with?
You have used Gpg4win 1.9.14-Beta back then, if you happen to try 2.0.0
can you repeat the findings?
The installation also was Exchange based.
This is the built-in reader in my Dell Latitude D430, by the way.
This is the relevant lsusb output:
We don't continue 0.9.x. Thus I don't want to fix that problem unless you have
a real need for it.
This is probably due to wrong MIME headers or internal conversions by Outlook
which break the signature. This old version of GpgOL has a limited MIME parser.
With version 1.0 as included in Gpg4win 2.0 we have a complete MIME parser and
your problem might be solved.
Note that issue#1019 states that encryption works with XP and OL2007 - There was
no change in the mIME stuff since then.
Sorry, as stated in the README this does not work. I need to find a bit of time
to play with Exchange to figure out the right way to order the MIME headers.
There is no guarantee that I will succeed, though.
Fixed in svn 5123. I fixed that a year ago in trunk and forgot to backport it.
Fixed again. (svn 5122).
I'm using an Exchange base account.
Indeed, I applied it only to gnupg-2. Applied it to 1.4 now.
Ooops, I missed to copy the included files. I added a new make traget to assist
me in the future.
What card reader are you using?
Aug 17 2009
No, in that case you are already using GPA.
Hi, thanks for the quick reply, I'm not using Kleopatra, I tried gnupg4win lite
and had the same issue.
The delay is not in encrypting, the delay is in opening ANY outlook attachment
(I havent even tried encrypted attachments yet).
Is it still worth trying your diagnostics even though I'm not using Kleopatra ?
Kind regards,
Matt.
Are you using a local account, IMAP or an Exchange based account?
Are you using Kleopatra? If so, please try this:
Aug 14 2009
2009-04-02 Till Adam <till@kdab.net>
Unfortunately still not fixed in 1.4.10 rc1.
Sorry, this was the wrong report. #917 is still open.
Seems to has been missed to be synced. Issue is still there in 1.4.10 rc1.
Seems to has been missed to be synced. Issue is still there.
It seems, the buggy translation had been reintroduced:
Aug 13 2009
Hi Marcus,
On Thu, Aug 13, 2009 at 01:29:26PM -0000, Marcus Brinkmann via BTS wrote:
Marcus Brinkmann <marcus@g10code.com> added the comment:
I don't see a reason to apply the patch, there are no po files generated for
pinentry. Is this to sync our copy of gtksecentry of another project? I
checked krb5-auth-dialog in Ubuntu, and it does not have this patch.
The patch is in krb5-auth-dialog's upstream. Ubuntu is lagging as
usual, Debian has it.
I don't see a reason to apply the patch, there are no po files generated for
pinentry. Is this to sync our copy of gtksecentry of another project? I
checked krb5-auth-dialog in Ubuntu, and it does not have this patch.
Quite right, claws actually does invoke AC_SYS_LARGEFILE.
Aug 12 2009
Did 1.4. Will do 2.0 shortly, after a bit of testing.
Aug 11 2009
Okay - So I installed as you specified. Upon running and creating the key and backup of the
key I had another error that called my VS debugger. I'm not very current on assembler so I have
attached the output trace in a text file.
Sorry, typo in the URL, (there was one "kolab/" too much, but you could have
gotten to it via the main page. :) )
https://www.intevation.de/roundup/kolab/issue3583 (offline s/mime signing
without CRL for secret key gives unkown system error)
Sorry for the delay. I can not access the kolab tracker (404), has the link
changed? Errors for individual keys in a keylisting are not available in
detail, but only the invalid flag is set. When using an invalid key, a more
detailed reason may be available. There is currently no way to get more
detailed reasons about why a key in a key listing is invalid.
Well that is gpg4win ;-).