-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Till Kamppeter wrote: > In my opinion this is a show-stopper, report a "blocker" bug and inform > Warly. >
I tried posting this one, but my proxy server complained a malformed url during posting. I will try and post it later without a proxy (from home): Version: 9.2-11mdk Component: DrakConnect: Mandrake Network configuration tool Summary: Drakconnect hostname configuration is non-intuitive, leading to bad configurations Severity: blocker "The biggest problem with drakconnect, is that by default (if the user does not use any advanced or expert buttons) the machine will end up with a hostname of localhost. The problem is that any service which advertises the servers name to other machines, they will see the localhost, and connect to themselves. Common failures include: - -Windows machines being unable to connect to a samba server running on such a machine - -CUPS machines unable to print to a server on such a machine (except that Till patched CUPS to prevent this now - which should not be necessary) - -Redirects by a web server will redirect to 'localhost' in some cases (IIRC with Location's accessed without a trailing slash) - -Postfix will complain at startup - -Any SSL certificates generated automatically will have the name 'localhost' on the cert, instead of the real hostname. Specifically, note that no two Mandrake machines would be able to join a Windows domain unless the installer would know to change the hostname entry in expert mode in drakconnect. Also, if the user only sets the zeroconf name, they will also be registering a zeroconf name that does not match their hostname. The 2nd problem is that by default, the configured hostname is not supplied with the DHCP query. This means that on networks that use DDNS, the DNS entries will not be made by the DHCP server, and the machine will not get an FQDN as hostname. Note, that Windows by default does both of these, so this is the expected behaviour. My proposal is that Drakconnect should: - -By default propmt the user for one hostname, which shall be supplied as HOSTNAME in /etc/sysconfig/network and as DHCP_HOSTNAME in /etc/sysconfig/network-scripts/ifcfg-eth* - -By default not touch /etc/tmdns.conf. tmdns will by default register `hostname` as the zeroconf name. I haven't found a scenario where the user would want zeroconf to claim a different name than the hostname. If it is necessary, the expert modes should allow the following: - -Edit the DHCP_HOSTNAME value (but it should still default to the hostname entered), per interface - -Allow the user to use a different zeroconf name (though, why this would be useful is beyond me). I am sorry this bug was filed so late, but there have been many discussions on cooker on this. The drakconnect maintainer has participated in some of them, but has not replied to any of the suggestions or proposals. And still, we have a distribution where if the user sets the most visible hostname, when they log in, they find their hostname is localhost, and where software's default configuration is broken, and certain features (such as Windows Domain authentication) are virtually impossible to use." Regards, Buchan - -- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/a1/7rJK6UGDSBKcRAq1oAJ4yF8k58ht5AEj9detP8CCrt2OPZACdHAcD zi9ZJan7oaEqtpGBzCiP/Bw= =P2Ez -----END PGP SIGNATURE----- ***************************************************************** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. *****************************************************************
