Bug 198460 - Package scim lacks IPv6 support
Package scim lacks IPv6 support
Product: Fedora
Classification: Fedora
Component: scim (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Peng Huang
Fedora Extras Quality Assurance
: FutureFeature
Depends On:
Blocks: FC6Target
  Show dependency treegraph
Reported: 2006-07-11 08:39 EDT by Peter Vrabec
Modified: 2007-11-30 17:11 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 23:48:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Vrabec 2006-07-11 08:39:27 EDT
This bug was reported automaticaly in connection with IPv6 project.
Our aim is to support IPv6 in all Fedora Core packages so FC6 and RHEL5 will be ready for IPv6.
This package seems to lack IPv6 support.
Comment 1 Jens Petersen 2006-07-11 22:07:19 EDT
SCIM uses unix domain sockets by default and we have never tested it
over tcp sockets.  So does this still need to be done for FC6?
Comment 2 Jan Pazdziora 2006-07-12 01:43:58 EDT
There seems to be a code in scim-1.4.4-20060704/src/scim_socket.cpp file in
SocketAddress::SocketAddressImpl::set_address method that checks

else  if ((varlist [0] == "tcp" || varlist [0] == "inet") 

and based on that creates an AF_INET socket. Also, the __gethostname uses
gethostbyname_r, a IPv4-only function. Using getaddrinfo might be needed.

Could you check if the TCP code is ever used by other parts of scim?
Comment 3 Jens Petersen 2006-07-24 21:12:39 EDT
It is only used if one explicitly configures scim to use a tcp socket
instead of a unix one, but we've never actually tested that codepath...
Comment 6 Jens Petersen 2006-09-26 01:09:07 EDT
Lower to FC6 Target since net code is not used by default configuration
and indeed we have never even tested it.
Comment 7 Jens Petersen 2007-11-07 23:48:30 EST
I am going to defer this for now, since network socket support
is a low priority anyway.

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