Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #5537

Closed (moved)
(moved)
Open
Created Mar 30, 2012 by Nick Mathewson@nickm🍬

client_check_address_changed() looks likely to do badly with ipv6 connections

Clients call client_check_address_changed() on every outgoing connection. This function then does a getsockname() on the socket using a sockaddr_in, and logs a warnings if the getsockname() fails.

Unless I'm missing something fundamental, this will spam users' logs with a bunch of EFAULT errors.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking