-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick,
NA> Peter, are you using GPG through TB!'s Plugin?
yes
NA> If so, how did manage to change the comment line?
Simply via the "Preferences" dialog of GnuPGshell, in the GnuPG...
section there is a [comment] entry. Text filled in there will sho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rob,
R> error-message : "no default secret key ; secret key not available"
R> no problems signing with GnuPG from the command-line or with GnuPGShell.
may be this is a bug with v1.52 - try the latest beta (1.52f) from
http://www.ritlabs.com/the_bat/
Hello George,
GFS> Were the certificates you are encrypting to properly exported with the
GFS> ability of encryption enabled?
yes, have checked that twice, the certificate does have the ability of
public key encryption ...
could you please have a look at your mail directory:
do you have a file
Dave,
>> signing of msgs works fine, encryption doesn't work,
>> all I get is:
>> access violation at address 0050AB6A. Read of address
>> any hints?
DM> Cycle TB and try it again :)
already done, no effect ...
DM> There seems to still be some "holes" in the certificate support for
D
Hi,
evaluting S/MIME functions got the following problem:
signing of msgs works fine, encryption doesn't work,
all I get is:
access violation at address 0050AB6A. Read of address
any hints? (all certs present, S/MIME activated (switches don't
matter), PGP not activated ...)
/pk
---
5 matches
Mail list logo