Several issues with /etc/hosts.allow at a university setting

dpdoughe_at_allvantage.com
Date: 08/31/05


Date: 30 Aug 2005 18:06:37 -0700

Recently I was required to "register" my laptop (running Fedora 3) with
my university's computer support office in order to use their internet
on campus. Somehow in this self-guided on-line process they
automatically created a new hostname for my computer.

The next time I booted up with the ethernet connected, my computer
booted under this new hostname rather than localhost (as it will do if
I don't have the ethernet plugged in at boot time). Basically I am
very frustrated by this because I consider this having been "hacked".
I never created the hostname on my computer or did anything to tell my
computer that it should boot up under anything but localhost. Is this
some default setting in dhcp perhaps??? How to remove?

Other problems that occur of this new arrangement is that my display
won't work if booted under the new hostname. If I boot under localhost
(ethernet cable not plugged in) then I get display up (as usual). But
as soon as I plug the ethernet cable and do "/sbin/ifup eth0", the
hostname switches to the new host name and I lose the ability to open
any new apps requiring the display. I can do "xhost +" prior to
calling /sbin/ifup and everthing will work fine.

However, I've heard xhost + is an insecure way of doing things though
since it allows all hosts. Trying more restrictive "xhost hostname"
etc did not fix the display problem only "xhost +" seems to work.

Questions:
1) I don't want to be booted into the new host name even if the
ethernet is plugged in and active at boot. How do I turn off this
automatic "get thyself hacked" behavior. Basically when I want to
connect to the internet I'd like to a) switch to the new hostname and
then b) do /sbin/ifup eth0. In otherwords I want to be able to control
the hostname of my own damn computer. Seems reasonable to me...

2) I assume X is not aware of the new host name. I thought adding the
new host to /etc/hosts.allow was the prefered way rather than xhost +.
But this doesn't seem to do anything at all. Is /etc/hosts.allow the
correct file to use for this?

3) Another drag is that if I yank the connection to the internet after
being booted into the new host name, the display is again in a
non-functional state. How do I get back control of the display. In
other words, there should be a way of stating OK now go back to being
localhost and run display from there.



Relevant Pages

  • Re: CDE question
    ... The hostname is also listed in some ... > tx38 was an alias for a remote host, ... > is empty except for the loopback and the server itself, the DISPLAY ... HP Managed Services Germany ...
    (comp.sys.sun.admin)
  • Re: setting display for oracle runinstaller
    ... Hostname is, well, hostname. ... more than one display number. ... the display number, not the screen number; ie, the first zero, not the ... Unless the display is on a different host, ...
    (comp.unix.admin)
  • Re: hostnames and interfaces
    ... Apache documentation on doing virtual hosts and maybe do some ... A fully Qualified Host Name consists of two main parts. ... During installation, when it asks for hostname, it wants a Fully ... service what DNS server will be providing DNS service for that domain. ...
    (freebsd-questions)
  • Re: /bin/hostname
    ... Find a real news server. ... in /etc/hosts that maps the host and the FQDN to the static IP ... Linux distributions are supposed to follow Linux Standard Base standards, ... hostname -- show or set the system's host name ...
    (comp.os.linux.networking)
  • RE: apache not starting: FreeBSd 5.4
    ... Assigning a Host name to your FBSD system. ... statement hostname= to /etc/rc.conf. ... registered domain name on the public Internet (unless of course it's ...
    (freebsd-questions)