Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #22447

Closed (moved)
(moved)
Open
Created May 30, 2017 by David Goulet@dgoulet🆘

hs: HSDir do not accept v3 descriptors properly

When a v3 descriptor is uploaded, it goes through a series of validation including encrypted_data_length_is_valid() which checks for the encrypted data size to be a multiple of #define HS_DESC_PLAINTEXT_PADDING_MULTIPLE 128 but it's not true anymore becase we pad up to a minimum of 10000 bytes.

This is currently fixed upstream but wasn't backported to 030. It has been introduced in tor-0.3.0.1-alpha with commit cff1fd63f16.

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