Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 327
    • Issues 327
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #6849
Closed
Open
Issue created Sep 15, 2012 by grarpamp@grarpamp

refdox: Base16, Base32, and Base64 Data Encodings

A number of places in https://git.torproject.org/tor.git https://git.torproject.org/torspec.git refer to an obsoleted info rfc https://tools.ietf.org/html/rfc3548.html which should probably be repointed to the track rfc https://tools.ietf.org/html/rfc4648.html which has handy test vectors, etc.

find | xargs grep 3548

Also, there doesn't seem to be a torspec/docs "component" in trac to pick, so I picked the client.

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