Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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
  • #8217
Closed
Open
Created Feb 12, 2013 by George Kadianakis@asn

obfsproxy: obfs2: When deriving padding keys we truncate the shared-secret hash

In derive_padding_key() we do:

  if (shared_seed_nonzero(state->secret_seed))
    digest_update(c, state->secret_seed, OBFUSCATE_SEED_LENGTH);

OBFUSCATE_SEED_LENGTH should read SHARED_SECRET_LENGTH, similarly to how it is in derive_key().

This is a bug in obfsproxy master, and it will break compatibility with any correct obfs2 implementations.

Good thing is that obfsproxy is going obsolete these days, so most (all?) obfs2 shared-secret users will probably be using pyobfsproxy.

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