[mico-devel] Re: installation of mico failed

Chris Yate chrisyate at gmail.com
Wed Oct 11 00:13:33 PDT 2006


Hi,

We've had exactly the same issue with hosts files, both on the server
(Redhat) and the client (Windows) although the client is using TAO.
Now that we know the solution it's not a big problem!

But why does MICO have to know the hostname? It seems quite
unnecessary. What is wrong with just having the IP address(es)? I
consider this to be a bug!!
Having the correct IP Addresses in the hosts file on both the client
and server is just a fairly easy workaround.

Your thoughts? Is there a good reason for this, something which could
be fixed in a future release?

Chris

On 10/10/06, Andrew Zinn <andrewzinn at hotmail.com> wrote:
> This is something that would be useful in the INSTALL.txt documentation.  I
> just helped a friend install MICO on a Fedora Core 5 machine.  I knew he had
> to edit his hosts file, but it wasn't obvious to him.
>
> Thanks for all the work put into MICO.  Since I haven't seen it listed, I'll
> let you know I have MICO working with Linux 2.6 on x86_64 machines.
>
> Andrew Zinn
>
> >From: Karel Gardas <kgardas at objectsecurity.com>
> >
<SNIP>....
> >
> >don't focus your attention solely on DNS configuration. In fact I would
> >rather recommend you to inspect your /etc/hosts file which Rudolf already
> >suggested. The whole issue is that your machine of some name needs to be
> >able to also get it's own IP address and to the machine IP you need to be
> >able to get the machine name. For both these tasks /etc/hosts is perfectly
> >enough, you just need to setup or even install your machine correctly.


More information about the Mico-devel mailing list