Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Torsocks
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • Torsocks
  • Issues
  • #17618
Closed
Open
Issue created Nov 16, 2015 by Trac@tracbot

Segfault in tsocks_accept4() if called through syscall()

Hello,

There is a segfault in tsocks_accept4() when it is called through syscall() and accept4() isn't called first.

It's because tsocks_libc_accept4 is only initialized through accept4() and not syscall().

From what I can tell this is not only a problem with tsocks_accept4() but many other calls made through syscall().

My suggested fix is to replace the native tsocks calls in syscall.c with their libc equivalents. E.g. instead of calling tsocks_accept4(), calling accept4().

Whatever the best fix, I can provide a patch for it given the right direction.

Trac:
Username: crystalmaker

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