On Sunday 04 June 2006 07:54, Todd Zullinger wrote:
> Ingo Klöcker wrote:
> > On Saturday 03 June 2006 04:57, engage wrote:
> >> On Thursday 01 June 2006 08:59 pm, Todd Zullinger wrote:
> >>>engage wrote:
> Why is someone sending an encrypted message to this list?
> >>>
> >>>It's not encrypted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ingo Klöcker wrote:
> On Saturday 03 June 2006 04:57, engage wrote:
>> On Thursday 01 June 2006 08:59 pm, Todd Zullinger wrote:
>>>engage wrote:
Why is someone sending an encrypted message to this list?
>>>
>>>It's not encrypted. It's just signed
Hello Ingo,
Saturday, June 3, 2006, 9:19:36 PM, you wrote:
> On Saturday 03 June 2006 04:57, engage wrote:
>> On Thursday 01 June 2006 08:59 pm, Todd Zullinger wrote:
>> >engage wrote:
>> >> Why is someone sending an encrypted message to this list?
>> >
>> >It's not encrypted. It's just signed a
On Saturday 03 June 2006 04:57, engage wrote:
> On Thursday 01 June 2006 08:59 pm, Todd Zullinger wrote:
> >engage wrote:
> >> Why is someone sending an encrypted message to this list?
> >
> >It's not encrypted. It's just signed and armored.
> >
> >Doesn't your mail client automatically display th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
engage wrote:
> On Thursday 01 June 2006 08:59 pm, Todd Zullinger wrote:
>>engage wrote:
>>> Why is someone sending an encrypted message to this list?
>>
>>It's not encrypted. It's just signed and armored.
>>
>>Doesn't your mail client automatically d
On Thursday 01 June 2006 08:59 pm, Todd Zullinger wrote:
>engage wrote:
>> Why is someone sending an encrypted message to this list?
>
>It's not encrypted. It's just signed and armored.
>
>Doesn't your mail client automatically display this for you?
No. I keep getting prompted for my passphrase f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Brown wrote:
> On Thu, Jun 01, 2006 at 10:59:54PM -0400, Todd Zullinger wrote:
>> engage wrote:
>>> Why is someone sending an encrypted message to this list?
>
>> It's not encrypted. It's just signed and armored.
>
>> Doesn't your mail client a
* Laurent Jumet <[EMAIL PROTECTED]> wrote:
> > Many mail clients will assume that any GPG message is encrypted and
> > prompt for a passphrase prior to invoking GPG.
>
> Are you sure?
> Security wouldn't be compromised if passphrase is given to anything else
> then gpg?
F.e. mutt itself
On Thu, Jun 01, 2006 at 10:59:54PM -0400, Todd Zullinger wrote:
> engage wrote:
> > Why is someone sending an encrypted message to this list?
> It's not encrypted. It's just signed and armored.
> Doesn't your mail client automatically display this for you?
Many mail clients will assume that any
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello !
Mark Brown <[EMAIL PROTECTED]> wrote:
>> > Why is someone sending an encrypted message to this list?
>> It's not encrypted. It's just signed and armored.
>> Doesn't your mail client automatically display this for you?
> Many mail clien
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
engage wrote:
> Why is someone sending an encrypted message to this list?
It's not encrypted. It's just signed and armored.
Doesn't your mail client automatically display this for you?
- --
ToddOpenPGP -> KeyID: 0xD654075A | URL: www.pobox
Why is someone sending an encrypted message to this list?
On Wednesday 31 May 2006 09:12 pm, Alphax wrote:
>-BEGIN PGP MESSAGE-
>Version: GnuPG v1.4.4-svn4147:IDEA-TIGER192-DSA2 (MingW32)
>
>owNCWmg2MUFZJlNZeXIg9QABDH/3mvZv7d3u1u7+6/9u9+fv7zbr3P+Y
>et9XR/NAAbdzYbgyhoAA0aGgAAAB6gAAA
Hello !
Sven Radde <[EMAIL PROTECTED]> wrote:
>>> But this is logical, isn't it?
>>> You don't trust a key (what's there to trust?). You trust the fact that
>>> *a certain key belongs to a certain user-id* and if new ids are added,
>>> you would have to think again if the owner of the key actuall
-BEGIN PGP MESSAGE-
Version: GnuPG v1.4.3 (MingW32)
owNCWmg2MUFZJlNZi1q7vwABAn/3/lJiuvJnV7X9/gxyP+/f4whZQALBEpCCgYQQ
QBshMAFlQQaghT2kwpkPUZAekAPUAAAD0mmQeo9IB6mjTQeo9qnqDUyTAjQjJppN
qmn6oAB5Tyh6IAMgAADyjygD1BkOGgGgANAaA0AAADTRpoAyAAAaNMgx1aBLX3en
1PYzeWxPmZ31iEAjwF6YzDunLCUGzjBsaVxPa4PT98n
-BEGIN PGP MESSAGE-
Version: GnuPG v1.4.3 (MingW32)
owNCWmg2MUFZJlNZLMzs4gABJn//+nIoAvQXV7X9/EYAP///4QTQSoJBJo7hAQKA
EAAYAogwAYltKwamplJtNJ7UmJ6gNMQ9IMEA0aNoIbUaAaaMGk9IYyDU0mBNAKZN
Gg0AAeoBoA00NBkAaCEp5I/VG0yhkNBoaA0yAGgAANB0L26igoXVF92F
EW5m9AAD3g6khlhsgcvJru0hRj/8XZzD+ggTIjgCGcE
-BEGIN PGP MESSAGE-
Version: GnuPG v1.4.3 (MingW32)
owNCWmg2MUFZJlNZvE3tWgAByP/3+nYhAmBn//X//92YP+f/4RBBRo3MIoeA0kAA
i0oQQAJHZ3cZxcImkmFPGqaep5Q9TQ2piZPUNPUeoAGhoZAGQB6hoHqGQNPRP1Qi
aAphkp5DTJMmQaNAADRoABqp+TRGpiNI9INAGgaBpoAAAGgAAAan
pRlTyNED0jIzUAaBoBoDQ0AGQGgaBAyIhXffQNN
Alphax wrote:
> Laurent Jumet wrote:
>> Hello !
>>
>> Charly Avital <[EMAIL PROTECTED]> wrote:
>>
>>> This is a bit strange.
>>
>> You mean that you cannot read compressed (not crypted) messages.
>>
>>
>
> eg. a message produced with gpg -a -s?
>
Sorry, I should also have pointed out th
-BEGIN PGP MESSAGE-
Version: GnuPG v1.4.4-svn4147:IDEA-TIGER192-DSA2 (MingW32)
owNCWmg2MUFZJlNZeXIg9QABDH/3mvZv7d3u1u7+6/9u9+fv7zbr3P+Y
et9XR/NAAbdzYbgyhoAA0aGgAAAB6gAAANBoAaDQAPUAAAD1AAAGgGgPKBo9TE09
T0nptUKqaep6npDQGgyD0gDQGjQA9TIAaGgaADIAaaaABpiAGgANABoyaAADTQNG
mgiqeRGwk0bUDIGT
Hello !
Charly Avital <[EMAIL PROTECTED]> wrote:
> This is a bit strange.
You mean that you cannot read compressed (not crypted) messages.
--
Laurent Jumet
KeyID: 0xCFAF704C
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.
-BEGIN PGP MESSAGE-
Version: GnuPG v1.4.3 (MingW32)
owNCWmg2MUFZJlNZ4Z2JuQAAwf/3+nMgAmAHT5it/FeAv+//40NAwGDARoAEgFV8
CI6IMAEyRBqqf6iJ5Gp6JiMTTaTQ0xGmZCPSZqGTIyPSbQ1MCNPJk0GpoJhQyYU0
yepkAaDTQAZNDQAAZAaAGg40MmmmTQAMEAaDJoABk0AAAMmQDRE1RVa1+7VU/UdD
MbWeAN1UaDZBbKaN8sm9Pfvik8anY5UA0w1urZgFsq/
20 matches
Mail list logo
