Editing a saz file (as opposed to real time data) would not be an
issue. If I could distribute a package that would allow them to
install Fiddler2 and modify the HKLM setting that should be fine.
I need to tell management that we have a capture only tool for users
with an issue - FiddlerCap; and a corresponding tool for our network
and performance engineers that would allow them to do the analysis.
On Jul 9, 4:32 pm, EricLaw <
bay...@gmail.com> wrote:
> Can you explain more about your specific constraints? E.g. if there
> was a HKLM registry setting that *forces* viewer mode (and that
> prevents capture of traffic) would that be sufficient?
>
> (That could be easily added, but a coworker could still easily change
> their copy of a data session by right-clicking the session and
> choosing "Unlock for editing.")
>
> Editing On Jul 9, 11:58 am, Chaulklin <
garychaulk...@yahoo.com> wrote:
>
>
>
> > If I want to distribute Fiddler in my organization, but ensure that
> > whomever I distribute it to can only execute Fiddler as if they had
> > used the "-viewer" option; what would my options be?
>
> > They can't (legally) get and use unapproved software. So is there a
> > way I could distribute something to my coworkers that could not be
> > used for anything but viewing previously recorded (FiddlerCap) saz
> > files? Fiddler with the "-viewer" option is what I am looking for as
> > opposed to raw zip files.
>
> > These coworkers are not developers and can't have tools that allow
> > them to modify response data. These coworkers just diagnose
> > problems. The scenario I envision is for the end user to capture an
> > issue with FiddlerCap, send us the saz file, and then one of us would
> > use Fiddler to diagnose the issue.- Hide quoted text -
>
> - Show quoted text -