Skip to content
GitLab
  • Menu
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 318
    • Issues 318
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • 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
  • #880
Closed
Open
Created Dec 02, 2008 by Nick Mathewson@nickm🐻Owner

Parsing misuses -----END SIGNATURE----- tags

Sometimes[*] in parsing dir-spec documents, we look for the tag -----BEGIN SIGNATURE----- or -----END SIGNATURE----- to find the end of the document or the boundary between two documents. This is wrong. There is nothing stopping a perfectly valid document from containing an internal entity with an attached tag of type SIGNATURE.

We have two options:

  • Change the spec so that signature objects are forbidden where not mandatory.
  • Change the implementation so entries with signature objects are tolerated.

[*] We definitely do this for certificates and may do it for other things too.

[Automatically added by flyspray2trac: Operating System: All]

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