Your message dated Sun, 23 Apr 2006 16:47:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362571: fixed in dbconfig-common 1.8.12
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)

--- Begin Message ---
Package: dbconfig-common
Version: 1.8.11
Severity: important

I was trying to debug a problem i had with simba and ended up looking at
this code:

----
                ###
                ### perform a few sanity checks on the data
                ###

                # if dbserver is unset, that means localhost.
                if [ -z "$dbc_dbserver" ]; then
                        # if the server is local, only allow connections from 
localhost
                        dbc_dballow="localhost"
                else
                        # otherwise, only tell the remote database to allow 
from us
                        dbc_dballow=`hostname`
                fi
----

I see two bugs here. 

The first one, and the one i am getting: if i tell dbserver to use "localhost"
dbc_dballow gets set to my hostname ("stark"). "Stark" hostname resolves to my 
real ip address, 
on which, by default, mysql does not listen to.

The second bug: if i would actually write the data to a remote server, that 
machine may or may not
be in the same domain name as me (search field in /etc/resolv.conf), so it 
should be "hostname -f", or even 
better an ip address.

This is how i think the code should look like:

----
                ###
                ### perform a few sanity checks on the data
                ###

                # if dbserver is unset, that means localhost.
                if [ -z "$dbc_dbserver" ] || [ "$dbc_dbserver" = "localhost" ]; 
then
                        # if the server is local, only allow connections from 
localhost
                        dbc_dballow="localhost"
                else
                        # otherwise, only tell the remote database to allow 
from us
                        dbc_dballow=`hostname -f`
                fi
----


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages dbconfig-common depends on:
ii  debconf [debconf-2.0]         1.4.72     Debian configuration management sy
ii  pwgen                         2.05-1     Automatic Password generation
ii  ucf                           2.007      Update Configuration File: preserv

dbconfig-common recommends no packages.

-- debconf information excluded


--- End Message ---
--- Begin Message ---
Source: dbconfig-common
Source-Version: 1.8.12

We believe that the bug you reported is fixed in the latest version of
dbconfig-common, which is due to be installed in the Debian FTP archive:

dbconfig-common_1.8.12.dsc
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.12.dsc
dbconfig-common_1.8.12.tar.gz
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.12.tar.gz
dbconfig-common_1.8.12_all.deb
  to pool/main/d/dbconfig-common/dbconfig-common_1.8.12_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
sean finney <[EMAIL PROTECTED]> (supplier of updated dbconfig-common package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


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

Format: 1.7
Date: Mon, 24 Apr 2006 01:26:02 +0200
Source: dbconfig-common
Binary: dbconfig-common
Architecture: source all
Version: 1.8.12
Distribution: unstable
Urgency: low
Maintainer: sean finney <[EMAIL PROTECTED]>
Changed-By: sean finney <[EMAIL PROTECTED]>
Description: 
 dbconfig-common - common framework for packaging database applications
Closes: 348720 350588 362571
Changes: 
 dbconfig-common (1.8.12) unstable; urgency=low
 .
   [sean finney]
   * dbconfig-common is now migrated to svn.debian.org.
   * two fixes for GRANT command construction from Radu Spineanu:
     - if dbc_dbserver is localhost, then dbc_dballow should
       also be set to localhost (currently it's set to the output of
       `hostname`, just like with remote connections)
     - if connecting to a remote host, use the fqdn (`hostname -f`)
       instead of the node name.
     (closes: #362571).
   * the source package in ./examples is now split into several
     smaller source packages, one per binary.  this should hopefully
     make things much easier to understand for developers interested
     in using dbconfig-common.  thanks to Jelle Boomstra for the
     suggestion (closes: #350588).
   * fix a documentation bug on where installation files should
     be placed.  thanks to Uwe Steinmann for pointing this out
     (closes: #348720).
   * Cameron Dale noticed that a mix of script/sql/admin sql upgrades
     would not necessarily be applied in sorted order with respect
     to each other.  this *should* be fixed now, but i'm sure i'll
     hear if it isn't.
   * added missing build-depend on gs.
   * added a debugging and logging function, and started using it
     in various places as i add more code.  to get a little more
     info on what goes on, export dbc_debug=1 before installing
     a dbc-using package.
   * logic fix for install/upgrades in postinst that would otherwise
     result in installation code being run when it shouldn't, which
     can be really annoying.  now everything *should* work the way
     it ought to...
Files: 
 a8948852a096823c5ad5331fce7d49a9 549 admin optional dbconfig-common_1.8.12.dsc
 30694cd47256c71177035d82b27a57b4 198241 admin optional 
dbconfig-common_1.8.12.tar.gz
 65a40054c69747eecf1ed6aedbaafb9f 383242 admin optional 
dbconfig-common_1.8.12_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFETA44ynjLPm522B0RAnJDAJ45+r765ArYIiFeXLbS/1uN2ANj5QCfSlrF
X++X2pWc/1uUnWkoffIR5G0=
=UZ8L
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to