On 05/26/2011 02:36 AM, Lukasz Lacinski wrote:
myproxy-logon successfully connects to localhost. Kernel accept a connection
request and the connection is established. More important is that what happens
later. Later the library libwrap, myproxy-server is built against, verifies
access control policy defined in /etc/hosts.allow/ etc/hosts.deny. If you
execute myproxy-server again in debug mode you will see that libwrap blocks
the connection.
Lukasz
Hey
I tried running the server and trying to log in from a different console without
the xinet daemon. I don't know why it is saying "Cannot get subject name from
certificate".
[dknight@fool soc]$ myproxy-logon -d -v -s localhost
MyProxy v5.3 17 Jan 2011 PAM OCSP
Attempting to connect to 127.0.0.1:7512
Successfully connected to localhost:7512
using trusted certificates directory /etc/grid-security/certificates
server name:
/O=Grid/OU=GlobusTest/OU=simpleCA-fool.man.machine/CN=host/fool.man.machine
checking that server name is acceptable...
server name matches "[email protected]"
authenticated server name is acceptable
Enter MyProxy pass phrase:
Cannot get subject name from your certificate.
From another console,
[dknight@fool ~]$ myproxy-server -d -v
myproxy-server v5.3 17 Jan 2011 PAM OCSP starting at Fri May 27 01:46:50 2011
reading configuration file /etc/myproxy-server.config
Processing usage_stats_target (usage-stats.cilogon.org:4810)
USAGE-STATS: Initialized (usage-stats.cilogon.org:4810) (VvtrlLB)
using storage directory /home/dknight/soc/gt/var/myproxy
Starting myproxy-server on localhost:7512...
using trusted certificates directory /etc/grid-security/certificates
Authenticated client
/O=Grid/OU=GlobusTest/OU=simpleCA-fool.man.machine/CN=host/fool.man.machine
Error reading: failed to read token Broken pipe
Exiting: Error in myproxy_recv_ex()
Is there any error in creating the certificates?
Regards
Amitav
