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

Offen
#49,254 24 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
networking

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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']

    Vorherrschende Sprache
    Python
    Sterne
    77.2k
    Forks
    36k
    Ø Merge
    1 T. 9 Std.
    Gemergte PRs (30 T.)
    558

    Beitragsleitfaden

    Beitragsleitfaden öffnen

    Erste Schritte

    1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
    2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
    3. Forken Sie das Repository und arbeiten Sie in einem Branch.
    4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

    Mehr aus python/cpython

    Alle Issues in python/cpython

    Ähnliche Issues

    Weitere Issues zu Python

    Neue Issues direkt in Ihr Postfach

    Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.