[Bro-Dev] [JIRA] (BIT-1178) SSL/TLS analyzer does not abort early enough on non-ssl connections

[Bernhard Amann (JIRA)]

    [ https://bro-tracker.atlassian.net/browse/BIT-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220#comment-16220 ] 

Bernhard Amann commented on BIT-1178:
-------------------------------------

topic/bernhard/ssl-analyzer contains fixes to all the aforementioned issues.

The branch...
* removes the TLS state machine
* fixes TLS protocol version detection. It also should bail-out correctly on non-tls-connections now
* adds support for a few TLS extensions, including server_name (which might work slightly better now), alpn and ec-curves.
* also adds support for the heartbeat events and the heartbleed detector script
* adds very basic support for OCSP stapling (one can get access to the data).

I think it should be ready for merging as it is. I hope I did not break anything...

github diff link:
https://github.com/bro/bro/compare/topic;bernhard;ssl-analyzer

There still are a few issues that I might fix in the future - e.g. I might add real ocsp stapling support. However, those seem much less urgent and probably will not be interesting to a lot of users at the moment.

> SSL/TLS analyzer does not abort early enough on non-ssl connections
> -------------------------------------------------------------------
>
>                 Key: BIT-1178
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-1178
>             Project: Bro Issue Tracker
>          Issue Type: Problem
>          Components: Bro
>    Affects Versions: git/master
>            Reporter: Bernhard Amann
>            Assignee: Bernhard Amann
>             Fix For: 2.3
>
>
> Some sites see quite a bit of non-ssl traffic on port 443. At the moment, the SSL analyzer manages to parse quite a lot of this non-ssl traffic and generates ssl-events for it (including sending things to the certificate analyzer which generates warnings).
> We should probably try to abort much earlier.



--
This message was sent by Atlassian JIRA
(v6.3-OD-02-026#6318)