Revision history [back]

I would like to propose here several solutions that I thought of,
that can be effective in solving the security problem raised.

1) A way to Password Protect any usage of the existing Driver.

2) Installing Wireshark ona Virtual Machine
This is actually a great solution, since the VM is running only when you run it, and the Npcap Driver is installed there,
and not on your actual machine.
It does have one disadvantage tho:
It means that the program that you want to inspect its traffic, also has to run on the VM.
Generally, this is not a problem, simply install the program on the VM, and then run it there, together with Wireshark.
The problem is, that sometimes you want the program to have real access to the Ethernet or Wi-Fi NICs.
And in this way, a VM is a disadvantage, because the VM application acts like a Router.
There is a way to set the VM's NIC in a Bridge Mode,
If it works well, then this might solve the problem I just mentioned..

Will it work 100% identical to the program+Wireshark running ont he real host,
I don't know, but this is a solution to explore.

If anyone has more ideas, please write.

I would like to propose here several solutions that I thought of,
that can be effective in solving the security problem raised.

I would like to propose here several solutions that I thought of, about,
that can be effective in solving the security problem raised.

1. A way to Password Protect any usage of the existing Driver.
2. Installing Wireshark ona Virtual Machine
   This is actually a great solution, since the VM is running only when you run it,
   and the Npcap Driver is installed there, and not on your actual machine.
    
   It does have one disadvantage tho:
   It means that the program that you want to inspect its traffic, also has to run on the VM.
   Generally, this is not a problem, simply install the program on the VM, and then run it there,
   together with Wireshark.
   But sometimes you may want the program to have real access to the Ethernet or Wi-Fi NICs.
   And in this way, a VM is a disadvantage, because the VM application acts like a Router.
   There is a way to set the VM's NIC in a Bridge Mode,
   If it works well, then this might solve the problem I just mentioned..
    
   Will it work 100% identical to the program+Wireshark running ont he real host,
   I don't know, but this is a solution to explore.

If anyone has more ideas, please write.

I would like to propose here several solutions that I thought about,
that can be effective in solving the security problem raised.

1. A way to Password Protect any usage of the existing Driver.Driver.
   But this is a new feature, that does not exist currently,
   and only if the developers of Wireshark (Npcap) decide that it's good, then it will exist..
2. Installing Wireshark ona Virtual Machine
   This is actually a great solution, since the VM is running only when you run it,
   and the Npcap Driver is installed there, and not on your actual machine.
    
   It does have one disadvantage tho:
   It means that the program that you want to inspect its traffic, also has to run on the VM.
   Generally, this is not a problem, simply install the program on the VM, and then run it there,
   together with Wireshark.
   But sometimes you may want the program to have real access to the Ethernet or Wi-Fi NICs.
   And in this way, a VM is a disadvantage, because the VM application acts like a Router.
   There is a way to set the VM's NIC in a Bridge Mode,
   If it works well, then this might solve the problem I just mentioned..
    
   Will it work 100% identical to the program+Wireshark running ont he real host,
   I don't know, but this is a solution to explore.

If anyone has more ideas, please write.

I would like to propose here several solutions that I thought about,
that can be effective in solving the security problem raised.

1. A way to Password Protect any usage of the existing Driver.
   But this is a new feature, that does not exist currently,
   and only if the developers of Wireshark (Npcap) decide that it's good, then it will exist..
2. Installing Wireshark ona Virtual Machine
   This is actually a great solution, since the VM is running only when you run it,
   and the Npcap Driver is installed there, and not on your actual machine.
    
   It does have one disadvantage tho:
   It means that the program that you want to inspect its traffic, also has to run on the VM.
   Generally, this is not a problem, simply install the program on the VM, and then run it there,
   together with Wireshark.
   But sometimes you may want the program to have real access to the Ethernet or Wi-Fi NICs.
   And in this way, a VM is a disadvantage, because the VM application acts like a Router.
   There is a way to set the VM's NIC in a Bridge Mode, Mode,
   If it works well, then this might solve the problem I just mentioned..
    
   Will it work 100% identical to the program+Wireshark running ont he on the real host,
   I don't know, but this is a solution to explore.

If anyone has more ideas, please write.

I would like to propose here several solutions that I thought about,
that can be effective in solving the security problem raised.

1. A way to Password Protect any usage of the existing Driver.
   But this is a new feature, that does not exist currently,
   and only if the developers of Wireshark (Npcap) decide that it's good, then it will exist..
2. Installing Wireshark ona Virtual Machine
   This is actually a great solution, since the VM is running only when you run it,
   and the Npcap Driver is installed there, and not on your actual machine.
    
   It does have one disadvantage tho:
   It means that the program that you want to inspect its traffic, also has to run on the VM.
   Generally, this is not a problem, simply install the program on the VM, and then run it there,
   together with Wireshark.
   But sometimes you may want the program to have real access to the Ethernet or Wi-Fi NICs.
   And in this way, a VM is a disadvantage, because the VM application acts like a Router.
   There is a way to set the VM's NIC in Bridge Mode,
   If it works well, then this might solve the problem I just mentioned..
    
   Will it work 100% identical to the program+Wireshark running on the real host,
   I don't know, but this is a solution to explore.

If anyone has more ideas, please write.