Bug 990560 - libdnet needs to use getaddrinfo instead of gethostbyname
Summary: libdnet needs to use getaddrinfo instead of gethostbyname
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libdnet
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 983265
TreeView+ depends on / blocked
 
Reported: 2013-07-31 12:58 UTC by Richard W.M. Jones
Modified: 2016-12-20 12:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-20 12:40:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2013-07-31 12:58:54 UTC
Description of problem:

See src/addr.c.

Use of gethostbyname may prevent the program from working
properly on IPv6 systems.  getaddrinfo should be used in preference.

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

libdnet-1.12-11.fc20

Comment 1 Fedora Admin XMLRPC Client 2013-08-16 04:32:59 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora End Of Life 2013-09-16 14:56:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 3 Fedora End Of Life 2015-05-29 09:13:59 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Richard W.M. Jones 2015-05-29 09:19:45 UTC
Still using gethostbyname in Rawhide version.

Comment 5 Fedora Admin XMLRPC Client 2015-06-28 07:10:49 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Robert Scheck 2015-06-28 16:34:42 UTC
Richard, are you aware of any patch which resolves this issue?

Comment 7 Richard W.M. Jones 2015-06-29 11:06:09 UTC
No.  Realistically I should have filed this bug upstream.
http://libdnet.sourceforge.net/

Comment 8 Fedora Admin XMLRPC Client 2015-06-29 18:08:58 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 9 Robert Scheck 2015-06-29 18:25:25 UTC
I filed https://sourceforge.net/p/libdnet/bugs/26/ for this at upstream.

Do you think it makes sense to keep this RHBZ still open? The real work
should happen at upstream from my point of view.

Comment 10 Richard W.M. Jones 2015-06-29 18:34:07 UTC
As the assignee it's ultimately up to you, but maybe we should leave
it open just to ensure the fix gets added back to Fedora.

Comment 11 Robert Scheck 2015-06-29 19:19:10 UTC
Given that the spec file mentions https://code.google.com/p/libdnet as the
homepage, I also filed https://github.com/dugsong/libdnet/issues/36 to be on
the safe side.

Comment 12 Jan Kurik 2015-07-15 14:46:35 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 13 Fedora End Of Life 2016-11-24 11:00:40 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2016-12-20 12:40:16 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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