Project

General

Profile

Actions

Feature #807

closed

Implement CONNECT support

Added by Eric Leblond about 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Effort:
Difficulty:
Label:

Description

When using a proxy for HTTPS, the CONNECT keyword is used to open the connection to the peer. Suricata is currently not seeing the TLS exchange because it does not switch the flow applayer to TLS after seeing this keyword.

Actions #1

Updated by Victor Julien about 11 years ago

  • Target version set to TBD

Currently in our HTP glue layer we do detect when a CONNECT tunnel is in place, but we silently ignore it in HTTP parsing. So an implementation should probably hook into this.

Actions #2

Updated by Victor Julien over 10 years ago

  • Target version changed from TBD to 3.0RC2
Actions #3

Updated by Victor Julien over 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Eric Leblond
Actions #4

Updated by Victor Julien over 9 years ago

  • Target version changed from 3.0RC2 to 2.1beta2
Actions #5

Updated by Victor Julien over 9 years ago

  • Target version changed from 2.1beta2 to 2.1beta3
Actions #6

Updated by Victor Julien over 9 years ago

  • Target version changed from 2.1beta3 to 2.1beta4
Actions #7

Updated by Victor Julien almost 9 years ago

  • Target version changed from 2.1beta4 to 3.0RC1
Actions #8

Updated by Victor Julien over 8 years ago

  • Target version changed from 3.0RC1 to 70
Actions #9

Updated by Victor Julien over 6 years ago

  • Status changed from Assigned to Closed
  • Assignee deleted (Eric Leblond)
  • Target version deleted (70)

This has been implemented since in 4.0.

Actions

Also available in: Atom PDF