You could also put it in your ~/.kde/Autostart directory
On Tuesday, March 18, 2003 4:44 pm, Benoit Mortier wrote:
> Le Mardi 18 Mars 2003 21:37, Henning Moll a écrit :
> [..]
>
> > (gpg-agent outputs a little shell script that sets the environment
> > variable GNUPG_AGENT_INFO). You may want to a
Le Mardi 18 Mars 2003 21:37, Henning Moll a écrit :
[..]
> (gpg-agent outputs a little shell script that sets the environment variable
> GNUPG_AGENT_INFO). You may want to add this to your ~/.xsession or startkde
> so that all programs see the environment variable.
> ---
>
> ok, so i did. I've add
Hi!
Excerpt from http://kmail.kde.org/kmail-pgpmime-howto.html :
---
(gpg-agent outputs a little shell script that sets the environment variable
GNUPG_AGENT_INFO). You may want to add this to your ~/.xsession or startkde
so that all programs see the environment variable.
---
ok, so i did. I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
El Vie 04 Oct 2002 11:02, David Pashley escribió:
> On Friday 04 October 2002 2:33 am, bruno randolf wrote:
> > ok. sorry for my wrong post. i eventually took the time to read the gnu
> > privacy handbook. what i suggested was nonsense and dangerous. a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 04 October 2002 2:33 am, bruno randolf wrote:
> ok. sorry for my wrong post. i eventually took the time to read the gnu
> privacy handbook. what i suggested was nonsense and dangerous. and i'll
> never do something like that again, promised..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ok. sorry for my wrong post. i eventually took the time to read the gnu
privacy handbook. what i suggested was nonsense and dangerous. and i'll never
do something like that again, promised...
what lead me to this stupid workaround was the fact, that
On Thu, 3 Oct 2002 16:15, David Pashley wrote:
> trust yourself. I would be surpised if someone had managed to create a key
> which hadn't been self-signed.
They do that all the time. Just recently I went to a key-signing party and
one of the people there hadn't self-signed their key. I'm surpr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 03 October 2002 2:50 pm, David Pashley wrote:
> On Thursday 03 October 2002 1:19 pm, bruno randolf wrote:
> > i'm not sure if this is the problem in your case, but kmail only encrypts
> > to keys which are signed and trusted.
> >
> > so you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 03 October 2002 2:40 pm, Russell Coker wrote:
> On Thu, 3 Oct 2002 15:17, Ben Burton wrote:
> > > so you have to do
> > > gpg --edit-key
> > > Command> sign
> > > Command> trust
> > > Command> save
> >
> > No! You should only ever sign a
El Jue 03 Oct 2002 13:16, Hendrik Sattler escribió:
> Am Donnerstag, 3. Oktober 2002 11:30 schrieb José Manuel Pérez:
> > Hi all.
> >
> > I've got KDE 3.0.3 and gnupg 0.13-3 from Debian unstable. I've generated
> > my
>
>
> Huh:
> ii gnupg 1.0.7-2
> I was under the impression that the original message was about your own
> key, which you should sign (keys that aren't self-signed are worthless).
> Presumably you don't need to look at your own drivers' license.
Sure, but the message I quoted was regarding encryption which is generally
(thoug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 03 October 2002 1:19 pm, bruno randolf wrote:
> i'm not sure if this is the problem in your case, but kmail only encrypts
> to keys which are signed and trusted.
>
> so you have to do
> gpg --edit-key
>
> and then:
> Command> sign
> ...
>
On Thu, 3 Oct 2002 15:17, Ben Burton wrote:
> > so you have to do
> > gpg --edit-key
> > Command> sign
> > Command> trust
> > Command> save
>
> No! You should only ever sign a key if you can be sure the key belongs to
> the person who claims to own it. This generally means you have received
> th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> so you have to do
> gpg --edit-key
> Command> sign
> Command> trust
> Command> save
No! You should only ever sign a key if you can be sure the key belongs to the
person who claims to own it. This generally means you have received the key
(or i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i'm not sure if this is the problem in your case, but kmail only encrypts to
keys which are signed and trusted.
so you have to do
gpg --edit-key
and then:
Command> sign
...
Command> trust
...
Command> save
after that you are able to select the key
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 3. Oktober 2002 11:30 schrieb José Manuel Pérez:
> Hi all.
>
> I've got KDE 3.0.3 and gnupg 0.13-3 from Debian unstable. I've generated my
Huh:
ii gnupg 1.0.7-2GNU privacy guard - a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 03 Oct 2002 10:30 am, José Manuel Pérez wrote:
> Hi all.
>
> I've got KDE 3.0.3 and gnupg 0.13-3 from Debian unstable. I've generated my
> keys and configure kmail (1.4.3) in order to use gpg, but it never signs
> nor encripts my messages.
Hi all.
I've got KDE 3.0.3 and gnupg 0.13-3 from Debian unstable. I've generated my
keys and configure kmail (1.4.3) in order to use gpg, but it never signs nor
encripts my messages.
Someone knows what can I do? I don't get any error/warning message about it,
and I know gpg works ok.
Thanks i
On Sun, 1 Sep 2002 23:40, Tom Badran wrote:
> On Sunday 01 Sep 2002 9:25 pm, Russell Coker wrote:
> > Is there some way to reconfigure kmail to make it behave better? Or is
> > it just buggy?
>
> I have never had any problem with this across kde 1/2/3. Do you have an
> exceptionally large number o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 01 September 2002 9:25 pm, Russell Coker wrote:
> A problem that I have had with kmail in kde 2.0 and am now having with
> kmail in kde 3.0.3 is that it takes up lots of CPU time when launching gpg.
>
> When I do an operation that causes GPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 01 Sep 2002 9:25 pm, Russell Coker wrote:
> Is there some way to reconfigure kmail to make it behave better? Or is it
> just buggy?
I have never had any problem with this across kde 1/2/3. Do you have an
exceptionally large number of keys
A problem that I have had with kmail in kde 2.0 and am now having with kmail
in kde 3.0.3 is that it takes up lots of CPU time when launching gpg.
When I do an operation that causes GPG to take some time (IE re-calculating
the trust db because new signatures have been received for some keys) the
On Thu, Jan 17, 2002 at 06:00:24PM +0100, Laurent Rathle wrote:
> I've generated a key with 3 different UID with GPG. I affected each one to an
> identity in KMail. When I sign my message, KMail always use the same identity
> for the three. Is it possible to have a key with three UID with KMail
On Thu, Jan 17, 2002 at 06:00:24PM +0100, Laurent Rathle wrote:
>
> Hello,
>
> I've generated a key with 3 different UID with GPG. I affected each one to an
> identity in KMail. When I sign my message, KMail always use the same identity
> for the three. Is it possible to have a key with three U
Hello,
I've generated a key with 3 different UID with GPG. I affected each one to an
identity in KMail. When I sign my message, KMail always use the same identity
for the three. Is it possible to have a key with three UID with KMail ?
Thank you
--
[EMAIL PROTECTED]
On Thu, 18 Oct 2001 17:05, David Bishop wrote:
> You probably had that problem before I remembered I hadn't uploaded my key
> to the keyservers :-) I put all three of them on the mit keyserver about
> three weeks ago, so anyone that uses it or any mirrors should be okay. Of
> course, if you add t
t that I
> > look at to try and solve the problem?
The only remaining problems I have with kmail and gpg is when someone has a
huge multiply-signed key (like Marc Mutz), where even though I have his
public key, it takes about 6 seconds just to process it on a Piii733. That
is being worked on for t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 18 Oct 2001 12:40 am, Hendrik Sattler wrote:
> Am Donnerstag, 18. Oktober 2001 00:58 schrieb Russell Coker:
> > I notice that you are sending PGP/GPG signed email with kmail, so I
> > presume that it's working OK for you.
> >
> > When I see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 18. Oktober 2001 00:58 schrieb Russell Coker:
> I notice that you are sending PGP/GPG signed email with kmail, so I presume
> that it's working OK for you.
>
> When I see your messages GPG takes ages to process the signature (a minute
>
I notice that you are sending PGP/GPG signed email with kmail, so I presume
that it's working OK for you.
When I see your messages GPG takes ages to process the signature (a minute or
more on a P3-650). So I generally run "killall gpg" in another window.
How do you find gpg performance with km
30 matches
Mail list logo
