Re: Conditional compiles

[Roland Knall <rknall () gmail com>]

One specific future scenario would be an iOS or Android version of
Wireshark purely for analyzing traffic captures and not capturing in
itself. Usually on such systems providing a binary which can capture system
traffic is frowned upon if not outright forbidden by the developer
licenses. Therefore generating a binary which is not even capable of
capturing (as well as integrating plugins or lua scripts for instance)
would be preferrable.

I am not propagating going there, but I do not see a reason in actively
bricking up that road by adding a simplified version of libpcap or making
it obligatory to build against it.

regards

On Tue, Feb 14, 2017 at 3:30 PM, Dario Lombardo <dario.lombardo.ml () gmail com
> wrote:

> On Tue, Feb 14, 2017 at 3:22 PM, Jeff Morriss <jeff.morriss.ws () gmail com>
> wrote:
>
> > I remember getting (infrequent) questions/requests for building Wireshark
> > without the ability to capture.  Usually the desire seems to come from
> > corporate IT policies which don't want people capturing corporate traffic
> > but which need to support users' ability to analyze captures made elsewhere
> > (test systems or maybe from customers?).
> >
> > [Of course most of these requests are probably for the Windows version
> > where you can control the ability to capture by not installing WinPCAP.]
> Well... this is a capability issue. I don't think you can prevent your
> users to capture by giving them a incomplete version of a software. If they
> have the capability of capture, (aka they are root/admin) they can still
> capture with a binary copy of the software. If they can't install software
> or don't have the proper capability... they are done. I think that mixing
> features of a software and capabilities is a bit messy... but maybe there
> are specific scenarios I can't understand.
>
> ____________________________________________________________
> _______________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark org?subject=
> unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe