Debian bug report logs - #958, boring messages

Message sent to debian-devel@pixar.com:

Subject: Bug#958: pgp PubRing SecRing and RandSeed don't work
Reply-To: andrew@kryten.it.com.au (Andrew Howell), debian-bugs@pixar.com
Resent-To: debian-devel@pixar.com
Resent-From: andrew@kryten.it.com.au (Andrew Howell)
Resent-Sender: iwj10@cus.cam.ac.uk
Resent-Date: Wed, 07 Jun 1995 18:33:02 GMT
Resent-Message-ID: <debian-bugs-handler.958.060718305323106@pixar.com>
Message-Id: <m0sJPr2-000AdQC@kryten.it.com.au>
From: andrew@kryten.it.com.au (Andrew Howell)
To: debian-bugs@pixar.com
Date: Thu, 8 Jun 1995 02:29:24 +0800 (WST)
Content-Type: text
Content-Length: 1084

Package: pgp-i
Version: 2.6.2i-1

[kryten:/home/andrew] pgp -kv
config.txt: unknown keyword: "PubRing"
config.txt: unknown keyword: "SecRing"
config.txt: unknown keyword: "RandSeed"
/usr/lib/pgp-i/config.txt: Maximum level of 3 error(s) detected

When I uncommented these settings in /etc/pgp-i.conf so I could have
my public and secret rings in ~/.pgp but not have to put a copy of
all the other pgp files there as welli, it didn't like it.

I had PGPPATH set to /usr/lib/pgp-i/

For now I guess I'll set PGPPATH to ~/.pgp and makes links in that
directory back to the files in /usr/lib/pgp-i/ so I don't need
unneccesary copies of the files.

Andrew

-----------------------------------------------------------------------
Dehydration - 34%, Recollection of previous evening - 2%, embarrassment
factor - 91%.  Advise repair schedule:- off line for 36 hours, re-boot
startup disk, and replace head - wow, what a night!
                -- Kryten in Red Dwarf `The Last Day'

Andrew Howell				               andrew@it.com.au
Perth, Western Australia		      howellaa@cs.curtin.edu.au

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: andrew@kryten.it.com.au (Andrew Howell)
Subject: Bug#958: Acknowledgement (was: pgp PubRing SecRing and RandSeed don't work)
In-Reply-To: <m0sJPr2-000AdQC@kryten.it.com.au>
References: <m0sJPr2-000AdQC@kryten.it.com.au>

Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#958" or "Re: Bug#958" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

Message sent to debian-devel@pixar.com:

Subject: Bug#958: pgp PubRing SecRing and RandSeed don't work
Reply-To: iwj10@cus.cam.ac.uk (Ian Jackson), debian-bugs@pixar.com
Resent-To: debian-devel@pixar.com
Resent-From: iwj10@cus.cam.ac.uk (Ian Jackson)
Resent-Sender: iwj10@cus.cam.ac.uk
Resent-Date: Sat, 10 Jun 1995 19:03:02 GMT
Resent-Message-ID: <debian-bugs-handler.958.061019001528079@pixar.com>
Message-Id: <m0sKPq3-0000XfZ@chiark.al.cl.cam.ac.uk>
Date: Sat, 10 Jun 95 13:40 BST
From: iwj10@cus.cam.ac.uk (Ian Jackson)
To: debian-bugs@pixar.com

Andrew Howell writes ("Bug#958: pgp PubRing SecRing and RandSeed don't work"):
> [kryten:/home/andrew] pgp -kv
> config.txt: unknown keyword: "PubRing"
> config.txt: unknown keyword: "SecRing"
> config.txt: unknown keyword: "RandSeed"
> /usr/lib/pgp-i/config.txt: Maximum level of 3 error(s) detected
>
> When I uncommented these settings in /etc/pgp-i.conf so I could have
> my public and secret rings in ~/.pgp but not have to put a copy of
> all the other pgp files there as welli, it didn't like it.

It works for me.  You haven't actually sent me a copy of your
/etc/pgp-i.conf, but I suspect you've made a syntax error - for
example, missing out the double quotes that should surround the value.

> I had PGPPATH set to /usr/lib/pgp-i/

That seems to me to be an unwise thing to do, at the very least.

PGPPATH is supposed to be the directory containing your *private* PGP
files, which are not system-wide.  I'd be inclined to say that the
fact that PGP is willing to accept pubring, secring and randseed
keywords in the system-wide configuration file is something of a
misfeature - people shouldn't do that.

> For now I guess I'll set PGPPATH to ~/.pgp and makes links in that
> directory back to the files in /usr/lib/pgp-i/ so I don't need
> unneccesary copies of the files.

Unnecessary copies of which files ?  config.txt ?  It's only 4.3Kb !
The other stuff (keyrings and so forth) should be in your home
directory.

Ian.

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: iwj10@cus.cam.ac.uk (Ian Jackson)
Subject: Bug#958: Info received (was Bug#958: pgp PubRing SecRing and RandSeed don't work)
In-Reply-To: <m0sKPq3-0000XfZ@chiark.al.cl.cam.ac.uk>
References: <m0sKPq3-0000XfZ@chiark.al.cl.cam.ac.uk>

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developers to
accompany the original report.

If you wish to continue to submit further information on your problem,
please do the same thing again: send it to debian-bugs@pixar.com, ensuring
that the Subject line starts with "Bug#958" or "Re: Bug#958" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

Message sent to debian-devel@pixar.com:

Subject: Bug#958: pgp PubRing SecRing and RandSeed don't work
Reply-To: andrew@kryten.it.com.au (Andrew Howell), debian-bugs@pixar.com
Resent-To: debian-devel@pixar.com
Resent-From: andrew@kryten.it.com.au (Andrew Howell)
Resent-Sender: iwj10@cus.cam.ac.uk
Resent-Date: Sat, 10 Jun 1995 19:33:02 GMT
Resent-Message-ID: <debian-bugs-handler.958.061019210528675@pixar.com>
X-Debian-PR-Package: pgp-i
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Sat, 10 Jun 1995 19:33:02 GMT
Received: with rfc822 via encapsulated-mail id 061019210528675;
          Sat, 10 Jun 1995 19:21:06 GMT
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sKW4e-0006H0C; Sat, 10 Jun 95 12:20 PDT
Received: from kryten.it.com.au by pixar.com with SMTP id AA27628
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 10 Jun 1995 12:18:26 -0700
Received: by kryten.it.com.au
	id m0sKW49-000AdAC
	(Debian /\oo/\ Smail3.1.29.1 #29.31); Sun, 11 Jun 95 03:19 WST
Message-Id: <m0sKW49-000AdAC@kryten.it.com.au>
From: andrew@kryten.it.com.au (Andrew Howell)
To: iwj10@cus.cam.ac.uk, debian-bugs@pixar.com
Date: Sun, 11 Jun 1995 03:19:28 +0800 (WST)
In-Reply-To: <m0sKPq3-0000XfZ@chiark.al.cl.cam.ac.uk> from "Ian Jackson" at Jun 10, 95 01:40:00 pm
X-Mailer: ELM [version 2.4 PL24 PGP2]
Content-Type: text
Content-Length: 2889

> Andrew Howell writes ("Bug#958: pgp PubRing SecRing and RandSeed don't work"):
> > [kryten:/home/andrew] pgp -kv
> > config.txt: unknown keyword: "PubRing"
> > config.txt: unknown keyword: "SecRing"
> > config.txt: unknown keyword: "RandSeed"
> > /usr/lib/pgp-i/config.txt: Maximum level of 3 error(s) detected
> >
> > When I uncommented these settings in /etc/pgp-i.conf so I could have
> > my public and secret rings in ~/.pgp but not have to put a copy of
> > all the other pgp files there as welli, it didn't like it.
>
> It works for me.  You haven't actually sent me a copy of your
> /etc/pgp-i.conf, but I suspect you've made a syntax error - for
> example, missing out the double quotes that should surround the value.

PubRing = "$HOME/.pgp/pubring.pgp"
SecRing = "$HOME/.pgp/secring.pgp"
RandSeed = "$HOME/.pgp/randseed.bin"

There are the lines from my /etc/pgp-i.conf file. Do you actually use
them. I was a littled confused with the package as you didn't leave
any ideas on how you would expect it to be setup. Or at least I couldn't
find any. How do you set yours up.

> > I had PGPPATH set to /usr/lib/pgp-i/
>
> That seems to me to be an unwise thing to do, at the very least.
>
> PGPPATH is supposed to be the directory containing your *private* PGP
> files, which are not system-wide.  I'd be inclined to say that the
> fact that PGP is willing to accept pubring, secring and randseed
> keywords in the system-wide configuration file is something of a
> misfeature - people shouldn't do that.

The whole point of me setting PubRing SecRing and RandSeed to another place
was to have them in a non public place as you can see above.
Though PGP doesn't seem to be very willing at all ;) It doesn't seem to know
the existance of the keywords....
Unwise, I don't think so, makes good sense to me.

> > For now I guess I'll set PGPPATH to ~/.pgp and makes links in that
> > directory back to the files in /usr/lib/pgp-i/ so I don't need
> > unneccesary copies of the files.
>
> Unnecessary copies of which files ?  config.txt ?  It's only 4.3Kb !
> The other stuff (keyrings and so forth) should be in your home
> directory.

*shrug* It all adds up. I was looking for a way for every user to not
need a config.txt file unless they actually wanted to change something.
My previous non-debian pgp setup was just a .pgp directory in $HOME
with all the files in it, this seemed wasteful. If that's the way it's
meant to be, so be it.

Andrew

-----------------------------------------------------------------------
Dehydration - 34%, Recollection of previous evening - 2%, embarrassment
factor - 91%.  Advise repair schedule:- off line for 36 hours, re-boot
startup disk, and replace head - wow, what a night!
                -- Kryten in Red Dwarf `The Last Day'

Andrew Howell				               andrew@it.com.au
Perth, Western Australia		      howellaa@cs.curtin.edu.au

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: andrew@kryten.it.com.au (Andrew Howell)
Subject: Bug#958: Info received (was Bug#958: pgp PubRing SecRing and RandSeed don't work)
In-Reply-To: <m0sKW49-000AdAC@kryten.it.com.au>
References: <m0sKW49-000AdAC@kryten.it.com.au>

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developers to
accompany the original report.

If you wish to continue to submit further information on your problem,
please do the same thing again: send it to debian-bugs@pixar.com, ensuring
that the Subject line starts with "Bug#958" or "Re: Bug#958" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: iwj10@cus.cam.ac.uk (Ian Jackson)
In-Reply-To: <m0sKycX-0000YJZ@chiark.al.cl.cam.ac.uk>
References: <m0sKycX-0000YJZ@chiark.al.cl.cam.ac.uk> <m0sJPr2-000AdQC@kryten.it.com.au>
Subject: Bug#958: marked as done (was: pgp PubRing SecRing and RandSeed don't work)

Your message dated Mon, 12 Jun 95 02:48 BST
with message-id <m0sKycX-0000YJZ@chiark.al.cl.cam.ac.uk>
and subject line Bug#958: pgp PubRing SecRing and RandSeed don't work
has caused the attached bug report to be marked as done.

It is your now responsibility to ensure that the bug report is dealt
with.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Ian Jackson
(maintainer, debian-bugs)

Received: with rfc822 via encapsulated-mail id 060718305323106;
          Wed, 07 Jun 1995 18:30:53 GMT
From kryten.it.com.au!andrew Wed Jun  7 11:29:37 1995
Return-Path: <andrew@kryten.it.com.au>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sJPrF-0005NiC; Wed, 7 Jun 95 11:29 PDT
Received: from kryten.it.com.au by pixar.com with SMTP id AA26648
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Wed, 7 Jun 1995 11:28:03 -0700
Received: by kryten.it.com.au
	id m0sJPr2-000AdQC
	(Debian /\oo/\ Smail3.1.29.1 #29.31); Thu, 8 Jun 95 02:29 WST
Message-Id: <m0sJPr2-000AdQC@kryten.it.com.au>
From: andrew@kryten.it.com.au (Andrew Howell)
Subject: pgp PubRing SecRing and RandSeed don't work
To: debian-bugs@pixar.com
Date: Thu, 8 Jun 1995 02:29:24 +0800 (WST)
X-Mailer: ELM [version 2.4 PL24 PGP2]
Content-Type: text
Content-Length: 1084

Package: pgp-i
Version: 2.6.2i-1

[kryten:/home/andrew] pgp -kv
config.txt: unknown keyword: "PubRing"
config.txt: unknown keyword: "SecRing"
config.txt: unknown keyword: "RandSeed"
/usr/lib/pgp-i/config.txt: Maximum level of 3 error(s) detected

When I uncommented these settings in /etc/pgp-i.conf so I could have
my public and secret rings in ~/.pgp but not have to put a copy of
all the other pgp files there as welli, it didn't like it.

I had PGPPATH set to /usr/lib/pgp-i/

For now I guess I'll set PGPPATH to ~/.pgp and makes links in that
directory back to the files in /usr/lib/pgp-i/ so I don't need
unneccesary copies of the files.

Andrew

-----------------------------------------------------------------------
Dehydration - 34%, Recollection of previous evening - 2%, embarrassment
factor - 91%.  Advise repair schedule:- off line for 36 hours, re-boot
startup disk, and replace head - wow, what a night!
                -- Kryten in Red Dwarf `The Last Day'

Andrew Howell				               andrew@it.com.au
Perth, Western Australia		      howellaa@cs.curtin.edu.au

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: andrew@kryten.it.com.au (Andrew Howell)
Subject: Bug#958 acknowledged by developer (was: pgp PubRing SecRing and RandSeed don't work)
References: <m0sKycX-0000YJZ@chiark.al.cl.cam.ac.uk> <m0sJPr2-000AdQC@kryten.it.com.au>
In-Reply-To: <m0sJPr2-000AdQC@kryten.it.com.au>

This is an automatic notification regarding your bug report.

Responsibility for it has been taken by one of the developers, namely
iwj10@cus.cam.ac.uk (Ian Jackson).

You should be hearing from them with a substantive response shortly, if
you have not already done so.  If not, please contact them directly,
or email debian-bugs@pixar.com or myself.

Ian Jackson
(maintainer, debian-bugs)

Ian Jackson / iwj10@thor.cam.ac.uk, with the debian-bugs tracking mechanism

This page last modified 06:43:02 GMT Wed 21 Jun