> On Feb 6, 2015, at 5:00 PM, anthony kasza wrote:
>
> I was under the impression the spec was still being drafted.
It’s basically done. https://http2.github.io/
Implementations and real world use are starting to show up all over the place.
If you’d like to dig around and find evidence of ht
I was under the impression the spec was still being drafted.
-AK
On Feb 6, 2015 12:54 PM, "Vlad Grigorescu" wrote:
> I don't believe anyone's done any work on this. From what I can tell, most
> implementations (at least IE, Firefox, and Chrome) are only supporting
> HTTP/2.0 over TLS. If that tr
I don't believe anyone's done any work on this. From what I can tell, most
implementations (at least IE, Firefox, and Chrome) are only supporting
HTTP/2.0 over TLS. If that trend continues, the only changes to Bro might
just be ensuring that the SSL analyzer would work with it.
--Vlad
On Fri, F
[
https://bro-tracker.atlassian.net/browse/BIT-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19525#comment-19525
]
Daniel Thayer commented on BIT-1238:
Do you have a set of test files that you could make pu
Has anyone done any work on upgrading Bro to support HTTP/2? If so I'm very
interested in what might have been done and/or what is being done?
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
Seth Hall created BIT-1312:
--
Summary: Plugin path loaded from bro-path-dev.sh
Key: BIT-1312
URL: https://bro-tracker.atlassian.net/browse/BIT-1312
Project: Bro Issue Tracker
Issue Type: Problem
Seth Hall created BIT-1311:
--
Summary: GRE tunnels should be reported as Tunnel::GRE in
tunnels.log
Key: BIT-1311
URL: https://bro-tracker.atlassian.net/browse/BIT-1311
Project: Bro Issue Tracker
Is
Open Merge Requests
===
IDComponentReporterAssigneeUpdated For Version
PrioritySummary
--- -- -- -- -
-- ---
BIT-1011 [1] Bro
