>>>> I seemed to have stumbled across a problem, and have had NO
>>>> response whatsoever in the Cooker mailing list.  This is extremely
>>>> frustrating, as up until this point, everything I've ever posted has
>>>> been fixed within a number of hours.  This bug was first reported over
>>>> a week ago, and has been reposted once and mentioned twice.  I don't
>>>> have all the details here with me, but I'm going to spill out as much
>>>> as possible and hope that I get a response this time.
>>> 
>>> what give you  :
>>> 
>>> telnet localhost auth 
>>> 
>>> here(7.1) it's run just fine
>> Are you using the secure kernel?
> 
> no

Probably why you aren't seeing the problem.

>> Running from inetd:
>> 
>> [root@big /etc]# telnet localhost auth 
>> Trying 127.0.0.1...
>> Connected to localhost.localdomain.
>> Escape character is '^]'.
>> Connection closed by foreign host.
>> 
>> [root@big /etc]# tail -2 /var/log/messages
>> Jun  4 14:56:41 big in.identd[30631]: started
>> Jun  4 14:56:41 big in.identd[30631]: fopen("/proc/net/tcp", "r"):
>> Permission denied
> 
> here is the point, secure kernel dont' allow you to use this procfile,
> you have to switch to the normal kernel

I will accept that as a temporary workaround.  IMHO, this should not be
considered a permanent fix.  I personally don't know that much about the
"secure" kernel.  I've read the rpm -qi, and it talks about securing pieces
of /proc, "so that users may not see who else is logged on or what they are
doing".  I'm not really too sure what this has to do with the file that
pidentd is trying to read, but it must have something (otherwise, why would
it be having this problem?).  As I run a somewhat public system, the word
"secure" means a lot to me, so I'd prefer to use it.

It may be that Mandrake would want to look into one of the following:

 - Modifying the secure kernel so that it doesn't interfere with pidentd.
 - Finding another identd solution other than pidentd that doesn't require
   access to that file.
 - Something else I haven't thought of.

I guess this can be added to the list of things "I'd like to see changed in
Mandrake", although I think that this is somewhat more on the lines of
"partially broken functionality" rather than a "new feature request", and I
would treat it accordingly.

Thank you for your time in confirming that this was an actual problem
(rather than me or my system smoking crack), providing a temporary
workaround, and being an all-around good Mandrake person.

Don Head
Linux Mentor
Wave Technologies, Inc.
[EMAIL PROTECTED]

>> Running standalone:
>> 
>> [root@big haze]# /etc/rc.d/init.d/identd start
>> Starting identd: [  OK  ]
>> 
>> [root@big haze]# tail -2 /var/log/messages
>> Jun  4 15:05:03 big identd[30809]: fopen("/proc/net/tcp", "r"):
>> Permission denied
>> Jun  4 15:05:03 big identd: identd startup succeeded
>> 
>> [root@big haze]# telnet localhost auth        
>> Trying 127.0.0.1...
>> telnet: Unable to connect to remote host: Connection refused

Reply via email to