socket.getfqdn() doesn't cope properly with purely DNS-based setups

Open
#49,254 24 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

Start at the socket.getfqdn() entry point and compare its behavior in purely DNS-based setups with the outputs documented by python5004-test.c. Review python2.7-socket-getfqdn.patch, including the updated python2.7-socket-getfqdn.patch, and use the observed discrepancy to define the expected behavior and tests for the Library (Lib) component.

Written by the indexing model from the issue text.

Description

3.10 3.11 3.9 (EOL) stdlib topic-socket type-bug
BPO 5004
Nosy @loewis, @tiran, @mcepl, @bitdancer, @thomaswaldmann, @jan-hudec, @shoop
Files
  • python2.7-socket-getfqdn.patch
  • python5004-test.c: test C program showing various gethost function output on my system
  • python2.7-socket-getfqdn.patch: Updated patch, originally by Stijn.Hoop
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = None
    created_at = <Date 2009-01-19.22:29:02.219>
    labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
    title = "socket.getfqdn() doesn't cope properly with purely DNS-based setups"
    updated_at = <Date 2021-12-16.17:35:04.319>
    user = 'https://bugs.python.org/dfranke'
    

    bugs.python.org fields:

    activity = <Date 2021-12-16.17:35:04.319>
    actor = 'mcepl'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2009-01-19.22:29:02.219>
    creator = 'dfranke'
    dependencies = []
    files = ['29919', '29921', '50390']
    hgrepos = []
    issue_num = 5004
    keywords = ['patch']
    message_count = 24.0
    messages = ['80216', '109635', '109647', '162508', '173987', '187065', '187098', '187234', '187237', '187238', '187253', '187256', '187350', '187355', '297435', '300593', '308979', '372583', '404775', '404780', '404796', '404806', '404826', '405364']
    nosy_count = 14.0
    nosy_names = ['loewis', 'christian.heimes', 'mcepl', 'r.david.murray', 'dfranke', 'devurandom', 'mcjeff', 'ankitoshniwal', 'Thomas.Waldmann', 'Stijn.Hoop', 'bulb', 'James Shewey', 'richard.security.consultant', 'shoop']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue5004'
    versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
    

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.