Your message dated Fri, 28 Oct 2005 20:54:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#333585: postgresql-8.0: --auth=?? not documented
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 12 Oct 2005 19:56:46 +0000
>From [EMAIL PROTECTED] Wed Oct 12 12:56:46 2005
Return-path: <[EMAIL PROTECTED]>
Received: from roller.integritxx.hu (roller.integritxx.local) [212.108.199.204]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EPmiU-0005Ru-00; Wed, 12 Oct 2005 12:56:46 -0700
Received: from akac.integritxx.local ([192.168.4.1]
helo=szikla.integritxx.local)
by roller.integritxx.local with esmtp (Exim 4.32)
id 1EPmiR-0001KQ-Co; Wed, 12 Oct 2005 21:56:43 +0200
Received: from baldvin by szikla.integritxx.local with local (Exim 4.44)
id 1EPmiR-0002I5-6J; Wed, 12 Oct 2005 21:56:43 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Kovacs Baldvin <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: postgresql-8.0: --auth=?? not documented
X-Mailer: reportbug 3.7.1
Date: Wed, 12 Oct 2005 21:56:43 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: postgresql-8.0
Version: 8.0.4-1
Severity: normal
initdb warns that you should use -A next time. Fine. Then you do
man initdb: it says for -A: trust is the default, but you should use
some other mechanism.
However, it is nowhere documented which other mechanisms can you
choose, especially what on the earth should you write for using pg_hba.conf??
I'v tried hba, pg_hba, hostbased, host with no success.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11.11-szikla
Locale: LANG=C, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8)
Versions of packages postgresql-8.0 depends on:
ii libc6 2.3.5-5 GNU C Library: Shared libraries an
ii libcomerr2 1.36release-1 common error description library
ii libkrb53 1.3.6-1 MIT Kerberos runtime libraries
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libpq4 8.0.3-15 PostgreSQL C client library
ii libreadline5 5.0-10 GNU readline and history libraries
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii postgresql-client-8.0 8.0.4-1 front-end programs for PostgreSQL
ii postgresql-common 27 manager for PostgreSQL database cl
ii zlib1g 1:1.2.2-4 compression library - runtime
-- no debconf information
---------------------------------------
Received: (at 333585-done) by bugs.debian.org; 29 Oct 2005 00:57:12 +0000
>From [EMAIL PROTECTED] Fri Oct 28 17:57:12 2005
Return-path: <[EMAIL PROTECTED]>
Received: from box79162.elkhouse.de [213.9.79.162]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EVf20-0006mC-00; Fri, 28 Oct 2005 17:57:12 -0700
Received: from localhost.localdomain (unknown [66.103.220.201])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "Martin Pitt (iBook)", Issuer "piware CA" (verified OK))
by box79162.elkhouse.de (Postfix) with ESMTP id 02CC1260E41
for <[EMAIL PROTECTED]>; Sat, 29 Oct 2005 02:56:40 +0200 (CEST)
Received: by localhost.localdomain (Postfix, from userid 1000)
id 65408138EB; Fri, 28 Oct 2005 20:54:22 -0400 (EDT)
Date: Fri, 28 Oct 2005 20:54:22 -0400
From: Martin Pitt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#333585: postgresql-8.0: --auth=?? not documented
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="ffoCPvUAPMgSXi6H"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
--ffoCPvUAPMgSXi6H
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi Kovacs!
Kovacs Baldvin [2005-10-12 21:56 +0200]:
> initdb warns that you should use -A next time. Fine. Then you do
> man initdb: it says for -A: trust is the default, but you should use
> some other mechanism.
Please do not use initdb directly unless you have a special reason to
do so; there is a reason why it is not in the $PATH. Please use
pg_createcluster, which picks sensible defaults.
> However, it is nowhere documented which other mechanisms can you
> choose, especially what on the earth should you write for using pg_hba.co=
nf??
It's summarized in the pg_hba.conf help [1] and covered in great
detail in the section "authentication methods" [2] in the docs.
Have a nice day,
Martin
[1] http://www.postgresql.org/docs/8.0/interactive/client-authentication.ht=
ml
[2] http://www.postgresql.org/docs/8.0/interactive/auth-methods.html
--=20
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
--ffoCPvUAPMgSXi6H
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDYsg+DecnbV4Fd/IRAvb0AJ4kmXZMB4GUtAQoFerUH1bMprYUhACg+5Ns
u8EeIld+ZPg5FQuA9LaI/oM=
=DSOY
-----END PGP SIGNATURE-----
--ffoCPvUAPMgSXi6H--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
