We provide a SaaS so we don't have any installers. I was thinking more
in the lines of the google toolbar installer.
From what you say, all that's needed is to sign the Esker XPI, and
provide a link to it.

Did I get it right?

Thanks,
Leeor Aharon.

--- In esker-activex-plugin@yahoogroups.com, "Roumiantzeff, Nicolas"
<nicolas.roumiantzeff@...> wrote:
>
> Hi Leeoraharon,
>
> Your .exe installation should be a simple Windows program with the
the npeskp32.dll file embedded as a resource and which copies it to
the FireFox "Plugins" folder.
>
> You can locate the FireFox folder in the Windows registry under the
key: HKEY_CLASSES_ROOT\FirefoxHTML\shell\open\command.
>
> You can check Firefox.exe product version (using a bunch of Windows
API documented by Microsoft).
>
> And, if you purchase a certificate from a recognized certification
authority (Verisign or Thawte), you may sign your .exe file and get
rid of the "author not verified" warning.
>
> Nicolas Roumiantzeff
>
>
> Nicolas Roumiantzeff
> Ingénieur Expert Logiciel / Chief Software Engineer
> Esker SA
> Tél : +33 (0)4 72 83 46 79
> Fax : +33 (0)4 72 83 46 40
> mailto:Nicolas.Roumiantzeff@...
> http://www.esker.fr/ ¦ http://www.flydoc.fr/
>
>
>
> From: esker-activex-plugin@yahoogroups.com
[mailto:esker-activex-plugin@yahoogroups.com] On Behalf Of leeoraharon
> Sent: Wednesday, October 29, 2008 9:19 AM
> To: esker-activex-plugin@yahoogroups.com
> Subject: Re: [Esker ActiveX Plug-in] PRIVATE
>
>
>
> --- In esker-activex-plugin@yahoogroups.com
<mailto:esker-activex-plugin%40yahoogroups.com> , "Doug D" <doug@> wrote:
> >
> > --- In esker-activex-plugin@yahoogroups.com
<mailto:esker-activex-plugin%40yahoogroups.com> , "Roumiantzeff, Nicolas"
> > <nicolas.roumiantzeff@> wrote:
> > >
> > > Nicolas Roumiantzeff
> > >
> > > P.S. if anybody as a suggestion regarding this security issue...
> > >
> >
> > We redistribute the plugin as part of our installation .exe. Granted,
> > this means the user needs to download and run a program, but it has
> > worked fine for us.
> >
>
> Well, if we take off the 'author not verified' warning, there
> shouldn't be too much of a problem with that approach. My knowledge of
> FF plugin development is practically non existent, so I have no idea
> how to go about achieving that either.
>