Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Arti Arti
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 142
    • Issues 142
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • ArtiArti
  • Issues
  • #331
Closed
Open
Created Feb 10, 2022 by Nick Mathewson@nickm🐻Owner

Be "at least as secure" as Tor (as a client)

This is a fairly open-ended ticket; it is a requirement for %Arti 1.0.0: Ready for production use, but we need to decide what exactly it comprises.

Some likely candidates to include are:

  • SafeLogging (#189 (closed))
  • Zeroizing keys (#254)
  • Circuit isolation code (#150 (closed))
  • File permission checking (#315 (closed))
  • Setting per-process flags and dropping permissions as in C tor's winprocess_sys.c, restrict.c, setuid.h (#364)
  • Netflow padding (#62)

Some things not necessarily to include (now) are:

  • seccomp2 sandboxing (huge kludge, less necessary in Rust)
  • memory-DoS resistance (waits for %Arti 1.2.0: Onion service support )
  • hardened PRNG (current prng is "good enough")
Edited Feb 24, 2022 by Nick Mathewson
Assignee
Assign to
Time tracking