Hi all,
I've been a rabidly-devout user of TheBat! for quite some time now,
and of course upgraded to version 2 the day it came out...
I've run into a few problems however, mainly with PGP.
(1) I'm using PGP 6.5i, and have noticed that some of the content of
the encrypted emails are going
Hi Dave,
@5-Sep-2003, 10:12 Dave Collins [DC] in
mid:[EMAIL PROTECTED] said to
TBUDL:
DC (1) I'm using PGP 6.5i, and have noticed that some of the
DC content of the encrypted emails are going missing.
... snip
DC If I copy the encrypted text and decrypt from the clipboard,
DC everything is
Hi Marck ,
Good to see you here :-)
MDP None at all. I haven't noticed anything like this going on. This
MDP wants reporting to the BT once the beta gets rolling for 2.00.1. I
MDP use 6.5.8ckt (and this is a very good release of 6.5 of PGP) and
MDP would be interested to try some private
Hello Thomas!
On 26 Dec 2001 at 04:37:47 you wrote:
You should have a problem? Damn, I don't! What am I doing wrong? ;-)
You quote out of context?! ;-)
PS: Are you really awake on Boxing Day at 4:30 in the morning
--
Dierk Haasis
http://www.Write4U.de
http://Interest.Write4U.de/pongo
PGP
Hi Dierk,
On Wed, 26 Dec 2001 10:51:12 +0100GMT (26/12/2001, 17:51 +0800GMT),
Dierk Haasis wrote:
DH You quote out of context?! ;-)
Of course. ;-)
DH PS: Are you really awake on Boxing Day at 4:30 in the morning
It may have been 4:30 where you live, but over here it was 11:30 and I
was
Hi list,
I'm using pgpn version 7.1 with the bat but i have following problem: if i
want to sign a message, i should be able to use PGP tray, option current
window/sign. The problem is that it's greyed out and i can not use it. So,
something is stealing the focus from
On 25 Dec 2001, at 20:38:48 [GMT +0100] (which was 20:38 where I live)
Luc wrote:
L I'm using pgpn version 7.1 with the bat but i have following problem: if i
You will need to install PGP 6.5.8 instead of 7.1; The API for 7.1 has
not been released, and therefore the developers at RITLabs
It was foretold that on 25/12/2001 at 22:15:47 GMT+0100 (which was 22:15 where I live)
Gerd Ewald wrote and spread these wise comments on the bat! and pgp problems:
Hmmm, although you are right concerning PGP 658 and TheBat, I
understood Luc in a different way:
he uses *PGPTray* of PGP7.1
It was foretold that on 25/12/2001 at 22:41:42 GMT+0100 (which was 22:41 where I live)
Dierk Haasis wrote and spread these wise comments on the bat! and pgp problems:
There are only two things that come to mind: Try a fresh install of
PGP. Or your version (I understand it is the original NAI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Dierk Haasis,
On Tuesday, December 25 2001 at 01:41 PM PDT, you wrote:
There are only two things that come to mind: Try a fresh install of
PGP. Or your version (I understand it is the original NAI version) has
a bug.
I think you are right
On Tue, 25 Dec 2001 20:38:48 +0100, Luc [L] wrote these comments:
...
L I'm using pgpn version 7.1 with the bat but i have following
L problem: if i want to sign a message, i should be able to use PGP
L tray, option current window/sign. The problem is that it's greyed
L out and i can not use it.
Hi Dierk,
On Tue, 25 Dec 2001 22:41:42 +0100GMT (26/12/2001, 05:41 +0800GMT),
Dierk Haasis wrote:
DH The only time you should have a problem with TB! concerning PGP is
DH with RITLab's plug-ins or the internal version.
You should have a problem? Damn, I don't! What am I doing wrong? ;-)
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Thomas,
I disagree. Ritlabs should offer a DLL with the correct version
number, or even better: a DLL that finds the correct version number.
Offering a DLL with a wrong version number is plainly wrong.
I pretty much agree with that. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Dierk,
It should have worked, see my version string.
Looks nice, I want to edit mine too! :-)
Maybe you just edited the version string in either the wrong DLL
6.5, I was told?
or the wrong place
That's what I assume. I don't really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Alexander!
On Friday, November 02, 2001 at 11:13:25 AM you wrote:
or the wrong place
That's what I assume. I don't really know where to edit what. Could
you maybe explain that to me in more detail? Off-list, maybe?
Actually I can't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Alexander!
On Wednesday, October 31, 2001 at 12:51:36 PM you wrote:
Why is that so? Couldn't that be corrected in a new dll?
Because at the moment - and it is a lng moment as of now - there
is no DLL with a correct version number. It
Hi Dierk,
On Wed, 31 Oct 2001 15:10:04 +0100GMT (31/10/2001, 22:10 +0800GMT),
Dierk Haasis wrote:
Why is that so? Couldn't that be corrected in a new dll?
DH Because at the moment - and it is a lng moment as of now - there
DH is no DLL with a correct version number. It doesn't make sense
Hello everybody,
I'm running 1.54 beta10 right now, but no different with 1.53t which I
used before.
I installed PGP 6.5.8 for NT (running Win2k). I had PGP 6.0.2
installed before. PGP itself works fine, I created my own private key
(a new one with 6.5.8, as I had some strange problems with the
Hello Alexander,
Wednesday, October 31, 2001, 10:49:48 AM, you wrote:
AL Why does it show 6.0.2i instead of 6.5.8??
You have to manually edit the pgp65.dll with a Hex-editor and replace
the version number (standard this is 6.5i as I recall correctly) with
6.5.8. Then if you sign a message
Hello David,
You have to manually edit the pgp65.dll with a Hex-editor
Why is that so? Couldn't that be corrected in a new dll?
and replace the version number (standard this is 6.5i as I recall
correctly) with 6.5.8.
Well, that didn't work. But if that is the only reason why the numbers
Hi there Nick,
Going back 18:13 27.10.2000. when you uttered the following thoughts:
I believe we are talking about two different things here: The fact that
not all MUA's observe the signature delimiter, so when replying, you would
have to reply to selected text only (eliminate the PGP
Hi there Gerd,
Going back 16:03 26.10.2000. when you uttered the following thoughts:
Christian already posted the improved regex. Another way is (although not really
a good one) Shift-Ctrl-D which verifies the signed message and produces a
"decrypted" version of the message without any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On October 27, 2000, at 8:42:46 AM, Johannes M. Posel Wrote:
Christian already posted the improved regex. Another way is (although
not really a good one) Shift-Ctrl-D which verifies the signed message
and produces a "decrypted" version of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Nick Andriash !
On Fri, 27 Oct 2000 09:13:13 -0700 GMT your local time,
which was 27.10.2000, 18:13 (GMT+0200) where I live, you wrote:
[...]
I think what Gerd is referring to, is decrypting an encrypted message and
not just a PGP signed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Dierk Haasis !
On Wed, 25 Oct 2000 19:18:02 +0200 GMT your local time,
which was 25.10.2000, 19:18 (GMT+0200) where I live, you wrote:
Haven't called it that. And this doesn't change the problem: Since the
signature delimiter is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Gerd!
On Thursday, October 26, 2000 at 4:03:40 PM you wrote:
Are you sure you have seen a "new" one or did you see a sig in TB! that says
"Version 6.5.8" like mine ? If so, I changed the DLL with an Hex-editor. So
there is nothing new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Christian!
On Tuesday, October 24, 2000 at 11:22:03 PM you wrote:
This is not a bug. PGP always does this.
Haven't called it that. And this doesn't change the problem: Since the
signature delimiter is not recognised the sig can't
Dierk Haasis wrote:
This is not a bug. PGP always does this.
Haven't called it that. And this doesn't change the problem: Since the
signature delimiter is not recognised the sig can't be stripped
automatically.
[...]
There's a fine regexp for this:
oneline
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello TBUDL Members!
I just wanted to summarize some of the problems we see with PGP and
TB!:
1. PGP adds "hyphen+space"
2. If one uses external PGP To show the right PGP version one has to
hack the DLL
3. Not all options of
Dierk Haasis wrote:
I just wanted to summarize some of the problems we see with PGP and
TB!:
1. PGP adds "hyphen+space"
This is not a bug. PGP always does this.
2. If one uses external PGP To show the right PGP version one has to
hack the DLL
Yes, it would be better if TB simply (?)
30 matches
Mail list logo