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 328
    • Issues 328
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • 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
  • #17197
Closed (duplicated) (duplicated)
Open
Issue created Oct 01, 2015 by teor@teor

Use CRLF for all text files written on Windows, accept either CRLF or LF on all platforms

In legacy/trac#17501 (moved), stem becomes confused because some text files written on Windows use CRLF, and others use LF.

We could use CRLF for all text files written on Windows, and accept either CRLF or LF on all platforms.

Here is a list of files from DataDirectory with their line endings on Windows:

CRLF cached-certs
CRLF cached-consensus
LF   cached-descriptors
LF   cached-descriptors.new
CRLF cached-microdesc-consensus
LF   cached-microdescs
LF   cached-microdescs.new
CRLF state

We might want to review all files written by tor, including those only written by hidden services and any other components.

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