Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #13553

Closed (moved)
Open
Opened Oct 23, 2014 by cypherpunks@cypherpunks

CA pinning for the RPM repo

Since #12897 (moved) has been implemented RPM repo data is fetched using HTTPS.

To protect against SSL MITM attacks via compromized/rogue CAs I would suggest to implement CA pinning.

YUM provides an easy way to implement this. Simply add an additional line to your torproject.repo file [1]

sslcacert=/path/to/issuing-ca.pem

That pem file should be rpm-managed so you can easily update it in case you switch CA.

[1] https://www.torproject.org/docs/rpms.html.en

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#13553