Mailing List Archive

On Wed, 27 Jan 1999, Steven Bakker wrote:

> I found the same problem. Haven't investigated too much, but is this
> a platform specific problem (like, Solaris), or common to all builds?

I should check on the FreeBSD box today. I was developing on a Linux box,
and my FreeBSD box built without any problems, but that was after I
applied my little patch. I also noticed an autoconf error fly right by,
but I absolutely forgot to investigate it..

On another note, I haven't had a chance to read completely through the
list archives, so maybe someone can direct me to an URL if it's already
been discussed, but has anyone had problems with gpg integration with Pine
4.05?

It took me about 5 minutes to figure out the correct display-filters and
sending-filters settings, so that's not the issue. Taking the example of
signature verification, if I view a PGP signed message in Pine (4.05) on
one of my Linux boxen, everything seems to operate as advertised; I see
the original message, minus '---- BEGIN' erratum and signature, with 'Good
signature.*' or 'BAD signature.*' and related messages. However, if I use
it on a FreeBSD box, everything disappears -- the window is blank except
for the header. Similarly, if I try to decrypt a message, it actually
returns some error and won't even complete without error. (Working from
the command prompt, however, verifies that gpg works as advertised.)

I figure this is not gpg's fault, after quickly scanning log_info(). I'm
pretty sure this is a Pine issue. Not having yet had time to pull down
the Pine source and hack around with it, I was curious -- has anyone else
had similar problems?

Cheers,


Jordan Ritter
Network Security Engineer
Ring-Zero, Netect, Inc. Boston, MA

"Quis custodiet ipsos custodes?"

Jordan Ritter <jpr5@darkridge.com> writes:

> the original message, minus '---- BEGIN' erratum and signature, with 'Good
> signature.*' or 'BAD signature.*' and related messages. However, if I use

Don't rely on these patterns but the one which --status-fd 2 prints.

On Wed, Jan 27, 1999 at 09:31:12AM +0000, Steven Bakker wrote:

> >>>>> On Tue, 26 Jan 1999, "JR" == Jordan Ritter wrote:
> JR> I also came across some weirdness in the make [dist]clean rule for
> JR> the stuff in 'intl/'. I commented out the libintl.h rule and that
> JR> seemed to fix it.
> I found the same problem. Haven't investigated too much, but is this a
> platform specific problem (like, Solaris), or common to all builds?
> Similarly, I noticed that the generated makefile on a Solaris 7 machine
> no longer adds the "-lsocket -lresolv" mantra when linking. To my
> recollection, 0.9.1 did add it. Is this also happening on earlier Solaris
> versions, or is it simply that autoconf doesn't recognise Solaris 7 as
> Solaris?
> (Anyway, it's easy to fix by hand in g10/Makefile.)

nope failed for me too (under 2.6)

Steve

--
NetTek Ltd tel +44-171 483 1169 fax +44-181 444 6103
Flat 2, 43 Howitt Road, Belsize Park, London NW3 4LU
Epage steve-pager@gbnet.net [body of text only]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 27 Jan 1999, Werner Koch wrote:

> Jordan Ritter <jpr5@darkridge.com> writes:
>
> > the original message, minus '---- BEGIN' erratum and signature, with 'Good
> > signature.*' or 'BAD signature.*' and related messages. However, if I use
>
> Don't rely on these patterns but the one which --status-fd 2 prints.

It was only an observation of what constituted valid behaviour, and not
really an assessment of the validity of the content. Remarkably, if I set
- --status-fd 1, I at least get the [gnupg] messages, but everything else is
still lost.

I take it, by lack of response, that noone knows what I'm talking about.
I'll toy around with it and see if I can come up with a solution.


Jordan Ritter
Network Security Engineer
Ring-Zero, Netect, Inc. Boston, MA

"Quis custodiet ipsos custodes?"

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv

iQA/AwUBNq9TaCktN7QjnWKjEQIR2ACeLr9SFxCANOkc1LLWjL+VuH4MAEAAoP+Z
w8pTHzTKkMw7JNufZNNOugmu
=oBRE
-----END PGP SIGNATURE-----