Ask Your Question

Looking for instructions for downloading and building wireshark on windows.

asked 2018-04-27 13:56:25 +0000

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.

I am trying to setup my pc to build Wireshark so I can create my own dissector. I tried using the instructions at, and I get to the point where I need to pull the code using GIT. However, in section "2.2.9. Install and Prepare Sources" it tells you to clone the code from git clone but that path does not exist?

Does anyone have any instructions for downloading and setting up a build environment that may be more up to date? I am also looking for tips and advice for building a dissector. I appreciate any help or advice.

Thanks - mike

edit retag flag offensive close merge delete


What do you mean by "that path does not exist?" For a browser it doesn't present anything, other than that text, for git it certainly does. Did you actually try the git clone action?

Jaap gravatar imageJaap ( 2018-04-27 14:53:08 +0000 )edit

How have you determined that path doesn't exist, do you get an error from git? If so, what was the error?

The machine you are running this on must have access to the internet.

Running this on my Win10 VM gives the following:

> git clone
Cloning into 'wireshark'...
remote: Counting objects: 48918, done
remote: Finding sources: 100% (1852/1852)
remote: Total 544511 (delta 694), reused 544154 (delta 694)
Receiving objects: 100% (544511/544511), 759.03 MiB | 4.78 MiB/s, done.
Resolving deltas: 100% (419526/419526), done.
Checking out files: 100% (5794/5794), done.
grahamb gravatar imagegrahamb ( 2018-04-27 15:37:27 +0000 )edit

Thanks for responding, yes I tried to clone it using git just as the instructions indicated. This was the error I received when I ran the command. It looks like an certificate issue. Thanks gain - mike

PS C:\Development> git clone
Cloning into 'wireshark'...
fatal: unable to access '': SSL certificate problem: self signed 
certificate in certificate chain
PS C:\Development>
WiresharkNovice gravatar imageWiresharkNovice ( 2018-04-27 18:03:40 +0000 )edit

Then you should definitely look at the certificate chain, starting at, which should be signed by Let's Encrypt Authority, signed by DST Root CA.

Jaap gravatar imageJaap ( 2018-04-27 20:12:53 +0000 )edit

Thank you for the help! I greatly appreciate it. - mike

WiresharkNovice gravatar imageWiresharkNovice ( 2018-04-30 17:21:59 +0000 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2018-04-30 09:34:51 +0000

grahamb gravatar image

Looks like you have an https inspecting proxy (probably a firewall) in the path to that is substituting the original certificate with it's own, and your git client doesn't trust the self-signed certificate.

You can either:

  1. Turn off git certificate checks (not recommended).
  2. Add the proxy certificate to the git certificate store, as mentioned here.
  3. Use a tarball instead of a git clone. Much harder to track your local changes and update with a new tarball (unless you throw it all in a local git repo).
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

1 follower


Asked: 2018-04-27 13:56:25 +0000

Seen: 669 times

Last updated: Apr 27 '18