Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-daemon
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 111
    • Issues 111
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-daemon
  • Issues
  • #548
Closed (promoted) (promoted)
Open
Created May 17, 2021 by Sébastien Blin@sblinOwner

Add Fuzzy tests

A lot of places in Jami are receiving data from another point. This can cause crashes, potential attacks, etc. The goal is to improve quality and avoid crashes in the daemon whenever random payloads can be received.

Some place I can list:

  • Sockets in connecting Manager:
    • SIP calls
    • File transfer
    • SIP Messages
    • ICE sockets
  • OpenDHT (DHT protocol & Jami messages)
  • Media calls
  • UPnP
  • SIP account
  • Account imports (via archive)

So, as a first step, we can:

  • Experiment various tools to perform fuzz testing
  • Generate random payloads for the places listed before.

Note that for some places this will need some investigation to send payloads to the component. However, for SIP/ConnectionManager/ICE it should not be difficult as sockets are exposed.

Edited May 17, 2021 by Sébastien Blin
Assignee
Assign to
Time tracking