Ask Your Question
0

How to make Wireshark decompress an already decrypted HTTP2 capture?

asked 2018-06-09 16:47:54 +0000

Excelli gravatar image

According to the wiki,

Wireshark 2.4 - header decompression support now requires external nghttp2 package (true for official Windows/macOS builds)

I'm on Linux, and have installed nghttp2. I still get what is probably a compressed stream beyond the header of

PRI * HTTP/2.0

SM

What else should I do?

edit retag flag offensive close merge delete

Comments

I'm on Linux, and have installed nghttp2.

If you're running a version of Wireshark that your distribution provides as a package, then:

  • If it was built with nghttp2, installing it should have installed nghttp2 (most Linux packaging systems keep track of dependencies and install required packages). In that case, installing nghttp2 shouldn't make a difference.
  • If it wasn't built with nghttp2, installing nghttp2 shouldn't make a difference.

If you're running a version of Wireshark that you built yourself, you would have to have installed nghttp2, including a developer package for nghttp2, before configuring the build and building Wireshark.

Does the "About" dialog for Wireshark say it's built with nghttp2? It would be mentioned in the "Compiled" section.

Guy Harris gravatar imageGuy Harris ( 2018-06-09 20:09:33 +0000 )edit

This site is preventing me from either adding a comment (looks like an old broken recaptcha) or editing the original question (edits just disappear). Trying this as a last resort.

I appreciate the clarifications.

My package is provided by my distribution and it says it's compiled with nghttp2.

I also tried the official Windows version with identical results, but I don't know where to get the external package mentioned in the wiki.

Excelli gravatar imageExcelli ( 2018-06-09 21:03:56 +0000 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2018-06-10 04:38:35 +0000

Guy Harris gravatar image

My package is provided by my distribution and it says it's compiled with nghttp2.

Then there's probably a bug in the HTTP2 dissection. You'll have to file a bug on the Wireshark Bugzilla and attach the capture, along with any keys needed to decrypt it.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2018-06-09 16:47:54 +0000

Seen: 51 times

Last updated: Jun 10