When I use PGPcmdline (version 6.5.8) in an XP Command window to
decrypt a file created with PGP 6.5.2a, after entering the keyword,
the system works for about 20 seconds, a 24 MB xxx.$00 file is created
during this time, then the command prompt reappears, the .$00 file
disappears but NO decrypted file is created and no error messages are
given. This has worked for years in the past. What must I do to
decrypt my file? |
Request for Question Clarification by
endo-ga
on
04 Jun 2003 21:38 PDT
Hi,
Have you tried with the extra switch '-o outfile' to save the output
in a file called outfile. If so, what are the results of that?
Thanks.
endo
|
Clarification of Question by
movrshkr-ga
on
05 Jun 2003 05:23 PDT
Yes, I have used the "-o outfile" option.
The encrypted files are created with PGP 6.5.2a.
(1) In the past, before moving to a XP machine, I used the PGP 6.5.8
command line utility with the -d -o and -z switches to decrypt these
files. In verbose mode, after the temp file is created, the following
error is shown: event 3: error -11391. I can find no documentation
for this error.
(2) I have tried using the latest PGP version, 8.0, to manually
decrypt, and I get a "Bad Packet" error. An output file is created,
but it contains only about 90%, 24MB, of the expected ouput.
(3) I have also tried using GnuPG, but it fails to produce any output.
|
Request for Question Clarification by
endo-ga
on
05 Jun 2003 06:08 PDT
Is this a problem with only a given specific file or all files?
If so, you might want to consider either restoring the file from your
source in case it is corrupted, either from a backup or from wherever
it came from (email, web...).
I'll have a look for the errors you mention in a bit.
Thanks.
endo
|
Clarification of Question by
movrshkr-ga
on
05 Jun 2003 07:13 PDT
I have an archive of older encrypted files from the same source: PGP
command line still works for them. The problem is present for all
recent files. For a while I thought the problem might arise from
having installed WinXP Pro, but, as I said above, PGP command line
still works for the old files.
By the way, THANK YOU for looking into this problem!
-- Bill Jones
|
Request for Question Clarification by
endo-ga
on
05 Jun 2003 08:55 PDT
Could you possible upload one of these files somewhere so I can play
around with it? And also provide me with the key if that isn't a
problem, if it is, is it possible to create a new file with a new key
you wouldn't be using later?
If you need a place to upload you could use:
ftp.membres.lycos.fr
username: dbky
password: googleanswers
Thanks.
endo
|
Clarification of Question by
movrshkr-ga
on
05 Jun 2003 09:10 PDT
endo,
Unfortunately, I cannot send you a copy of one of these files: it is
proprietary confidential financial information. Also, because the
problem is almost certainly due to some change at the source of the
data, it would make no sense for ME to encode something here. I
repeat: the source is encrypted with PGP 6.5.2a -- an OLD OLD version
of PGP of which I do not even have a copy!
Again, thank you for your efforts.
--Bill Jones
|
Request for Question Clarification by
endo-ga
on
07 Jun 2003 09:07 PDT
Hi,
Sorry for taking such a long time to get back to you.
Could you please try PGP 6.5.2a and see if it works for your files:
http://www.pgpi.org/cgi/download.cgi?filename=PGPfreeware652a.zip
Assuming that you can install and run PGP 6.5.2a and that this is the
same version you used to encrypt your files, and this still doesn't
work, even on another PC, then your files must be corrupted, and
there's not much you can do about that, except try and recollect them
from your source. Have they been stored on a cd-r that was left in
sunlight or on a floppy?
Sorry for not being more helpful.
Thanks.
endo
|
Clarification of Question by
movrshkr-ga
on
07 Jun 2003 10:26 PDT
Endo,
Thank you for your attention to this problem. I will be putting
together another machine this week. When it's ready, I'll put PGP
6.5.2a (thanks for the link!) and try it.
One other piece of information: when I use PGP 8 to decrypt the new
files, it halts with a "Bad Packet" error; but, it APPEARS that only
the last expected line, the one beginning with Z1UTRL (Z1UTRL
00223387, for example) is the only line missing from the decrypted
output.
This means that I can get my data, but not by "Shelling out" from my
application. So, the pre-processing of the data can no longer be a
mechanized process. Also, there is still the lack of certainty that I
*am* getting all the data except that last Z1UTRL line.
Thanks again.
Bill Jones
|
