Bug 847834 - Port 43 is closed (when trying to use a TCPSocket client to an outbound server - whois server)
Summary: Port 43 is closed (when trying to use a TCPSocket client to an outbound serve...
Keywords:
Status: CLOSED DUPLICATE of bug 843315
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Rob Millner
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-13 17:26 UTC by Paola Cerioli
Modified: 2015-05-14 22:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-14 17:09:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Paola Cerioli 2012-08-13 17:26:43 UTC
Description of problem:

From my Openshift app, I am trying to connect to whois servers via client sockets on port 43 (default port for whois requests). The port 43 seems closed.
I describe the problem and how to reproduce it in here:
https://openshift.redhat.com/community/forums/openshift/problems-installing-the-ruby-gem-whois

Version-Release number of selected component (if applicable):


How reproducible:

You can run this short Ruby scripts (even with irb):

require "socket"
socket = TCPSocket.new("whois.nic.it", 43)
socket.write ("example.it\r\n") 
response = socket.read
puts response
socket.close  # close socket when done

On my laptop works and I get the whois info for the specified domain name.
But on the Openshift server, I get this error:

irb(main):002:0> socket = TCPSocket.new("whois.nic.it", 43)
Errno::EACCES: Permission denied - connect(2)
 from (irb):2:in <code>initialize&#039;&#10;  from (irb):2:in</code>new'
 from (irb):2
   from /opt/rh/ruby193/root/usr/bin/irb:12:in `<main>'

Comment 1 Miciah Dashiel Butler Masters 2012-08-14 13:49:36 UTC
Isn't this the same as bug 843315? The SELinux policy blocks port 43.

Comment 2 Rob Millner 2012-08-14 17:09:25 UTC
It is a duplicate of 843315 - thanks!

*** This bug has been marked as a duplicate of bug 843315 ***


Note You need to log in before you can comment on or make changes to this bug.